What a WordPress Speed Audit Actually Measures

Lab scores on the homepage are a vanity metric. Here is the audit we run on templates shoppers and editors actually open.

Lab scores on the homepage are a vanity metric. A WordPress speed audit worth paying for names templates, the LCP element on each, third-party scripts, and a list of plugins that earn their keep. We do this as part of WordPress speed optimization and store work.

If a vendor only sends a screenshot of PageSpeed Insights on /, you bought a PDF, not an audit.

Templates, not a single URL

We open the URLs people actually use: a landing page from ads, a category or blog index, a single post or product, and the template that has the builder. Each gets a field pass on a mid-range phone. The LCP element is written down. If it is a lazy image or a font, that is the first ticket.

Stores add cart and checkout. We already argued that category pages come first. The audit is how we prove it.

What we count

Requests, bytes, and main-thread time. TTFB vs front-end. Image inventory: unscaled uploads, missing srcset, decorative SVGs loaded as 2x PNGs. Fonts: families, weights, whether heading text is the LCP. JS: theme, builder, plugins, tag manager. CSS: builder CSS that loaded site-wide for a widget on one page.

Plugins: last updated, whether they load globally, whether a lighter replacement exists. Hosting: PHP version, object cache, page cache rules, and whether the origin is in the region of the audience. CDN: only if it is configured for the actual HTML and assets, not a checkbox.

What we do not count as a win

A cache plugin installed without exceptions for carts. A “delay JavaScript” toggle that breaks the menu. Swapping to a new theme as the first move when the problem is a page-builder stack on every archive. Those are how sites get faster in the lab and broken in production.

Deliverable

A written list, ordered by impact vs risk, with before numbers on the measured URLs. Implementation can be us or your team. Maintenance afterwards is how it stays — WordPress maintenance. If Elementor is the bottleneck, that can be a builder diet or Elementor development with a pattern library, not more add-ons.

Bring the URLs and access on a free consultation. If WordPress is the wrong tool entirely, we will say so — when WordPress is the wrong tool.