Skip to content
Oh My Web

WordPress speed optimization service — Core Web Vitals green, or you do not pay.

A fixed-fee sprint at ₹19,999 / $299 that takes a WordPress site to a largest-contentful-paint under two seconds, no layout shift and a passing Core Web Vitals grade — with the before and after measured rather than asserted. If the template we optimise does not pass afterwards, you do not pay.

Start with the free audit

Speed, security and plugin report, emailed in about ten minutes. No call, no obligation, and it tells you whether you need this at all.

Optional. Only if you would rather we called.

We use it to send the report and nothing else. If the answer is “install a caching plugin and resize four images”, that is what the reply will say.

Diagnosis

Where WordPress sites actually lose their time

Six causes cover almost every slow site we look at, and only two of them are the ones people expect.

  • Hero images nobody resized

    A 2 MB photograph served at four times the size it is displayed. Routinely a second or more of largest-contentful-paint on its own, and the easiest thing on this list to fix.

  • Render-blocking builder CSS

    Elementor and Divi ship large stylesheets that must download and parse before anything paints. On a mid-range phone that is often several hundred milliseconds before the page starts existing.

  • Forty plugins, each loading assets

    Most plugins load their CSS and JavaScript on every page, including the ones where they do nothing. The count matters more than any single plugin does.

  • No object cache

    Every page view re-running the same database queries. On a busy or query-heavy site this is the difference between a fast server and a slow site.

  • Shared-host time to first byte

    If the server takes 800 ms to send the first byte, nothing you do in the browser gets that back. This is the one the plugins cannot touch.

  • Third-party scripts

    Chat widgets, tag managers, tracking pixels and embeds, each fetching from someone else's server on someone else's schedule.

The sprint

What we change, and what we measure against

Eight areas, worked in order of return, on a staging copy — then measured with a lab test and with field data where there is enough traffic to have any.

Images
Converted to WebP or AVIF, sized for the slot they occupy, lazy-loaded below the fold, and given explicit dimensions so nothing shifts.
Critical CSS
The styles needed for the first screen inlined, the rest deferred, so the page paints before the stylesheet finishes.
JavaScript audit
Everything deferred or made async unless it genuinely has to block. Anything loading on pages that do not use it is stopped from doing so.
Plugin audit
What is installed, what it loads, what it is for. Removals proposed with reasoning, and nothing removed without your approval.
Object and page caching
Redis where the host permits it, a page cache in front, and a CDN so the assets are not crossing an ocean each time.
Fonts
Subset to the characters you use, self-hosted where licensing allows, and given a display strategy so text is readable while they load.
Database
Revisions, expired transients and orphaned metadata cleared, and the tables that matter indexed properly.
PHP and server
Moved to a current PHP version, with server-level tuning if the site is on hosting we run.

The targets

Largest contentful paint
Under 2.0 seconds on a throttled mobile test
Cumulative layout shift
Zero — every image and embed given explicit dimensions
Interaction to next paint
Under 200 milliseconds
Lighthouse performance
95 or better, mobile preset

These are the same targets we hold this site to, measured the same way. You get the before and after numbers, not a screenshot of a desktop score.

Price and guarantee

₹19,999 / $299, fixed. If the template we optimise does not pass Core Web Vitals afterwards, you do not pay — the full terms are in the refund policy.

One honest caveat: a server we do not control can make that impossible. If your host’s response time is the ceiling, we tell you before taking the job rather than taking the fee and failing — and moving the site is often the cheaper fix.

Keeping it fast

Speed decays. Every image somebody uploads at full size, every plugin added and forgotten, every new embed takes a little back. A site optimised once and left alone is measurably slower in a year.

Care Pro and Growth include a speed pass every quarter, which is why this sprint is free on both — the one-off exists for sites that are not on a plan.

Questions

Speed questions, answered

How can I optimise a WordPress site for speed?

In order of return: fix the images, cut the plugin count, put a page cache and a CDN in front, defer the JavaScript that does not need to block, and check what your server's time to first byte actually is. The first two usually account for most of the gain, and neither requires buying anything.

Is there a free WordPress speed optimisation plugin?

Several, and they are good. WP-Optimize and LiteSpeed Cache are free and cover caching, image compression and database cleanup; WP Fastest Cache has a free tier. If your site is a reasonably standard theme with a sensible plugin count, one of those plus resized images will get you a long way for nothing.

So when is it worth paying someone?

When you have already installed a caching plugin and the numbers barely moved. That usually means the problem is somewhere a plugin cannot reach: server response time, a page builder's stylesheet, a plugin count no cache can rescue, or third-party scripts. Fighting that with settings costs more hours than hiring costs money.

Will this break my site?

It is done on a staging copy first, every time, with the live site untouched until you have looked at the copy. Aggressive optimisation can break things — that is exactly why it is not done live. Anything we cannot make safe, we do not do, and we tell you what we left on the table and why.

Do you work on WooCommerce?

Yes, and stores are where this pays back fastest. They also need more care: cart and checkout pages cannot be cached the way a blog post can, and getting that wrong causes the kind of bug that shows up as lost orders rather than as an error.

How long does it take?

About a week for a standard site, including the staging build, your review and the before-and-after measurements. We measure with a lab test and with field data where the site has enough traffic to have any, because a lab score on its own is a number rather than an experience.

Find out what is actually slow first.

The free audit takes about ten minutes and tells you where the time is going. Sometimes the answer is a plugin you can install yourself, and we would rather say that than sell you a sprint you do not need.