How to run a full site scan
Grade your whole site — Core Web Vitals, caching, assets and platform — and get a ranked list of fixes with the points each one recovers.
A PageSpeed score tells you how one page rendered on one test machine. xSpeed Scan asks a broader question: across roughly twenty checks in four weighted areas, how well is this site actually set up? It returns one grade out of 100 and — more usefully — a ranked list of what to fix, each with the number of points it would recover.
Where to find it
- In your WordPress admin, click xSpeed Cache in the left menu.
- In the xSpeed Cache sidebar, open the Health & insights group.
- Click the Speed Test card, then the xSpeed Scan tab.
Shortcut: open
wp-admin/admin.php?page=xspeed#/insights/score/scandirectly.✅ This tab is part of xSpeed Cache (Free).
- xSpeed Scan — what the report covers.
- Visibility notice — where the report will be published.
- Run a scan — starts it; becomes Scan again once you have a report.
Settings at a glance
This tab has no stored settings — it’s one action and its result:
| Control | What it does |
|---|---|
| Run a scan | Grades the site and stores the report. Scan again once one exists. |
| Dimension bars | The four graded areas, each with points earned out of its weight. |
| What to fix next | Failed and partial checks, ranked by points recovered. |
| Full report | Opens the hosted report. |
How it works
Press Run a scan and the engine grades your site across four weighted dimensions, taking roughly 20–60 seconds:
| Dimension | What it covers |
|---|---|
| Core Web Vitals | Measured loading behaviour — LCP, CLS, TBT and friends. |
| Server & caching | Whether caching is actually working at the origin. |
| Assets | Weight and delivery of CSS, JavaScript, images and fonts. |
| Platform | The underlying stack — PHP, server software, configuration. |
Each bar shows the points earned against that dimension’s weight, so you can see which area is costing you most rather than just the total.
Read this before your first scan
⚠️ Your report is published publicly by default. The card says so above the button, not buried after it: “This report will be publicly visible at xspeedcache.com, listed under your domain.”
The scan engine publishes every report it stores to a per-host feed that anyone can enumerate by domain. Connecting xSpeed Hub keeps your reports unlisted; without it, a report for a client site is discoverable by that client’s domain. Decide that before you run one, because the decision is made at scan time.
It is not a second PageSpeed score
This is the distinction worth holding on to, and the panel is careful about it.
A Lighthouse result is one check inside this scan — worth 18 of the 100 points. The two numbers are on different scales and measure different things, so the card labels them separately — the scan’s own score out of 100, and Lighthouse performance, out of 100 with the device it measured — rather than presenting one as a version of the other.
So a site can grade well here and score moderately in Lighthouse, or the reverse. They are not in disagreement — they are answering different questions. Use Speed test for the score Google ranks on; use this for whether the site is configured well.
💡 A “partial scan” is not a failure. If some checks can’t run, the panel says “Partial scan — some checks could not run, so the score covers less than the full rubric” and the score covers less than the full 100. Treat that total as a floor, not a verdict.
What to fix next
The ranked list is the point of the whole feature. Each entry carries:
- Status — whether the check failed outright or passed partially.
- Evidence — what the scan actually observed.
- Remediation — what to change.
- Points recoverable — how much the grade improves if you fix it.
Sorting by points recovered means you spend effort where it counts, instead of working down a list where a trivial item sits above a structural one. It pairs naturally with the recommendations on Health’s Overview tab: those read your xSpeed configuration, this grades the site as delivered.