The work combined Core Web Vitals data, laboratory tests, network waterfalls, source code and behaviour on devices. A cache plugin cannot resolve every issue.
Why can an older site remain slow with caching?
There was no single cause across the sites. Theme assets, page builders, globally loaded libraries, repeated images, external widgets, missing media dimensions, unsuitable lazy loading and page-specific code loaded everywhere all contributed.
Some projects also involved Chrome and Firefox differences, mobile-menu failures, poorly cropped hero images and changes that improved test scores while breaking functionality.
Diagnosis: from user data to a specific resource
Field data
Core Web Vitals and real-user issues where the website had sufficient field data.
Laboratory tests
PageSpeed Insights and Lighthouse helped reproduce issues, but their score was not treated as the only KPI.
Network waterfall and loading order
Identifying render-blocking resources, heavy fonts, LCP images and third-party scripts.
Theme and plugin review
Assessing necessary components, conflicts and limitations caused by theme architecture.
Functional tests
Menus, forms, galleries, consent, checkout and behaviour across browsers and screen widths.
A method based on identified bottlenecks
Start with the largest bottleneck
Priority went to the cause of LCP delays, long tasks or large transfers rather than every tool warning.
Reversible changes
Each stage was tested separately so its effect could be identified and conflicts reversed.
Mobile as a core scenario
Hero sections, menus, forms and content were checked on narrow screens with mobile-first indexing in mind.
Clear limitations
Where the main constraint was an old, heavy theme, the report explained the cost of continued patching and when a rebuild might be more appropriate.
Common implementation work
- defer or conditionally load non-critical scripts,
- remove unnecessary embeds and heavy widgets,
- configure caching, minification and bundling only where they do not cause conflicts,
- correct lazy loading and LCP-image priority,
- replace or compress large graphics and set suitable dimensions,
- stabilise hero sections, headings and fonts across browsers,
- repair mobile navigation and interactive elements,
- reduce duplicate images and unnecessary global code,
- review technical updates, canonicals, sitemaps and indexing issues.
Sources used
- Google Search Console and Core Web Vitals reports,
- PageSpeed Insights / Lighthouse,
- browser developer tools and network waterfalls,
- Chrome, Firefox and mobile tests,
- HTML, CSS, JavaScript and cache-configuration reviews.
Aggregate outcomes
Main bottlenecks addressed
The largest resources and unsuitable loading priorities no longer dominated initial loading in the reviewed implementations.
A more stable mobile experience
Menus, hero sections and layouts behaved more consistently across tested widths and browsers.
A clearer technical decision
Clients received an explanation of what could be optimised and what could not reasonably be fixed without changing the theme.
I do not publish invented 100/100 claims. Some projects showed substantial laboratory-score improvements, but stability, LCP, functionality and avoiding regressions were more important.
Lessons for website owners
- Caching cannot fix a heavy theme architecture by itself.
- A high test score does not guarantee a good user experience.
- Optimisation needs to cover mobile and actual website features.
- JavaScript changes should be introduced in stages and regression-tested.
- A rebuild can sometimes be more economical than continuing to patch an old implementation.
FREQUENTLY ASKED QUESTIONS
Can WordPress be made faster without changing the theme?
Often, but the scope depends on the theme and page builder. The main constraints should be identified before work begins.
Should the PageSpeed score be the goal?
It should be a diagnostic signal. The goal is a fast, stable, usable website that retains its functionality.
Is it safe to defer every script?
No. It can break menus, forms, galleries and measurement. Loading order and dependencies need testing.

