Skip to content
This repository has been archived by the owner on Aug 10, 2022. It is now read-only.

#9410 fix #9468

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

#9410 fix #9468

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
21 changes: 2 additions & 19 deletions src/content/en/fundamentals/performance/get-started/wrapup-7.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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 #}

Expand All @@ -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).

Expand Down Expand Up @@ -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/)

Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down