Luxury train operator revenue rises by £45,384 when page load drops from 5s to 1s (modelled estimate). Try the slow website cost calculator

Free audit

WordPress SEO audit and Core Web Vitals report

A website performance audit that treats speed as part of technical SEO. Check your Lighthouse score, see which Core Web Vitals are failing and get the WordPress-specific fixes — plus the estimated carbon footprint the same page weight produces.

Live Google Lighthouse data. No account needed to see your scores.

What a good Lighthouse score looks like

  • 90–100 good. Judge yourself on the mobile score, not desktop.
  • 50–89 needs work. Where most WordPress sites sit before optimisation.
  • 0–49 poor. Usually images and JavaScript rather than anything exotic.
  • Lab vs field. Lighthouse is a lab test; Google ranks on 28 days of real-visitor field data.

These figures are modelled estimates and should not be interpreted as direct measurements of electricity use or greenhouse gas emissions.

Core Web Vitals

How to improve Core Web Vitals on WordPress

Three metrics decide your page-experience signal. Each one has its own causes and its own fixes, so the audit reports them separately rather than averaging them away.

Under 2.5 seconds

LCP — Largest Contentful Paint

How quickly the main content appears. On WordPress the usual causes of a slow LCP are an unoptimised hero image, render-blocking theme CSS and slow time to first byte.

  • Serve the hero image as WebP or AVIF at the displayed size
  • Preload the LCP image and stop lazy-loading it
  • Inline critical CSS and defer the rest of the theme stylesheet
  • Add server-level page caching so PHP is not invoked per request
Under 0.1

CLS — Cumulative Layout Shift

How much the layout jumps while loading. Almost always caused by images without dimensions, late-loading fonts, or ad and embed slots with no reserved space.

  • Set explicit width and height on every image and iframe
  • Reserve fixed space for ads, cookie banners and embeds
  • Use font-display: swap with a matched fallback metric
  • Avoid injecting banners above existing content after load
Under 200 milliseconds

INP — Interaction to Next Paint

How fast the page responds to taps and clicks. Driven by how much JavaScript the main thread has to execute, which on WordPress usually means page builders and plugin bundles.

  • Dequeue plugin scripts on templates that do not use them
  • Defer non-critical JavaScript and break up long tasks
  • Load chat widgets and tag managers after interaction
  • Reduce the number of plugins running site-wide

Report contents

What the WordPress audit reports

Four Lighthouse categories

Performance, Accessibility, Best Practices and SEO scores, captured on mobile and desktop from Google PageSpeed Insights.

Core Web Vitals with targets

LCP, CLS and INP against Google's thresholds, so you can see which specific metric is failing rather than a single blended number.

Page weight and request breakdown

Total transfer split by images, scripts, stylesheets, fonts and other resources — the fastest way to see what is actually costing you.

Estimated CO2e per pageview

A modelled emissions figure derived from the same transfer data, with an efficiency grade for context.

Prioritised fixes

Each finding turned into a WordPress-specific action, ordered by impact against effort.

Tracked re-scans

Scheduled re-checks on tracked sites so regressions from plugin updates and new pages surface automatically.

Common questions

WordPress SEO audit FAQs

Audit your WordPress site now

Lighthouse scores, Core Web Vitals, page weight and estimated emissions in one report.