Performance audit
Fast for real visitors, not just for the test tool.
A slow site costs visitors, conversions and the patience of your editors. I measure where the time goes, from the database query to the last image, and fix the causes instead of stacking caching plugins.
When it is time
Sounds familiar?
- Pages feel slow although a caching plugin is active
- Every click in the admin takes seconds, and editors complain
- The Core Web Vitals in Search Console are amber or red
- Traffic peaks bring the server to its knees
The audit
What I check.
Remote and read-only. You get a written report with every finding, its risk and the effort to fix it.
- Server response time, with and without page cache
- Database: slow queries, missing indexes, autoloaded options, bloated meta tables
- Object cache and transients: used, misused or missing
- Plugins and themes that load code on every request
- Assets: scripts, styles, fonts and images, and what blocks rendering
- Core Web Vitals from real-user data, where available
- External HTTP calls, cron jobs and background processing
- Hosting: PHP version, OPcache, web server and CDN
Start with the free check: it already tests the response time of your front page. Seconds, no access needed.
The fix sprint
What a sprint typically closes.
Fixed scope and price, agreed before we start. Every change arrives as a pull request that you review and merge.
- Cache what can be cached, at the right layer
- Rewrite the slowest queries and add indexes where they belong
- Clean up autoloaded options and orphaned data
- Load scripts and styles only where they are needed
- Move heavy work out of the page request into background jobs
FAQ
Questions I get asked.
Will you just install a caching plugin?
No. Caching hides problems until the cache is empty or the visitor is logged in. I fix the slow parts first, then add caching where it pays off.
How do you prove it got faster?
We measure before and after, with the same pages and the same tools. The numbers are part of the report.
Do you also optimize WooCommerce shops?
Yes. Cart, checkout and logged-in customers cannot be cached like a blog, so the work happens in queries, hooks and background jobs.
Let’s make your WordPress boring. In the best way.
Tell me about your site. You get an honest answer, even if it is “you don’t need me”.