Commit da1e71b

Daniel Axtens <dja@axtens.net>
2026-11-15 01:25:47
link images so hugo will process them 🤡
1 parent 475b541
Changed files (1)
blog
content
blog
csp-css-caching
blog/content/blog/csp-css-caching/index.md
@@ -46,11 +46,11 @@ A lot of web performance resources, including Google's, encourage you to put ren
 
 Indeed, if you load up [a page from this website](https://pagespeed.web.dev/analysis/https-www-intermittent-network-blog/l1jzs9lmnv?form_factor=mobile) in Google's web interface to PageSpeed Insights, Google suggests removing render blocking requests by deferring or inlining:
 
-![A screenshot from Lighthouse warning me about render-blocking requests for CSS](./recommendations.png)
+![A screenshot from Lighthouse warning me about render-blocking requests for CSS](recommendations.png)
 
 However, there's a critical detail elsewhere on the page:
 
-![Another part of the Lighthouse report, showing that the measurement was an initial page load](./test-details.png)
+![Another part of the Lighthouse report, showing that the measurement was an initial page load](test-details.png)
 
 In small print in the bottom left-hand corner, we see that this is measuring an _initial page load_. It assumes that none of the resources can be served from the browser cache. That makes sense for some sites - perhaps most sites - but it means that this analysis will overstate the impact of having an external CSS or JavaScript resource if it's cacheable, and a visitor visits multiple pages that use it.