WordPress speed

Speed optimization that holds up in production, not just on PageSpeed.

Most WordPress speed gigs chase Lighthouse score and miss the real users. We tune for the metrics that actually move conversion — LCP, CLS, INP — and verify the work against real-user CWV from Search Console, not a synthetic ping from Reston, Virginia.

LCP target

< 2.0s

CLS target

< 0.05

INP target

< 150ms

Verified

Real-user CWV, 30-day soak

What is WordPress speed optimization?

WordPress speed optimization is the practice of measuring real-user Core Web Vitals — LCP, INP, CLS — and fixing them at the source: hosting, theme, plugins, images, fonts, and JavaScript. Cache plugins help; they do not substitute for source-level work.

Why this exists

PageSpeed Insights is not the customer.

Synthetic scores are useful as a smoke test. They do not tell you what an actual visitor on actual 4G in actual traffic experiences. We optimize for real-user Core Web Vitals — the data Google ranks on — and verify gains against Search Console for 30 days post-launch. The Lighthouse score gets better too. That's a side effect.

What we hear most

Common WordPress performance failures we see.

01

LCP is past 3 seconds

Hero image 1MB, no fetchpriority, render-blocking CSS, web font swap on the LCP element. The fix is the render path, not a cache plugin.

02

CLS is in the red

Images without dimensions, fonts swapping, ads or embeds inserted late, hero animation pushing layout. CLS is a discipline problem, not a tool problem.

03

INP is silently bad

JS bundle is 800KB before main-thread is free. Hover effects, sliders, and tracker scripts compete for the long task. INP creeps over 200ms and you cannot tell from PageSpeed alone.

04

Cache plugins are masking bloat

WP Rocket and Object Cache make the home page fast. The product templates, search results, and admin remain slow because the underlying queries are unindexed.

05

Plugin and theme bloat

Forty active plugins, twelve of them loading sitewide that are only needed on one template. Front-end bundle is 2MB before it ships any actual content.

06

Image policy is missing

Uploads land in their original 4000px dimensions. WebP serving is partial. Lazy loading is on by default but applied to the LCP image (a CLS and LCP own goal).

What we deliver

What ships in a Haxtiv WordPress speed engagement.

A diagnosis, a fix, and a verified outcome — not just a one-time push.

Diagnosis

  • Real-user CWV pull from Search Console (CrUX) per template
  • Lab profiles in Lighthouse and WebPageTest with filmstrip
  • Network waterfall analysis on key templates
  • Slow-query log review (slow_log) for the database layer
  • Plugin and theme audit — what's loading where it shouldn't

Render path

  • Critical CSS extracted and inlined per template
  • Render-blocking assets deferred or async-loaded
  • Web fonts subset, preloaded, and swap-controlled
  • JS bundle split, idle-loaded, and tree-shaken
  • LCP element identified and prioritised (fetchpriority, preload)

Image & media

  • AVIF/WebP serving with srcset and sizes
  • Explicit dimensions on every image to eliminate CLS
  • LCP image lazy-loading disabled (a common own goal)
  • Background images converted to picture tags where appropriate
  • Video lazy-loaded and poster-frame optimized

Server & cache

  • Page cache strategy (Cloudflare, host-level, or plugin)
  • Object Cache Pro or Redis where it earns its keep
  • Database hygiene: autoload bloat, transients, post revisions
  • Slow-query rewrites and index additions
  • CDN configured with sensible cache rules

Verification

  • Real-user CWV monitoring for 30 days post-launch
  • Lighthouse and PageSpeed runs across key templates
  • Search Console CWV report watched weekly
  • Performance budget documented in the repo
  • Quarterly tune-up to keep the gains

Process

How this service runs end to end

The same six-step shape we use across every Haxtiv project — adapted to the specifics of this scope.

  1. 01

    Discover

    Audit, intent, and the part nobody is saying out loud

    We open with a working session — not a deck. We pull analytics, crawl the existing site, audit the brand, and interview the people closest to revenue. We surface the friction inside the team, not just the friction on the screen.

  2. 02

    Define

    Sitemap, story, and the metrics that actually matter

    We define the audience journeys, the commercial pages we are willing to defend, the SEO architecture, and the measurable outcomes. You get a shape of the project that survives feedback because it was built on evidence.

  3. 03

    Design

    Editorial system, art-directed, never templated

    Type, grid, motion, and tone built as a system. We design the hero, the long pages, the unloved corners, and the empty states. Every screen looks like it belongs to the same studio. Nothing is parked for later.

  4. 04

    Build

    Production code your team can keep

    WordPress, Shopify, or page builder — we build clean, accessible, performant, and documented. Component-led, naming you'll recognize next year, and a changelog your in-house team can read.

  5. 05

    Launch

    Migration without losing rankings or sleep

    Pre-launch crawl, redirect map, schema and metadata cutover, performance baseline, and a launch playbook. We run the deploy with you, not at you.

  6. 06

    Grow

    Care plan, CRO sprints, and quiet improvements

    We stay involved. Monthly performance reports, security and core updates, and CRO sprints that compound. The site gets better the longer you keep us.

What this looks like in production

Numbers we earn, not numbers we round up.

0+

Sites shipped

across 27 countries

0k

Studio hours

delivered since 2019

0.0x

Avg conversion lift

post-redesign clients

0%

Client retention

into year two

In their words

Senior teams who chose us.

Haxtiv replatformed our marketing site without losing a single ranking. We saw organic leads up 38% inside the first quarter and the editorial team finally has a layout system they don't fight.

Mara Iglesias

VP Marketing · Lumenwave Health

Headless WordPress redesign

Our previous Shopify build was a Frankenstein of apps. The Haxtiv team simplified the stack, rebuilt the PDP and CRO patterns, and our store is faster and more profitable than it has ever been.

Daniel Korver

Founder · Northbound Goods

Shopify Plus rebuild

Frequently asked

Answers worth asking for.

Don't see the question you're holding? Send it to [email protected] and we'll answer the same day.

Yes — typically 20–60 points on mobile depending on starting state. But Lighthouse is a smoke test. The real wins are in real-user LCP, CLS, and INP, which is what Google ranks on and what your visitors actually feel.

Continue reading

Where to go next

Start here

Bring the slow site — we'll bring the diagnosis and the fix.

30-minute call. We'll review the live CWV data, share a fixed quote, and tell you what's worth fixing first.

Book a 30-min call
Send a brief