A GTmetrix score in the red is rarely caused by one thing. It's usually five or six smaller issues stacked on top of each other — and fixing them in the wrong order wastes a lot of time. This is the checklist we run on every project before handoff.
1. Serve images at the size they're displayed
The single biggest win on most sites. A hero image uploaded at 4000px wide and displayed at 1200px is pure waste — modern WordPress handles responsive image sizes automatically once the theme declares the right image sizes.
2. Cut plugins that duplicate what the theme already does
Page builders and multi-purpose plugins often load their own copies of jQuery, icon fonts and animation libraries. A lightweight child theme with semantic markup usually removes the need for most of them.
3. Cache at the page level, not just the browser level
Server-side page caching (or a CDN in front of the site) removes the PHP and database work for repeat visits entirely — this is what usually takes a site from "fast on a good day" to consistently fast.
4. Load fonts and scripts so they don't block rendering
Self-hosting web fonts with proper font-display settings,
and deferring non-critical JavaScript, both reduce the time before a
visitor sees readable content.
"The goal isn't a perfect Lighthouse score in a vacuum — it's a site that still feels fast once it has real content, real plugins, and real traffic."
5. Measure on the same connection your visitors use
A site that loads in 1 second on an office fibre connection can still take 6 seconds on mobile data. We test on a throttled mobile profile in GTmetrix, not just desktop broadband, before calling anything finished.