Scan comparison
Green: scan A is better than scan B, red: scan A is worse. The change is always scan A − scan B.
vs.
+5
Filmstrip comparison
Scan A
06:00
90
FCP
LCP
Finished
Scan B
00:00
85
FCP
LCP
Finished
FCP
336 ms
vs.
320 ms
+16 ms
LCP
336 ms
vs.
320 ms
+16 ms
Finished
912 ms
vs.
992 ms
−80 ms
Score
90
vs.
85
+5
Scores
| Category | Scan A | Change | Scan B |
|---|---|---|---|
| Total | 90 | +5 | 85 |
| Speed | 82 | +12 | 70 |
| Images | 93 | 0 | 93 |
| Caching | 91 | 0 | 91 |
| WordPress | 100 | 0 | 100 |
| Technical | 100 | 0 | 100 |
Core metrics
Lab values from the Mobile profile (390 px). TTFB is measured by the check server and applies to both profiles.
| Metric | Scan A | Change | Scan B |
|---|---|---|---|
| TTFB i | 898 ms Needs improvement | −504 ms | 1.4 s Needs improvement |
| FCP i | 296 ms Good | ≈ 0 | 292 ms Good |
| LCP i | 296 ms Good | ≈ 0 | 292 ms Good |
| CLS i | 0 Good | ≈ 0 | 0 Good |
| TBT i | 0 ms Good | ≈ 0 | 0 ms Good |
| Requests i | 6 Good | ≈ 0 | 6 Good |
| Data volume i | 47.4 KB | ≈ 0 | 47.4 KB |
Page build timing
Navigation timing from the real page load in the browser.
Desktop (1440 px)
| Phase | Scan A | Change | Scan B |
|---|---|---|---|
| DNS | 8 ms | ≈ 0 | 5 ms |
| TCP connection | 14 ms | ≈ 0 | 20 ms |
| TTFB | 116 ms | ≈ 0 | 113 ms |
| Transfer | 2 ms | ≈ 0 | 3 ms |
| DOM loaded | 276 ms | ≈ 0 | 292 ms |
| Page loaded | 299 ms | −25 ms | 324 ms |
Mobile (390 px)
| Phase | Scan A | Change | Scan B |
|---|---|---|---|
| DNS | 2 ms | ≈ 0 | 20 ms |
| TCP connection | 16 ms | ≈ 0 | 18 ms |
| TTFB | 108 ms | −39 ms | 147 ms |
| Transfer | 3 ms | ≈ 0 | 2 ms |
| DOM loaded | 266 ms | ≈ 0 | 279 ms |
| Page loaded | 282 ms | ≈ 0 | 299 ms |
Comparison of problems
Problems and warnings compared between the two scans (warnings and errors only).
New problems in scan A (1)
Server response can be improved
The server response takes around 898 ms.
Fixed since scan B (1)
Server responds slowly
The server response takes around 1.4 s. That slows down page rendering very early on.
Unchanged (2)
Lazy loading is not clearly detectable
Images were detected, but no loading="lazy" on any image element.
No modern image formats detected
No WebP or AVIF image files were detected in the HTML image sources.
Deductions by category
Which individual points influence the score the most.
| Scan A | Label | Scan B |
|---|---|---|
| Speed | ||
| −18 pts | Elevated TTFB (Server response approx. 898 ms) | — |
| — | High TTFB (Server response approx. 1.4 s) | −30 pts |
| Images | ||
| −3 pts | No clear lazy loading (No lazy loading indicators found) | −3 pts |
| −4 pts | No modern image formats (No WebP/AVIF detected) | −4 pts |
| Caching | ||
| −5 pts | Caching partly disabled (no-cache, private) | −5 pts |
| −4 pts | No clear page cache indicator (No HIT/Age indicators detected) | −4 pts |