Speed Optimization

Managed service

When the baseline isn't enough

Every WebOps hosting plan ships with a conservative LiteSpeed + QUIC.cloud baseline that's universally safe for any WordPress site. Speed Optimization adds per-site tuning on top, for sites where the baseline leaves real Lighthouse points on the table.

  • Monthly 3-run PSI median
  • Post-update regression check
  • Per-cycle configuration tweaks
  • Plain-language monthly report
Book a discovery call

Baseline included with hosting documented here.

What's included

A measured tuning cycle, every month

The same shape of work we already do for security on top of the baseline. Quiet, recurring, reported in plain language.

Monthly PSI median

A 3-run PageSpeed Insights median on your homepage, captured the same day every month. Trend over time, not a single snapshot you can't trust.

Post-update regression check

After every plugin or theme update we run the speed harness again. If something dropped, we know about it before your visitors do.

Light tweaks per cycle

Per-cycle adjustments to the LiteSpeed configuration, image delivery, defer rules, and cache TTLs based on what the month's measurement actually shows.

Initial audit and baseline

Onboarding starts with a per-page audit, a before/after PSI report, and a 30-day re-check to confirm the tuning held.

Plain-language report

Every cycle ends with a short written report. What we measured, what we changed, what to expect next month. No screenshots-of-Lighthouse dumps.

Continuous monitoring

Between cycles, synthetic monitoring catches large speed regressions and surfaces them as a ticket instead of waiting for the monthly check.

From the fleet

Why this work has to be per-site

Earlier this year, one client on our fleet kept reporting that editing posts in their page builder would intermittently break the site layout. We chased the obvious causes for weeks. The real culprit turned out to be a LiteSpeed CSS optimization setting that ships ON by default and conflicts with most page builders. Flipping it off solved the recurring incident.

We then audited the same setting across all 122 WordPress installs on the fleet. Two more sites had the same latent risk, even though those owners hadn't reported a problem yet.

The same week, we tested a different LiteSpeed flag on two sites belonging to the same client. On the first site, here's what the 3-run median picked up:

+59
mobile PSI points
(38 → 97)
0.567 → 0
Cumulative Layout Shift
to actual zero
−31
mobile PSI points
same flag, second site

The second site ran a hero slider on the homepage. Same hosting stack, same setting, opposite outcomes. That's why the conservative baseline stays conservative for everyone, and why the aggressive optimizations live in a paid service that earns the right to make per-site changes by measuring before and after.

Scope boundary

What's not in the service

To keep the recurring cost honest, larger one-off work lives outside the monthly subscription. We'll quote it separately as a project.

Per-URL critical CSS tuning

Generating and stabilizing per-page Critical CSS or Used CSS across a deep site is a multi-day project, not a monthly tweak. We'll quote it as scope.

Custom plugin or theme snippets

Hand-written PHP or JavaScript to defer specific scripts, conditionally load assets, or rework a render path is project work. Bill at our dev rate.

Heavy front-end refactors

If the homepage is genuinely too heavy at the source (a hero slider with eight uncompressed full-bleed images, a builder template stacked with widgets), the fix is design, not configuration. We can help, scoped as a build.

Third-party script renegotiation

Marketing pixels, chat widgets, and ad tags that drag scores down often need an honest conversation with the team that put them there. We can lead it, scoped separately.

Pricing

Attach Speed Optimization to your hosting

A single managed tier, recurring monthly. We add it to your site after a quick scoping call.

Already a WebOps client? Talk to us about adding it. Not hosted with us yet? A one-time tune-up audit on your current host runs $200–$300; ask us about scope.

Common questions

Frequently asked questions

Every hosting plan ships with a conservative LiteSpeed and QUIC.cloud baseline that's safe for any WordPress site. See the baseline features. Speed Optimization is per-site tuning on top: aggressive optimizations that need per-site validation before they can ship safely.
We don't promise a specific number. We promise the process: monthly measurement, regression check, and per-cycle tweaks. The honest answer for your site might be a 20-point gain. It might also be that you're already as fast as the page composition allows, and the value of the service is the regression catch when a plugin update drops a metric.
Yes. We add it to your site after a quick scoping call. No setup fee, prorated to your hosting renewal date.
If the initial audit surfaces work that exceeds the recurring scope (per-URL CCSS tuning, custom snippets, a heavy front-end refactor), we'll flag it in the audit and quote it as a separate project. The recurring service covers what fits in a monthly cycle.
For the recurring service, yes. The tuning depends on the LiteSpeed Enterprise + QUIC.cloud stack we run on our own servers. If you're on another host, ask us about a one-time tune-up audit ($200–$300) on your current setup.
Anytime, just let us know. Your hosting plan continues with the baseline configuration; the aggressive optimizations roll back to defaults at the end of the billing cycle.

Find out where your site's real bottlenecks are

The free Website Health Report runs the same speed harness we use on day one of every service engagement. It's the cheapest way to find out whether your site has a 30-point Lighthouse gain hiding behind two settings nobody has tested in two years.

No setup fee Cancel anytime 30-day money back