[ Performance ] Improve Blog page Performance #6930
Description
Description
In Mobile Site of Blog
currently shows low performance scores on PageSpeed Insights
Here’s a detailed report highlighting the issues causing the page to lag: Report
Insights (Opportunities for Improvement)
| Audit Title | Est. Savings / Score | Relevance | Status | Details |
|---|---|---|---|---|
| Use efficient cache lifetimes | 736 KiB | LCP, FCP | 🔴 Failed | Cache lifetimes are too short (mostly 4 hours) for numerous first-party resources, including JS bundles and fonts. This delays repeat visits. |
| Forced reflow | (Empty) | (None specified) | 🔴 Failed | JavaScript is forcing layout recalculations (80 ms total reflow time from /framework-00cd734….js), which hurts performance. |
| LCP request discovery | (Empty) | LCP | 🔴 Failed | The Largest Contentful Paint image is not optimally discovered (missing fetchpriority=high) or being lazy-loaded in a way that delays LCP, despite not having loading="lazy" removed from the snippet. |
| Network dependency tree | (Empty) | LCP | 🔴 Failed | The Maximum critical path latency is 174 ms, caused by render-blocking resources like custom fonts (/static/QanelasSo….otf). |
| Improve image delivery | 145 KiB | LCP, FCP | 🟠 Warning | Multiple images are larger than their displayed size (e.g., 750x353/354 px used for 382x219/208 px display), indicating they are not properly sized or served responsively. |
| Render blocking requests | (Empty) | LCP, FCP | 🟠 Warning | A script from Cloudflare (email-decode.min.js) is blocking the page's initial render. |
| Duplicated JavaScript | 1 KiB | LCP, FCP | 🟠 Warning | Duplicated modules like node_modules/react-dom are present in different bundles, leading to unnecessary network download size (e.g., 20 KiB duplicate in /1108-2777267….js). |
| Minimize main-thread work | 3.4 s | TBT | 🔴 Failed | Excessive time spent on the main thread, primarily for Script Evaluation (1,846 ms), delaying interactivity. |
| Reduce JavaScript execution time | 2.0 s | TBT | 🔴 Failed | High total CPU time spent on JS, mainly within first-party scripts like /framework-00cd734….js (1,806 ms total CPU time). |
| Reduce unused JavaScript | 274 KiB | LCP, FCP | 🔴 Failed | Large amounts of JavaScript are downloaded but unused, including third-party scripts from Google Tag Manager and Hotjar, and a large portion of the main application bundle. |
| Minify CSS | 2 KiB | LCP, FCP | 🟠 Warning | Unminified CSS code is being served, which could save a small amount of bytes. |
| Avoid serving legacy JavaScript to modern browsers | 2 KiB | LCP, FCP | 🟠 Warning | Legacy JavaScript features are being transpiled by Babel (e.g., @babel/plugin-transform-classes), suggesting that unnecessarily large polyfills/transforms are being sent to modern browsers. |
| Reduce unused CSS | 24 KiB | LCP, FCP | 🟠 Warning | Unused CSS rules exist in stylesheets, leading to unnecessary download size. |
Expected Behavior
The website should implement the optimizations suggested by PageSpeed Insights.
Screenshots
Steps to Check Page Performance Scores
-
Open PageSpeed Insights
-
Enter the website URL.
-
Check the performance scores for both Mobile and Desktop.
-
Scroll down to review detailed insights and recommendations for improving page performance.
Contributor Resources and Handbook
The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.
- 📚 See contributing instructions.
- 🎨 Wireframes and designs for Layer5 site in Figma (open invite)
- 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack.
Join the Layer5 Community by submitting your community member form.