Executive Summary. Performance Report for: The web should be fast. Top 5 Priority Issues. How does this affect me?

Transcription

1 The web should be fast. Executive Summary Performance Report for: Report generated: Test Server Region: Using: Mon, Jul 30, 2018, 2:22 PM Vancouver, Canada Chrome (Android, Galaxy Nexus) , PageSpeed 1.15-gt1, YSlow PageSpeed Score (77%) YSlow Score (82%) Fully Loaded Time 16.2s Total Page Size 1.54MB Requests 79 Top 5 Priority Issues Minimize redirects F (22) AVG SCORE: 89% CONTENT HIGH Leverage browser caching F (27) AVG SCORE: 59% SERVER HIGH Defer parsing of JavaScript E (58) AVG SCORE: 70% JS HIGH Specify a cache validator B (84) AVG SCORE: 94% SERVER HIGH Serve resources from a consistent URL B (87) AVG SCORE: 88% CONTENT HIGH How does this affect me? Studies show that users leave a site if it hasn't loaded in 4 seconds; keep your users happy and engaged by providing a fast performing website. As if you didn't need more incentive, Google has announced that they are using page speed in their ranking algorithm. About GTmetrix We can help you develop a faster, more efficient, and all-around improved website experience for your users. We use Google PageSpeed and Yahoo! YSlow to grade your site's performance and provide actionable recommendations to fix these issues. About the Developer GTmetrix is developed by the good folks at GT.net, a Vancouver-based performance hosting company with over 22 years experience in web technology. What do these grades mean? This report is an analysis of your site with Google and Yahoo!'s metrics for how to best develop a site for optimized speed. The grades you see represent how well the scanned URL adheres to those rules. Lower grades (C or lower) mean that the page can stand to be faster using better practices and optimizing your settings. What's in this report? This report covers basic to technical analyses on your page. It is categorized under many headings: Executive: Overall score information and Priority Issues History: Graphed history of past performance Waterfall: Graph of your site's loading timeline Technical: In-depth PageSpeed & YSlow information These will provide you with a snapshot of your performance. Analyze your site at Page 1 of 10

2 History History Page load times 25s 20s 15s 10s 5s 0s Jul 30 02:15PM Jul 30 02:16PM Jul 30 02:17PM Jul 30 02:18PM Jul 30 02:19PM Jul 30 02:20PM Jul 30 02:21PM Jul 30 02:22PM Time to First Byte Onload Time Fully Loaded Page sizes and request counts 1.91MB 1.43MB KB KB 70 Jul 30 02:15PM Jul 30 02:16PM Jul 30 02:17PM Jul 30 02:18PM Jul 30 02:19PM Jul 30 02:20PM Jul 30 02:21PM Jul 30 02:22PM Requests HTML Size Total Page Size 60 PageSpeed and YSlow scores 100% 90% 80% 70% 60% Jul 30 02:15PM Jul 30 02:16PM Jul 30 02:17PM Jul 30 02:18PM Jul 30 02:19PM Jul 30 02:20PM Jul 30 02:21PM Jul 30 02:22PM PageSpeed Score YSlow Score Analyze your site at Page 2 of 10

