How to Improve Your Google PageSpeed Score in 2026
A step-by-step guide to improving your Google PageSpeed Insights score. Covers the most impactful fixes for images, JavaScript, caching, and server response time.
What is Google PageSpeed Insights?
Google PageSpeed Insights (PSI) analyses a URL and reports on its performance using Lighthouse lab data and — where available — real user data from the Chrome User Experience Report (CrUX).
The score runs from 0 to 100:
The score is a weighted average of several underlying metrics. It is a useful proxy for real-world performance but should not be treated as the goal in itself — the underlying metrics and real user experience are what matter.
Step 1: Fix your images first
Images are the single most common cause of low PageSpeed scores. A typical website can often gain 10–30 points just from image optimization.
What to do:
loading="lazy" on all images below the fold. Do not use it on above-the-fold images.fetchpriority="high" to your hero or LCP image.Step 2: Eliminate render-blocking resources
Render-blocking resources are CSS and JavaScript files that the browser must download and process before it can display any content. Every render-blocking file delays your First Contentful Paint and LCP.
What to do:
media="print" then swap to media="all" after load.Step 3: Enable caching
Caching is one of the fastest performance wins available. A properly cached page can load in under 200ms for returning visitors.
What to do:
Cache-Control headers on static assets (images, fonts, CSS, JS): aim for max-age=31536000 (one year) with content-addressed filenames.Step 4: Reduce JavaScript
JavaScript is the most expensive resource type on the web. It must be downloaded, parsed, compiled, and executed — all on the main thread.
What to do:
Step 5: Improve server response time (TTFB)
Time to First Byte is the time between a browser making a request and receiving the first byte of the response. Google recommends under 600ms.
What to do:
Step 6: Optimise fonts
Web fonts are a common cause of layout shift and delayed text rendering.
What to do:
font-display: swap so text renders immediately in a system font while the custom font loads.How to track your progress
After making changes, wait 24–48 hours and re-run PageSpeed Insights. Scores can fluctuate between tests, so run three checks and average the results.
Use Loadzen to save your URL and track your score over time. You will see whether changes you ship are moving the needle — and get alerted if a new deploy causes a regression.
Related guide
How to Improve Your PageSpeed Score →Keep reading
Check your own site
Run a free speed check with Loadzen and get a prioritized fix plan for your specific platform.
Run free speed check