What Your Free SEO Report Shows (and What to Fix First)
A free SEO report is only useful if it tells you what to do on Monday morning. This guide walks through every part of the free report we send, from the overall score to the seven-day expiry, explains what each part tells you and why it matters, and then sets out the order we would fix things in if the site were ours.
We also share what 829 of these reports have shown in aggregate, so you can see whether your result is unusual or entirely typical. Every figure on the report, and in this article, comes from a measurement. Where a measurement has limits, we say so.
What is in the report, part by part
The report is generated automatically from a crawl of your key pages and Google's own PageSpeed Insights tests. Nothing on it is estimated from industry averages, and there is no traffic or revenue projection, because we do not have your Search Console data at that stage.
The overall score and grade
The headline is a score from 0 to 100 and a letter grade from A to F. The score combines Google's own lab tests of your site with the technical and content issues we find, so it reflects both how the site performs and how well it is set up for search.
Treat the grade as a summary, not a verdict. An A means we found little to fix from the outside; a C or below means problems that are very likely costing visibility. The useful information sits underneath it, in the issues and the measured facts. If Google's tests cannot run against your site, the report says that performance data was unavailable rather than inventing it.
The worst issue
The report leads with the single issue we consider most damaging for your site, followed by the other important issues we found. They fall into a few families:
- Speed and mobile experience: how quickly the site loads and how well it performs on a phone.
- Security: whether the site is served over HTTPS.
- Crawlability: whether robots.txt and the sitemap let Google find your pages.
- On-page basics: titles and meta descriptions, including missing or duplicated ones.
- Content depth: key pages too thin to answer a buyer's questions.
The worst issue is where we would start. Everything else is ordered behind it.
The measured fact: load time against 2.5 seconds
Every report carries one concrete, checkable number: how long your homepage took to load, compared with Google's 2.5-second "good" threshold for Largest Contentful Paint. We show the real comparison, so a 7.5-second page is reported as three times slower than recommended, not rounded into a vague bucket.
Google's Core Web Vitals guidance sets the "good" LCP threshold at 2.5 seconds at the 75th percentile of page loads. That is the benchmark we compare against, and you can check your own figure in PageSpeed Insights at any time.
Lighthouse scores and Core Web Vitals
Below the headline you will find Google's four Lighthouse category scores (Performance, Accessibility, SEO and Best Practices) and a Core Web Vitals strip showing LCP, INP, CLS, First Contentful Paint and Time to First Byte. Google counts a page as passing when LCP is at or under 2.5 seconds, INP at or under 200 milliseconds and CLS at or under 0.1. If you want the detail behind each metric, our Core Web Vitals optimisation guide covers them one by one.
Quick wins
Quick wins are small, independent improvements that suit your site's results, such as optimising images, enabling compression, trimming JavaScript or improving the mobile layout. Each carries a typical effort estimate in minutes, not a promised uplift.
We removed per-site "you will gain X%" claims from quick wins earlier this year. Nobody can know a specific site's uplift before doing the work, so the report no longer pretends to.
The projected score
The projected score shows roughly where your score would land if the issues on the report were fixed. It is deliberately conservative: it credits only the fixes listed, assumes nothing else improves on its own, and never promises a perfect score.
The seven-day expiry
The report stays public for seven days from the day it was first emailed (or generated, if it was never sent). After that the page clears itself and offers to generate a fresh one. That is not a sales trick: a site changes, and a two-month-old speed reading is not something we want anyone acting on. You can claim the report into a free account to keep it beyond the window.
What 829 reports have shown
Between 21 February and 16 July 2026 our engine produced 829 reports covering 799 distinct domains, all websites we audited. The figures below are aggregates across that set; no individual site is identifiable. Two caveats apply: the reports were produced by successive versions of the engine, and the issue counts are floors, because each report lists only the most important issues it found.
| Measure | Result |
|---|---|
| Median overall score | 81 (grade B) |
| Grade distribution | A: 10%, B: 84%, C: 6%, D or F: under 1% |
| Median homepage load time (739 reports with a reading) | 3.9 seconds |
| Homepage slower than 3 seconds | 60% of reports with a reading |
| Median Lighthouse mobile Performance (692 with a score) | 62 |
| Mobile Performance below 50 | 22% of reports with a score |
| Failing Core Web Vitals in the lab (696 with data) | 91%, almost all on LCP |
| Missing meta descriptions | at least 61% of reports |
| Thin content on a key page | at least 59% |
| Sitemap problems | at least 39% |
| Duplicate title tags | at least 38% |
| robots.txt problems | at least 24% |
| No HTTPS | 4% |
The striking pattern is the gap between grade and speed. A B grade is the norm, yet nine in ten sites fail LCP in a mobile lab test. The reason is that the score looks at more than speed: Google's Accessibility, SEO and Best Practices checks tend to score well on modern templates and CMS themes, which lifts the overall result even when Performance is weak. A B on our report does not mean the site is fast. Read the load-time line before the grade.
Three result profiles we see again and again
Most reports fall into one of three shapes. Recognising yours tells you where the effort belongs.
The good-looking B with a slow homepage. Score in the low 80s, Accessibility and SEO scores in the 90s, Performance in the 50s or 60s, and a load time between 3 and 6 seconds. This is the most common profile by far. The template is sound; the weight sits in images, page builders and third-party scripts. Effort belongs almost entirely in speed.
The fast site with gaps in the basics. Performance is fine, but the issue list shows missing meta descriptions, duplicate titles and thin service pages. These sites are often new builds where the designer handled the code and nobody wrote the copy. Effort belongs in content and on-page fundamentals, which no speed tool can fix.
The site with a structural fault. A grade of C or below, usually driven by a serious fault such as missing HTTPS, a robots.txt rule blocking key sections, or a sitemap returning an error. These are rare in our data but urgent, because they cap everything else. Fix the structural fault before touching anything cosmetic.
What to fix first
The report orders issues by severity class. When we work on a site, we order fixes by a slightly different rule: first anything that stops Google crawling or trusting the site, then anything that hurts every visitor on every page, then page-level improvements. Here is that order, with how long each typically takes.
1. HTTPS, if it is missing
Only 4% of the sites we tested lacked HTTPS, but for those sites nothing else matters as much. Browsers flag the site as "Not secure", and Google lists HTTPS as part of its page experience signals. Most hosts issue a free certificate in minutes. Redirect every HTTP URL to its HTTPS equivalent with a 301 and update internal links.
2. robots.txt and sitemap problems
A robots.txt rule that blocks important paths, or a sitemap that is missing, unreachable or listing broken URLs, quietly limits what Google can find. These are usually ten-minute fixes with outsized consequences. Check that /robots.txt does not disallow pages you want indexed, that /sitemap.xml returns a valid file, and that the sitemap is referenced in robots.txt and submitted in Search Console. Our technical SEO audit guide covers the full crawlability checklist.
3. Homepage load time and LCP
This is the most common serious finding, and the one most likely to affect real visitors. On small-business sites the cause is usually one of three things: an oversized hero image, render-blocking scripts from plugins and third-party widgets, or slow server response. Work through them in that order:
- Serve the hero image at the size it is displayed, in a modern format, with explicit width and height. Our WebP implementation guide shows how.
- Turn on Gzip or Brotli compression at the server or CDN.
- Remove or defer scripts that are not needed for the first screen: chat widgets, sliders, unused analytics tags.
- If Time to First Byte is above roughly 0.8 seconds, look at hosting and caching before anything else.
Re-run PageSpeed Insights after each change rather than all at once, so you know which change moved the number.
4. Mobile performance
A mobile Performance score below 50 usually shares a root cause with slow load time, so fixing step 3 often fixes this too. If it does not, look at layout shift (CLS above 0.1, which affected 17% of the sites we tested) and heavy JavaScript execution. Google indexes the mobile version of your site, as our mobile-first indexing guide explains, so the mobile result is the one that counts.
5. Titles and meta descriptions
Duplicate titles and missing meta descriptions do not stop a page ranking, but they weaken how it appears in results. Google's documentation on title links and snippets is clear that unique, descriptive titles and summaries help it represent each page. Give every key page a unique title under about 60 characters and a description that states what the page offers. For a five-page site, this is an hour's work.
6. Thin content
Thin content on a key page was flagged on at least 59% of reports. Word count is a blunt instrument: a contact page does not need 1,000 words. The useful question is whether each service page answers what a buyer needs before getting in touch: what you do, for whom, where, at what kind of price, and why you. Expand the pages that matter commercially and leave utility pages alone.
What the report cannot tell you
A free report built from outside your site has hard limits, and we would rather you knew them:
- It tests a sample, not the whole site. A handful of key pages, not every URL.
- Speed figures are lab data. PageSpeed Insights lab results simulate a mid-range phone on a throttled connection. Real-user field data, where available, can be better or worse. Google explains the difference in its PageSpeed Insights documentation.
- INP needs real users. Interaction to Next Paint is a field metric, so a lab run rarely reports a meaningful value.
- It has no traffic, ranking or backlink data. Without Search Console access we cannot see clicks, impressions or which queries you rank for, so the report makes no traffic claims.
- It does not judge content quality or AI-search visibility. Whether ChatGPT or Google's AI answers cite you is a separate question; our AI visibility check tests that one.
If a ranking drop is what prompted you to look, also check the timing against our Google algorithm updates timeline before assuming a technical cause.
Next steps
If you received a report, the most valuable thing you can do this week is the first fix on the list above that applies to you, then re-test. Most sites we see need hours of focused work, not months.
When you re-test, compare like with like. Run PageSpeed Insights on the same URL, on mobile, two or three times, and take the middle result: lab scores move by a few points between runs because of network and server variance. A change of two or three points is noise; a load time that drops from 6 seconds to 3 is real. Keep a dated note of what you changed and when, so that if rankings move in the following weeks you can tell your own changes apart from a Google update.
If you would like a second pair of eyes on the findings, book a consultation and we will go through your report with you. If you have not had a report yet, you can run a free audit of your site with just your domain.
Key takeaways
- The overall score combines Google's own lab tests with the issues we find; a B grade can hide a slow site.
- The load-time line, measured against Google's 2.5-second LCP threshold, is the most important single number on the report.
- Across 829 reports, the median homepage took 3.9 seconds and 91% failed Core Web Vitals in the lab, almost entirely on LCP.
- Fix in this order: HTTPS, crawlability (robots.txt and sitemap), load time, mobile performance, titles and descriptions, then thin content.
- The report expires after seven days because site data goes stale; claim it or generate a fresh one before acting on old figures.
Where does your own site stand?
Run a free audit: enter your domain and get a dated, sourced record of what is publicly visible about your site. No login, no card. Prefer to talk it through? Book a consultation with our team.