3 Waterfall Chart Waterfall Chart The waterfall chart displays the loading behaviour of your site in your selected browser. It can be used to discover simple issues such as 404's or more complex issues such as external resources blocking page rendering. Weebly Website Builder: Create a Free Website, Store or Blog GET Foundweebly.com 0 GET ca 200 OK weebly.com 29 KB GET gdprscript.js?buildtime= OK weebly.com 227 B GET cxj0npn.js 200 use.typekit.net7.6 KB GET main.css?buildtime= OK cdn2.editmysite.com 52.1 KB GET abtest.css?buildtime= OK cdn2.editmysite.com 32.5 KB GET jquery.min.js 200 ajax.googleapis.com 29 KB GET utl.js?buildtime= & 200 OK cdn2.editmysite.com KB GET api.js 200 google.com 448 B GET circle-check.svg?v=1 200 OK cdn2.editmysite.com 539 B GET main.js?buildtime= OK cdn2.editmysite.com KB GET recaptcha en.js 200 gstatic.com 76.1 KB GET beet?type=load&ref=&duid=b2cef6713ab bfe4a d3b511&ts= OK weebly.com 42 B 76.5ms GET poster--mobile@2x.jpg 200 OK cdn2.editmysite.com KB GET poster--tablet.jpg 200 OK cdn2.editmysite.com 43 KB GET noise.jpg 200 OK cdn2.editmysite.com 6.2 KB GET w-icons.woff? OK cdn2.editmysite.com 78.2 KB GET 31AC96_2_0.woff 200 OK cdn2.editmysite.com 44.4 KB GET 31AC96_1_0.woff 200 OK cdn2.editmysite.com 45 KB GET snowday261.js 200 OK cdn2.editmysite.com 25.1 KB GET l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n4&v=3 200 use.typekit.net 23.8 KB 133.1ms GET l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=i4&v=3 200 use.typekit.net 24.6 KB 202.1ms GET l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n7&v=3 200 use.typekit.net 23.1 KB 223.9ms GET l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n3&v=3 200 use.typekit.net 25.6 KB 237.3ms GET l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=i3&v=3 200 use.typekit.net 24.2 KB 256.7ms GET l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n5&v=3 200 use.typekit.net 24.5 KB 263.5ms GET l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n9&v=3 200 use.typekit.net 24.3 KB 190.5ms GET l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n7&v=3 200 use.typekit.net 27.1 KB 145ms GET l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=i7&v=3 200 use.typekit.net 26 KB 167.8ms GET l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n5&v=3 200 use.typekit.net 28.6 KB 128.9ms GET l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=i5&v=3 200 use.typekit.net 27.2 KB 234.5ms GET gtmdata OPTIONS tp2 200 OK weebly.com 846 B 200 OK ec.weebly.com 0 GET p.gif?s=1&k=cxj0npn&ht=tk&h= 200 OK p.typekit.net 35 B 167.8ms POST tp2 200 OK ec.weebly.com 0 GET gtm.js?id=gtm-m9n5cnd&l=weblayer 200 googletagmanager.com 40.1 KB GET favicon.ico GET analytics.js 200 OK weebly.com 6.4 KB 200 google-analytics.com 14 KB GET conversion_async.js 200 googleadservices.com 6.7 KB GET fbevents.js GET qevents.js GET tfa.js GET bat.js 200 connect.facebook.net 13 KB 200 a.quora.com 5.4 KB 200 cdn.taboola.com4.8 KB 200 bat.bing.com 6.9 KB GET order?api_key=0034b8cb8b954ca5a382b32549deb3d7&event=site_visit&gtmcb= revfluence.com 0 GET ca? GET ca? POST tp2 GET spacer.png GET linkid.js GET ec.js fls.doubleclick.net 371 B fls.doubleclick.net 370 B 200 OK ec.weebly.com revfluence.com 95 B 200 google-analytics.com 856 B 200 google-analytics.com 1.3 KB 666.7ms 293.2ms 125.1ms 378.3ms 390ms 371.3ms 432.1ms 946ms 282.7ms 930.5ms 893.5ms 259ms 91.8ms 42.8ms 42.3ms 132.1ms 47ms 79.1ms 57.3ms GET pixel?j=1&u= 200 OK q.quora.com 43 B GET ?random= &cv=9&fst= &num=1&guid=ON&resp=GooglemKTybQhCsO&u_h=640&u_w=360&u_ah=640&u_aw= googleads.g.doubleclick.net 954 B 385.3ms 92.3ms 399.7ms 344.6ms 162.9ms 113.1ms 207.8ms 240.6ms 386.4ms 180.2ms 357.2ms 582.5ms 436.2ms 423ms 1.49s 134.4ms 23ms 29ms 29.5ms 793.2ms Analyze your site at Page 3 of 10

