WordPress

How Fast Is Your WordPress Site?

WordPress powers over 40% of the web, which means most slow websites are WordPress websites too. Run your site below to see which fix matters most — then check how your stack compares against millions of real WordPress origins.

WordPress Core Web Vitals: What the Field Data Shows

Real-user performance of every measured WordPress origin, from the Chrome UX Report (May 2026).

49.3%of WordPress sites pass all three Core Web Vitals on mobile

LCP

56.4%

INP

91.3%

CLS

86.9%

TTFB

24.8%

FCP

44.5%

Share of origins with a good score per metric (mobile, 2,872,480 WordPress origins measured). Data: May 2026, HTTP Archive Core Web Vitals Technology Report / Chrome UX Report.

The data points at one dominant culprit: server response time. WordPress renders pages with PHP and MySQL on every uncached request, and on budget shared hosting that alone can consume most of your LCP budget before the browser receives a single byte. Sites that combine full-page caching with a decent host routinely jump from the failing half into the passing half of these charts.

The 3 Most Common WordPress Performance Bottlenecks

1.Slow server response time (TTFB)

TTFB is by far WordPress's weakest metric — barely a quarter of WordPress sites respond fast enough on mobile. Every uncached page view executes PHP and hits the database, so cheap shared hosting and cache-less setups pay the full cost on every visit.

How to fix it: Enable full-page caching (a host-level cache like LiteSpeed/Varnish, or a plugin such as WP Rocket / W3 Total Cache), add a persistent object cache (Redis) for logged-in traffic, and if TTFB is still above ~800 ms, move to a better host or put a CDN in front.

# Check whether full-page caching is actually working:
curl -sI https://example.com | grep -iE "x-cache|x-litespeed-cache|cf-cache-status"
# A HIT on repeat requests means the cache is serving pages.

2.Render-blocking plugin CSS and JavaScript

Each active plugin can enqueue its own stylesheets and scripts on every page — even pages that never use the feature. The result is a long queue of render-blocking requests that delays FCP and LCP.

How to fix it: Audit your plugin list and remove what you don't use. For the rest, load non-critical scripts with defer — WordPress 6.3+ supports this natively via the loading-strategy argument when registering scripts — and use an asset manager (e.g. Asset CleanUp or Perfmatters) to unload plugin assets on pages that don't need them.

// functions.php — WordPress 6.3+: register your script with the defer strategy
wp_register_script(
    'my-theme-script',
    get_template_directory_uri() . '/js/my-script.js',
    array(),
    '1.0',
    array( 'strategy' => 'defer' )
);

3.Unoptimized hero images hurting LCP

Theme hero banners and featured images are the LCP element on most WordPress pages. Full-size JPEGs, missing dimensions, and lazy-loading the above-the-fold image all push LCP past the 2.5 s threshold.

How to fix it: Serve WebP/AVIF (WordPress supports WebP natively since 5.8), always set width/height so space is reserved, and make sure the hero image is NOT lazy-loaded — give it fetchpriority="high" instead. WordPress 6.3+ does this automatically for many themes.

<!-- The LCP image: eager + high priority, with explicit dimensions -->
<img src="hero.webp" width="1200" height="600"
     fetchpriority="high" decoding="async" alt="...">

Frequently Asked Questions

Why is my WordPress site still slow with a caching plugin?

Page caching only helps repeat, anonymous page views. If your TTFB is still high, the cache may be missing (check response headers), or the bottleneck is elsewhere: slow hosting, render-blocking plugin assets, or an unoptimized hero image. Run the analyzer above — it tells you which one to fix first.

How many WordPress sites actually pass Core Web Vitals?

About half of measured WordPress origins pass all three Core Web Vitals on mobile, according to HTTP Archive / Chrome UX Report data. The biggest gap versus other platforms is server response time (TTFB), which is mostly a hosting and caching problem rather than a theme problem.