Comparing Results

The Compare page lets you put two check batches side by side and instantly see which URLs improved and which regressed. Essential after a redesign, CMS upgrade, or technical deployment.

How to open

The Compare page is accessible from the project navigation. You need at least 2 completed batches before the page becomes useful.

Selecting batches

Two dropdowns at the top of the page let you pick the batches to compare:

• BEFORE — the earlier (baseline) batch
• AFTER — the newer (current) batch

Only completed batches appear in the lists, each showing its date and URL count.

Summary cards

After selecting both batches, four summary cards appear:

URL comparison table

Columns

Colour coding: ● Improved — score went up · ● Regressed — score dropped · ● Unchanged.

Filters

Pill buttons above the table let you narrow the list:

• All — show everything
• ↓ Regressed — only URLs that got worse
• ↑ Improved — only URLs that improved

Expanding a URL row

Click any row to expand a detailed before/after breakdown:

Lighthouse Scores — Performance, Accessibility, Best Practices, SEO; before / after for Mobile and Desktop.

Core Web Vitals — LCP, CLS, FCP, TTFB; before / after for Mobile and Desktop. Values are colour-coded — green if the result improved, red if it worsened.

Common workflows

Checking after a deployment

1. Run a check before deploying your update.
2. Deploy the update, then run a new check.
3. Open Compare, select the pre-deploy batch as BEFORE and the post-deploy batch as AFTER.
4. Filter by Regressed to find pages that got worse.

Validating an optimisation

1. Run a baseline check before your optimisation work (image compression, lazy loading, etc.).
2. Apply optimisations, then run a new check.
3. In Compare, select the before and after batches.
4. Confirm that Improved > Regressed.