Prompt
Why are my page speed scores still bad after compressing images?
Latest observation
Compressing images helps, but it’s usually only one piece of page speed. Your scores can still be bad because other parts of the page are slower or heavier than the images.
Common reasons:
-
Too much JavaScript
Large or poorly optimized scripts can block rendering, delay interaction, and hurt Lighthouse/PageSpeed scores. -
Render-blocking CSS and JS
If stylesheets or scripts load before the page can paint, the browser waits. -
Too many requests
Even if images are smaller, having lots of files, fonts, icons, and third-party scripts still adds overhead. -
Large CSS files / unused CSS
Big stylesheets or lots of unused rules increase download and processing time. -
Web fonts
Custom fonts can delay text rendering and cause layout shifts. -
Third-party scripts
Analytics, ads, chat widgets, tag managers, and embedded content often slow pages a lot. -
High TTFB / slow server response
If the server is slow to respond, the browser starts late no matter how optimized the images are. -
Large DOM or complex layout
Too many elements or heavy page structure can slow browser rendering. -
Images not fully optimized for delivery
Compressing alone doesn’t always help if:- images are still larger than needed
- they aren’t responsive (
srcset) - they load too early
- they aren’t lazy-loaded below the fold
- they’re in the wrong format (e.g. PNG instead of WebP/AVIF)
-
Caching issues
If assets aren’t cached well, repeat visits stay slow.
What to check next:
- Run PageSpeed Insights and look at the specific opportunities.
- Check Largest Contentful Paint (LCP), Total Blocking Time (TBT), and Cumulative Layout Shift (CLS).
- Audit:
- JS bundle size
- unused CSS
- third-party scripts
- server response time
- font loading
- Use browser DevTools waterfall to see what actually delays loading.
If you want, I can help you interpret a PageSpeed report if you paste the results or URL.