Scan comparison
Green: scan A is better than scan B, red: scan A is worse. The change is always scan A − scan B.
Scan A (current)
94
turbometrics.io
14 Oct 2026 12:00 AM
· Falkenstein
vs.
+13
Filmstrip comparison
Scan A
00:00
94
FCP
LCP
Finished
Scan B
06:00
81
FCP
LCP
Finished
FCP
252 ms
vs.
316 ms
−64 ms
LCP
252 ms
vs.
316 ms
−64 ms
Finished
889 ms
vs.
954 ms
−65 ms
Score
94
vs.
81
+13
Scores
| Category | Scan A | Change | Scan B |
|---|---|---|---|
| Total | 94 | +13 | 81 |
| Speed | 92 | +32 | 60 |
| 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 | 529 ms Good | −1.63 s | 2.15 s Poor |
| FCP i | 232 ms Good | −72 ms | 304 ms Good |
| LCP i | 232 ms Good | −72 ms | 304 ms Good |
| CLS i | 0 Good | ≈ 0 | 0 Good |
| TBT i | 0 ms Good | ≈ 0 | 6 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 | 2 ms |
| TCP connection | 13 ms | ≈ 0 | 17 ms |
| TTFB | 140 ms | ≈ 0 | 128 ms |
| Transfer | 2 ms | ≈ 0 | 1 ms |
| DOM loaded | 236 ms | −36 ms | 272 ms |
| Page loaded | 256 ms | −49 ms | 305 ms |
Mobile (390 px)
| Phase | Scan A | Change | Scan B |
|---|---|---|---|
| DNS | 9 ms | ≈ 0 | 4 ms |
| TCP connection | 18 ms | ≈ 0 | 18 ms |
| TTFB | 131 ms | ≈ 0 | 112 ms |
| Transfer | 2 ms | ≈ 0 | 5 ms |
| DOM loaded | 227 ms | −42 ms | 269 ms |
| Page loaded | 239 ms | −38 ms | 277 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 529 ms.
Fixed since scan B (1)
Server responds slowly
The server response takes around 2.15 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 | ||
| −8 pts | Slightly elevated TTFB (Server response approx. 529 ms) | — |
| — | Very high TTFB (Server response approx. 2.15 s) | −40 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 |