From 89df75b75c26e6925029df5713ba5377940f126f Mon Sep 17 00:00:00 2001 From: Mike Rottina Date: Thu, 25 Nov 2021 22:07:37 -0500 Subject: [PATCH] #9410 fix --- .../performance/get-started/wrapup-7.md | 21 ++----------------- 1 file changed, 2 insertions(+), 19 deletions(-) diff --git a/src/content/en/fundamentals/performance/get-started/wrapup-7.md b/src/content/en/fundamentals/performance/get-started/wrapup-7.md index 787c6fb47ce..768e54680ba 100644 --- a/src/content/en/fundamentals/performance/get-started/wrapup-7.md +++ b/src/content/en/fundamentals/performance/get-started/wrapup-7.md @@ -1,7 +1,7 @@ project_path: /web/fundamentals/_project.yaml book_path: /web/fundamentals/_book.yaml -{# wf_updated_on: 2018-08-17 #} +{# wf_updated_on: 2021-11-25 #} {# wf_published_on: 2018-02-22 #} {# wf_blink_components: Blink>PerformanceAPIs,Blink>JavaScript>Runtime #} @@ -19,11 +19,6 @@ versions of a web page, beginning with no optimization and progressing through s the speed-up techniques we've discussed, specifically text resource optimization, graphics resource optimization, and HTTP request reduction. -The original target is a simple, single HTML page with text, images, CSS, and JavaScript, -hosted on Firebase here: -[https://page-load-speed-demo.firebaseapp.com/pageload0.html](https://page-load-speed-demo.firebaseapp.com/pageload0.html). -Have a quick look at that, and then we can start improving it. - **Note:** The source code for all versions of the demo page referenced in this document can be found in [this GitHub repository](https://github.com/GoogleChromeLabs/FastPageLoadDemo). @@ -53,7 +48,7 @@ There are many, many tools available to help determine a page's load speed, far to list here. For this article, we will use three online services to help us see the results of our improvement efforts. -- [Google PageSpeed Insights](http://tinyurl.com/m65jex6) +- [Google PageSpeed Insights](/speed) - [WebPageTest](https://www.webpagetest.org/) @@ -185,9 +180,6 @@ which will generate a Lighthouse report. Then click the *Lighthouse PWA Score* a of the page to see the full Lighthouse Progressive Web App report, including the new Consistently Interactive metric. - Here is the text-minified version: - [https://page-load-speed-demo.firebaseapp.com/pageload1.html](https://page-load-speed-demo.firebaseapp.com/pageload1.html). - ## Graphical Content Another area ripe for improvement in this page is its over/misuse of graphics. This is not @@ -347,9 +339,6 @@ downloading images than before, a significant improvement. ![WebPageTest, optimized images](images/image_714.png) *WebPageTest, optimized images* -Here is the image-optimized version: -[https://page-load-speed-demo.firebaseapp.com/pageload2.html](https://page-load-speed-demo.firebaseapp.com/pageload2.html). - ## HTTP Requests Recall that the loading speed of a page depends not only on the size of the resources @@ -438,9 +427,6 @@ overall reduction in HTTP requests has leveled the playing field such that is no so image-heavy. To put it another way, in this version the browser makes no more server hits loading the images than it does loading *all other resources combined*. -Here is the reduced HTTP requests version: -[https://page-load-speed-demo.firebaseapp.com/pageload3.html](https://page-load-speed-demo.firebaseapp.com/pageload3.html). - ## All Together Now Now that we've seen some speed improvements resulting from individual techniques, let's see @@ -473,9 +459,6 @@ Fully Loaded scores, and its (beta) First Interactive time is less than a second ![WebPageTest, all techniques](images/image_722.png) *WebPageTest, all techniques* -Here is the all-techniques version: -[https://page-load-speed-demo.firebaseapp.com/pageload4.html](https://page-load-speed-demo.firebaseapp.com/pageload4.html). - ## Summary What can we take away from all these techniques, tests, and reports? Let's look at