Speed Optimization in 4 Minutes
Step 7 - Repeat-view Optimization
Did you notice that this page loaded twice? That's because we're taking advantage of browser caching. The first load data was retrieved from the server ('first-view'), but the second load your browser already had it locally and since nothing had changed it didn't even have to go to the server ('repeat-view'). You can't get any more optimized than staying within your own local browser cache.
There are various ways to set these headers so the browser knows to save it and for how long. The downside is sometimes this content will be saved too long, preventing the user from seeing the most up-to-date resources. There are ways around this, but it can be tricky.
Let's see how this affected our stats:
| Metric | This Load | Versus Last Step | Versus Baseline |
|---|---|---|---|
| Time to First Byte (TTFB) | - | - - | - - |
| Largest Contentful Paint (LCP) | - | - - | - - |
| Page Complete | - | - - | - - |
| Page Weight (transferred) | - | - - | - - |
Questions about these metrics?
Hover over the metrics above to see descriptions of each. Why didn't we choose other metrics, such as First Input Delay (FID) or Cumulative Layout Shift (CLS)? Simply because they were hard to represent in this demo. FID requires user interaction, which is tricky to fake. CLS is a lifetime metric (measured the whole time you're on the page, not just during load), so we can't report that until you leave the page. There are a lot of very important speed metrics and it's encouraged to get to know more than the few here.
Compared to the baseline, all the optimizations so far have affected the complete page load by -.
To ensure valid comparisons, we've placed a specific amount of hidden html comments here so the textual content of every step is the same length.
Optimization not as great as you think? Good observation. Sometimes speed optimization is trial and error. Not all steps work well for every website.