[ Performance ] Improve Pricing page Performance
Open
@Sbragul26 is already working on this.
Since Feb 20, 2026.
framework/gatsby
hacktoberfest
help wanted
kind/bug
type/performance
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 1.6k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 18
Description
Description
In Mobile Site of Pricing
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 | 1,982 KiB | LCP, FCP | ❌ Fail | Cache lifetimes are too short for many resources, forcing repeat downloads on subsequent visits. |
| Forced reflow | – | – | ❌ Fail | JavaScript is causing costly layout recalculations (forced reflows) on the main thread. |
| Network dependency tree | Max critical path latency: 548 ms | LCP | ❌ Fail | The critical request chain is too long, delaying content rendering. The longest chain ends with the font file /static/QanelasSoftRegular-6917692db33119190d17b5981aa19a0e.otf. |
| Defer offscreen images | 1,092 KiB | LCP, FCP | ❌ Fail | Images are loading unnecessarily even if they're offscreen (below the fold). |
| Minimize main-thread work | 7.3 s | TBT | ❌ Fail | Excessive time spent on the main thread in activities like Style & Layout (2,982 ms) and Script Evaluation (1,965 ms). |
| Reduce JavaScript execution time | 2.6 s | TBT | ❌ Fail | High time spent parsing, compiling, and executing JavaScript, primarily from /pricing, /framework-00cd734...js, and /21c5e1c...js. |
| Duplicated JavaScript | 37 KiB | LCP, FCP | ⚠️ Average | Code is duplicated across multiple bundles (e.g., @mui/system, @mui/utils), increasing download size. |
| Legacy JavaScript (Insight) | 62 KiB | LCP, FCP | ⚠️ Average | Legacy JavaScript polyfills/transforms are being served to modern browsers unnecessarily. |
| Minify CSS | 3 KiB | LCP, FCP | ⚠️ Average | CSS files are not fully minified, adding a small, unnecessary payload. |
| Avoid serving legacy JavaScript to modern browsers | 64 KiB | LCP, FCP | ⚠️ Average | Confirms legacy JavaScript polyfills/transforms are being served unnecessarily, adding to file size. |
| Reduce unused CSS | 15 KiB | LCP, FCP | ⚠️ Average | Stylesheets contain unused CSS rules that increase download size. |
| Reduce unused JavaScript | 889 KiB | LCP, FCP | ⚠️ Average | Large portions of JavaScript files are unused on the current page, notably: /21c5e1c...js, /6f82d58...js, and /d60e3cc...js. |
| Avoid enormous network payloads | 3,347 KiB | – | ⚠️ Average | The total page payload is very large, primarily due to large JavaScript and image files. |
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.