WordPress speed optimization that fixes the cause, not the score
A page-speed score is a symptom. Fast when cached and 40 seconds when not is an object-cache problem. Autoloader frames in the slow log are OPcache, not SQL. We read the layer that is actually failing before we install anything.
What the work is
Four things, each of which produces a number you can check on your own site afterwards.
Autoload and options audit
The per-request payload every uncached page hauls. On one store this was 276,000 rows before we touched a theme file.
Object cache and OPcache
Sized properly. A buffer pool at 5× available RAM was OOM-killing MySQL every 40 minutes on one server — the symptom read as “the site is slow”.
Edge and page cache, ordered correctly
Last matching rule wins at Cloudflare, so a bypass above a cache-all rule silently caches carts. We test with cache busting, every time.
Core Web Vitals and INP
Field data from CrUX, not a lab score. Lazy-loading inside display:none never loads — that is why the carousel spins forever.
The plugin installed to make the site faster was the entire reason it was slow
Cached pages returned in 0.27 seconds. Uncached ones took 24 to 46. Anyone spot-checking the homepage saw a perfectly fast site.
WooCommerce store on oversubscribed shared hosting · host load average 60–90
Read the full case study| Measurement | Before | After | Change |
|---|---|---|---|
| 2,000 cache writes | 703 ms | 2.5 ms | -99.6% |
| Cache files on disk | 251 MB | 0 MB | -100% |
Five jobs. Every month. Each one counted.
Retainers bundle all five. Any one of them can also be bought once, as a single measured pass with a before column and an after column.
Plans priced on the work,
not on the checklist
Month to month, no lock-in. Prices are per site, per month, exclusive of GST. Portfolios and multi-site estates are quoted on the estate.
For a site that just needs to stay up, patched and backed up
For a store where slow pages are costing orders
Running a portfolio you cannot afford to have go quiet? Managed starts from ₹17,999/mo.
The questions
everyone asks first
Straight answers, including the ones about price, access and what we will not do.
Updates, backups, uptime and security are the floor — every plan has those. What separates a retainer from a host's support desk is the measured work underneath: autoload and database health, object cache sizing, bot policy, disk audits, and a quarterly report with a before-and-after column. Your host will never do any of that, because none of it is their responsibility.