“We’ll do a speed audit” can mean very different things. At one end, someone runs your homepage through a free testing tool, takes a screenshot of the score and sends you a list of generic suggestions. At the other, a specialist investigates exactly what happens when real people load your pages, finds the causes of slowness and gives you a prioritized plan with expected results.
Both get called an audit. Only one is worth paying for. This post explains what a proper website speed audit involves, what you should receive at the end and how to tell the difference.
What a proper audit sets out to answer
A useful speed audit answers four questions:
- How fast does your site feel to real visitors on the devices and connections they actually use?
- Which pages matter most, and how do they perform?
- What exactly is causing the slowness?
- What should be fixed first, and what improvement can you expect?
Everything in the audit should serve those questions.
Step 1: Understanding your business and your pages
Speed matters most on the pages that drive your business: often the homepage, key service pages, landing pages for ads and the contact or booking page. A good audit starts by identifying those, along with where your visitors come from and which devices they use, usually from your analytics.
Auditing only the homepage is a common shortcut, and it often misses the pages where customers actually decide.
Step 2: Real-world data
Google collects anonymous speed measurements from real Chrome users, published as the Chrome User Experience Report. If your site has enough traffic, PageSpeed Insights and Google Search Console show this data for your pages and your site as a whole.
This is important because it reflects actual visitors, not a single test. A proper audit looks at your Core Web Vitals here:
- Largest Contentful Paint (LCP): how quickly the main content appears.
- Interaction to Next Paint (INP): how quickly the page responds to taps and clicks.
- Cumulative Layout Shift (CLS): how much the page jumps around while loading.
Step 3: Lab testing and diagnosis
Next come controlled tests, repeated under consistent conditions, typically simulating a mid-range phone on a mobile connection. These help diagnose causes. A thorough audit goes beyond the summary score and examines:
- Server response time: how long your hosting takes to begin sending the page.
- The loading sequence: what loads, in what order, and what blocks the page from appearing.
- Page weight: images, scripts, fonts and other files, and which are largest.
- JavaScript cost: which scripts keep the browser busy and delay responsiveness.
- Third-party code: analytics, chat, advertising, video embeds and social widgets.
- Layout shifts: which elements move and why.
- Caching: whether pages and files are cached effectively, at the server and in the browser.
Step 4: Looking under the hood
For WordPress sites, the most valuable findings often come from inside the site:
- Plugins: which add weight to pages or slow down the server, and which load where they’re not needed.
- Theme and page builder: how much overhead they add.
- Database: bloat from old revisions, logs and leftover data from removed plugins.
- Hosting: server resources, PHP version and configuration.
- Images and media: sizes, formats and how they’re delivered.
This is where generic tools stop and expertise starts. A tool can tell you a page has too much JavaScript. An audit tells you which plugin is responsible and whether you can safely remove it.
Step 5: The plan
The output of a good audit isn’t a score. It’s a plan:
- Findings explained in plain language, including why each matters to your business.
- Prioritized recommendations, ordered by impact and effort, so quick wins come first.
- Realistic expectations for what each change should achieve.
- Risks and trade-offs, such as a feature you might need to drop or replace.
- A baseline of current measurements, so improvements can be proven afterwards.
How to spot a weak audit
Be cautious if the “audit”:
- Only covers the homepage.
- Is mostly a screenshot of a score, without real-world data.
- Lists generic advice that could apply to any website.
- Doesn’t mention your specific plugins, theme or hosting.
- Promises a perfect score rather than better results for real visitors.
- Doesn’t explain how improvements will be measured.
What happens after the audit
The best audits lead to action. Fixes are made, ideally on a staging copy first, then measured against the baseline. Real-world data takes a few weeks to fully reflect improvements, because it’s based on a rolling 28-day window of visits. Ongoing monitoring then makes sure the site doesn’t slowly slide back as new content and features are added.
How much of your time it takes
A good audit shouldn’t demand much of your time. Expect a short conversation at the start about your business, your most important pages and any known problems, plus temporary access to your analytics, Search Console and possibly a staging copy of the site. At the end, there should be a walkthrough of the findings in plain language, with time for questions. Everything in between is the auditor’s work, not yours.
The takeaway
A real speed audit measures what your visitors actually experience on the pages that matter, diagnoses specific causes inside your site and hosting, and ends with a prioritized plan and a baseline to prove results. A score screenshot is a starting point, not an audit.
Performance is our specialty. If you’d like a proper audit of your WordPress site, with findings in plain language and a clear plan, get in touch.