4 Waterfall Chart GET ?v=2.8.23&r=stable 200 connect.facebook.net 16.2 KB GET mark?tim=12:21:55.262&item-url= 204 trc.taboola.com 9 B GET ?random= &cv=9&fst= &num=1&value=0&label=dvA8COHVqXAQosze1AM&guid=ON&resp=GooglemKTybQhCsO&u 200 googleadservices.com 1 KB 407.9ms GET ?random= &cv=9&fst= &num=1&value=0&label=t_j7CNyn44ABENftlJoD&guid=ON&resp=GooglemKTybQhCsO&u_h 200 googleadservices.com 1 KB 392.8ms GET ca GET ca POST collect 200 adservice.google.com 372 B 200 adservice.google.com 370 B 200 google-analytics.com 35 B GET js?id=gtm-plkfd8m&l=weblayer&t=gtm23&cid= google-analytics.com 13.8 KB GET collect?t=dc&aip=1&_r=3&v=1&_v=j68&tid=ua &cid= &jid= &gjid= &_gid= stats.g.doubleclick.net 364 B 331.4ms GET 0?ti= &Ver=2&mid=d88075cf-b4bb-253c-d6aa-b35e0d70685c&pi=0&lg=en-US&sw=360&sh=640&sc=32&tl=Weebly 204 bat.bing.com 9 B Website 33.4ms Builder: Create a Free GET tr?id= &ev=pageview&dl= 200 facebook.com 44 B 456.3ms GET tr?id= &ev=pageviewexternal&dl= 200 facebook.com 44 B 472.3ms GET ?random= &cv=9&fst= &num=1&guid=ON&u_h=640&u_w=360&u_ah=640&u_aw=360&u_cd=32&u_his=2&u_tz= 200 google.com 42 B 188.1ms GET ?random= &cv=9&fst= &num=1&guid=ON&u_h=640&u_w=360&u_ah=640&u_aw=360&u_cd=32&u_his=2&u_tz= 200 google.ca 42 B 866.5ms GET ?random= &cv=9&fst=*&num=1&value=0&label=dvA8COHVqXAQosze1AM&guid=ON&resp=GooglemKTybQhCsO&u_h=640&u_w= googleads.g.doubleclick.net 42 B 132.3ms GET ?random= &cv=9&fst=*&num=1&value=0&label=t_j7CNyn44ABENftlJoD&guid=ON&resp=GooglemKTybQhCsO&u_h=640&u_w=360&u 302 googleads.g.doubleclick.net 42 B 338.6ms GET iframe_api 200 youtube.com 859 B GET ga-audiences?v=1&aip=1&t=sr&_r=4&tid=ua &cid= &jid= &_v=j68&z= google.com 0 GET tr?id= &ev=microdata&dl= 200 facebook.com 44 B 119.4ms GET ?random= &cv=9&fst=*&num=1&value=0&label=dvA8COHVqXAQosze1AM&guid=ON&resp=GooglemKTybQhCsO&u_h=640&u_w= google.com 895 B 124.6ms GET ga-audiences?v=1&aip=1&t=sr&_r=4&tid=ua &cid= &jid= &_v=j68&z= &slf_rd=1&random= google.ca 42 B 147.3ms GET ca GET ca 200 adservice.google.ca 177 B 200 adservice.google.ca 177 B GET ?random= &cv=9&fst=*&num=1&value=0&label=t_j7CNyn44ABENftlJoD&guid=ON&resp=GooglemKTybQhCsO&u_h=640&u_w=360&u 302 google.com 895 B 156ms GET ?random= &cv=9&fst=*&num=1&value=0&label=dvA8COHVqXAQosze1AM&guid=ON&resp=GooglemKTybQhCsO&u_h=640&u_w= google.ca 42 B 97.4ms GET www-widgetapi.js 200 s.ytimg.com 7.5 KB GET ?random= &cv=9&fst=*&num=1&value=0&label=t_j7CNyn44ABENftlJoD&guid=ON&resp=GooglemKTybQhCsO&u_h=640&u_w=360&u 200 google.ca 42 B 162.3ms 79 Requests 1.5 MB 16.22s (onload: 9.14s) 186.1ms 179ms 629.9ms 530ms 48.7ms 123.3ms 629.8ms 121.7ms 834.7ms 724.6ms 432.1ms Analyze your site at Page 4 of 10

