No page or object cache
Every visit rebuilds the page and re-queries the database. On a modest host that alone can add a second or more to TTFB.
Performance
Not another caching plugin stacked on three others. A measured pass at the server, the database and the assets that actually block rendering.
Most “speed optimization” is a plugin with a score. The score goes up, the site still feels slow, and checkout still takes four seconds. Real gains come from the layer that is actually failing: slow TTFB on an overloaded shared host, a bloated options table autoloaded on every request, images served at 4000px, or a chat widget blocking the main thread.
I start with field data and a waterfall, decide which layer is responsible, and fix that. Then I measure again under the same conditions. You get before-and-after numbers for the metrics that affect rankings and revenue, not a screenshot of a green circle.
Every visit rebuilds the page and re-queries the database. On a modest host that alone can add a second or more to TTFB.
Plugins leave rows behind. When autoload data reaches megabytes, every request pays for it — including admin and AJAX.
Five stylesheets, three jQuery plugins, two font families and a chat widget in the head. The browser cannot paint until it has parsed them all.
Full-resolution uploads scaled by CSS, missing modern formats, and font files with no subset or preload. This is the usual cause of a weak LCP.
No opcache, old PHP, throttled CPU, or a shared plan with noisy neighbours. No front-end trick fixes a server that cannot answer in time.
Field data where available, lab data for repeatability, and server timing for TTFB. One set of numbers to compare against later.
Current PHP with opcache, sensible memory, page cache at the right level, and object cache where the database is the bottleneck.
Each script and stylesheet accounted for, deferred, split or removed. Unused plugins deleted rather than deactivated.
Revisions, expired transients, orphaned metadata and autoload bloat — with a backup and a reversible plan.
Correct dimensions, WebP or AVIF, lazy loading below the fold, priority hints on the LCP element, subset fonts with swap.
Same tests, same conditions, documented settings so the next plugin install does not quietly undo the work.
Speed is one input among many, and Core Web Vitals behaves more like a tie-breaker than a lever on its own. Faster pages reliably improve conversion and crawl efficiency, which is the durable win. I will not promise a position change from speed alone.
Yes. Front-end work happens on a staging copy first, is compared side by side, and is pushed only when layout and functionality match.
Sometimes. If TTFB cannot be fixed on the current plan, I will say so and quote a move separately. Moving hosts to avoid optimizing is usually the more expensive route.
A focused pass is typically one to three working days depending on size and how many third-party scripts are involved. Large WooCommerce catalogues take longer to test properly.
No, and anyone who does is gaming a lab test. Third-party scripts and real devices cap what a score can show. I commit to measured improvement in the metrics that matter and an honest account of what remains.
Speed & Core Web Vitals
A short diagnosis is free. If the fault is outside this service, you will be told which one applies — or that the site is not worth repairing.
Or email hello@wordpressfixe.com — first reply within 1 business day.