5 Page Load Timings Page Load Timings RUM Speed Index: 3,726 Redirect 0.7s Connect 4ms Backend 247ms TTFB 0.9s First paint 3.7s Contentful paint 3.7s DOM int. 7.5s DOM loaded 7.5s (1.1s) Onload 9.1s (5ms) Redirect duration This is the time spent redirecting URLs before the final HTML page is loaded. Common redirects include: Redirect from a non-www to www (eg. example.com to Redirect to a secure URL (eg. to Redirect to set cookies Redirect to a mobile version of the site Some sites may even perform a chain of multiple redirects (eg. non-www to www, then to a secure URL). This timing is the total of all this time that's spent redirecting, or 0 if no redirects occurred. In the Waterfall Chart, Redirect duration consists of the time from the beginning of the test until just before we start the request of the final HTML page (when we receive the first 200 OK response). During this time, the browser screen is blank! Ensure that this duration is kept to short by minimizing your redirects. Connection duration Once any redirects have completed, Connection duration is measured. This is the time spent connecting to the server to make the request to the page. Technically speaking, this duration is a combination of the blocked time, DNS time, connect time and sending time of the request (rather than just connect time). We've combined those components into a single Connection duration to simplify things (as most of these times are usually small). In the Waterfall Chart, Connection duration consists of everything up to and including the "Sending" time in the final HTML page request (the first 200 OK response). During this time, the browser screen is still blank! Various causes could contribute to this, including a slow/problematic connection between the test server and site or slow response times from the site. Backend duration Once the connection is complete and the request is made, the server needs to generate a response for the page. The time it takes to generate the response is known as the Backend duration. In the Waterfall Chart, Backend duration consists of purple waiting time in the page request. There are a number of reasons why Backend duration could be slow. We cover this is our "Why is my page slow" article. Time to First Byte (TTFB) Analyze your site at Page 5 of 10

6 Page Load Timings Time to First Byte (TTFB) is the total amount of time spent to receive the first byte of the response once it has been requested. It is the sum of "Redirect duration" + "Connection duration" + "Backend duration". This metric is one of the key indicators of web performance. In the Waterfall Chart, it is calculated at the start of the test until just before receiving on the page request and represented by the orange line. Some ways to improve the TTFB include: optimizing application code, implementing caching, finetuning your web server configuration, or upgrading server hardware. First paint time indicate a fast loading page. First paint time is the first point at which the browser does any sort of rendering on the page. Depending on the structure of the page, this first paint could just be displaying the background colour (including white), or it could be a majority of the page being rendered. In the Waterfall Chart, it is represented by the green line. This timing is of significance because until this point, the browser will have only shown a blank page and this change gives the user an indication that the page is loading. However, we don't know how much of the page was rendered with this paint, so having a early first paint doesn't necessarily If the browser does not perform a paint (ie. the html results in an blank page), then the paint timings may be missing. First contentful paint time First Contentful Paint is triggered when any content is painted - i.e. something defined in the DOM (Document Object Model). This could be text, an image or canvas render. This timing aims to be more representative of your user's experience, as it flags when actual content has been loaded in the page, and not just any change - but it may often be the same time as First Paint. Because the focus is on content, the idea is that this metric gives you an idea of when your user receives consumable information (text, visuals, etc) - much more useful for performance assessment than when a background has changed or a style has been applied. If the browser does not perform a paint (ie. the html results in an blank page), then the paint timings may be missing. DOM interactive time DOM interactive time is the point at which the browser has finished loading and parsing HTML, and the DOM (Document Object Model) has been built. The DOM is how the browser internally structures the HTML so that it can render it. DOM interactive time isn't marked in the Waterfall Chart as it's usually very close in timing to DOM content loaded. DOM content loaded time DOM content loaded time (DOM loaded or DOM ready for short) is the point at which the DOM is ready (ie. DOM interactive) and there are no stylesheets blocking JavaScript execution. If there are no stylesheets blocking JavaScript execution and there is no parser blocking JavaScript, then this will be the same as DOM interactive time. In the Waterfall Chart, it is represented by the blue line. The time in brackets is the time spent executing JavaScript triggered by the DOM content loaded event. Many JavaScript frameworks use this event as a starting point to begin execution of their code. Analyze your site at Page 6 of 10

7 Page Load Timings Since this event is often used by JavaScript as the starting point and delays in this event mean delays in rendering, it's important to make sure that style and script order is optimized and that parsing of JavaScript is deferred. Onload time Onload time occurs when the processing of the page is complete and all the resources on the page (images, CSS, etc.) have finished downloading. This is also the same time that DOM complete occurs and the JavaScript window.onload event fires. Note that there may be JavaScript that initiates subsequent requests for more resources, hence the reason why Fully loaded timing is preferred. In the Waterfall Chart, it is represented by the red line. The time in brackets is the time spent executing JavaScript triggered by the Onload event. Note that Onload time was the previous default for when to stop the test prior to Feburary 8th, Analyze your site at Page 7 of 10

8 PageSpeed Recommendations PageSpeed Recommendations RECOMMENDATION GRADE RELATIVE TYPE PRIORITY Minimize redirects F (22) AVG SCORE: 89% CONTENT HIGH Leverage browser caching F (27) AVG SCORE: 59% SERVER HIGH Defer parsing of JavaScript E (58) AVG SCORE: 70% JS HIGH Specify a cache validator B (84) AVG SCORE: 94% SERVER HIGH Serve resources from a consistent URL B (87) AVG SCORE: 88% CONTENT HIGH Minimize request size A (94) AVG SCORE: 96% CONTENT HIGH Minify JavaScript A (97) AVG SCORE: 88% JS HIGH Minify HTML A (99) AVG SCORE: 98% CONTENT LOW Enable gzip compression A (99) AVG SCORE: 85% SERVER HIGH Minify CSS A (99) AVG SCORE: 95% CSS HIGH Specify image dimensions A (99) AVG SCORE: 98% IMAGES MEDIUM Optimize images A (99) AVG SCORE: 70% IMAGES HIGH Remove query strings from static resources A (92) AVG SCORE: 88% CONTENT LOW Avoid bad requests A (100) AVG SCORE: 98% CONTENT HIGH Avoid landing page redirects A (100) AVG SCORE: 98% SERVER HIGH Enable Keep-Alive A (100) AVG SCORE: 96% SERVER HIGH Inline small CSS A (100) AVG SCORE: 96% CSS HIGH Inline small JavaScript A (100) AVG SCORE: 94% JS HIGH Optimize the order of styles and scripts A (100) AVG SCORE: 94% CSS/JS HIGH Put CSS in the document head A (100) AVG SCORE: 100% CSS HIGH Serve scaled images A (100) AVG SCORE: 73% IMAGES HIGH Combine images using CSS sprites A (100) AVG SCORE: 90% IMAGES HIGH Avoid A (100) AVG SCORE: 98% CSS MEDIUM Prefer asynchronous resources A (100) AVG SCORE: 100% JS MEDIUM Specify a Vary: Accept-Encoding header A (99) AVG SCORE: 96% SERVER LOW Specify a character set early A (100) AVG SCORE: 100% CONTENT MEDIUM Avoid a character set in the meta tag A (100) AVG SCORE: 100% CONTENT LOW Analyze your site at Page 8 of 10

9 PageSpeed Recommendations Avoid Plugins A (100) AVG SCORE: 100% CONTENT LOW Analyze your site at Page 9 of 10

10 YSlow Recommendations YSlow Recommendations RECOMMENDATION GRADE RELATIVE TYPE PRIORITY Add Expires headers F (34) AVG SCORE: 26% SERVER HIGH Reduce DNS lookups F (0) AVG SCORE: 69% CONTENT LOW Make fewer HTTP requests B (80) AVG SCORE: 32% CONTENT HIGH Use a Content Delivery Network (CDN) B (80) AVG SCORE: 21% SERVER MEDIUM Minify JavaScript and CSS A (90) AVG SCORE: 71% CSS/JS MEDIUM Avoid URL redirects A (90) AVG SCORE: 88% CONTENT MEDIUM Use cookie-free domains A (90) AVG SCORE: 50% COOKIE LOW Compress components with gzip A (100) AVG SCORE: 86% SERVER HIGH Make AJAX cacheable A (100) AVG SCORE: 100% JS MEDIUM Remove duplicate JavaScript and CSS A (100) AVG SCORE: 100% CSS/JS MEDIUM Avoid AlphaImageLoader filter A (100) AVG SCORE: 99% CSS MEDIUM Avoid HTTP 404 (Not Found) error A (100) AVG SCORE: 98% CONTENT MEDIUM Reduce the number of DOM elements A (100) AVG SCORE: 92% CONTENT LOW Use GET for AJAX requests A (100) AVG SCORE: 100% JS LOW Avoid CSS expressions A (100) AVG SCORE: 99% CSS LOW Reduce cookie size A (100) AVG SCORE: 100% COOKIE LOW Make favicon small and cacheable A (100) AVG SCORE: 100% IMAGES LOW Configure entity tags (ETags) A (100) AVG SCORE: 91% SERVER LOW Make JavaScript and CSS external (n/a) CSS/JS MEDIUM Analyze your site at Page 10 of 10