← Back to the scan

Scan comparison

Scan A (current)
74 scenegenerator.io
12 Sep 2026 4:04 AM · 🇩🇪 Falkenstein
Open scan report ⇄ Swap scans
vs. +4
Scan B (comparison)
scenegenerator.io 70
10 Sep 2026 3:40 AM · 🇩🇪 Falkenstein
Open scan report

Filmstrip comparison

Scan A 04:04 74
1.2 s
FCP
1.6 s
LCP
1.9 s
2.2 s
2.6 s
3.0 s
Finished
956 ms
1.5 s
1.6 s
2.0 s
2.4 s
3.0 s
3.1 s
Scan B 03:40 70
956 ms
FCP
1.5 s
LCP
1.6 s
2.0 s
2.4 s
3.0 s
3.1 s
Finished
FCP
780 ms vs. 464 ms +316 ms
LCP
964 ms vs. 584 ms +380 ms
Finished
2.994 ms vs. 3.134 ms -140 ms
Score
74 vs. 70 +4

Scores

Category Scan A Change Scan B
Total 74 +4 70
Speed 57 +10 47
Images 68 0 68
Caching 90 0 90
WordPress 100 0 100
Technical 96 0 96

Core metrics

Desktop profile (1440 px). Positive delta (A − B): scan A is worse; negative delta: scan A is better.

Metric Scan A Change Scan B
TTFB i 557 ms -232 ms 789 ms
FCP i 780 ms +316 ms 464 ms
LCP i 964 ms +380 ms 584 ms
CLS i 0.05 ≈ 0 0.05
TBT i 86 ms -130 ms 216 ms
Requests i 66 ≈ 0 64
Data volume i 3.902,2 KB ≈ 0 3.879,7 KB

Page build timing

Navigation timing from the real page load in the browser.

Desktop (1440 px)

Phase Scan A Change Scan B
DNS 12 ms ≈ 0 15 ms
TCP connection 12 ms -22 ms 34 ms
TTFB 713 ms +195 ms 518 ms
Transfer 2 ms ≈ 0 2 ms
DOM loaded 894 ms +117 ms 777 ms
Page loaded 1.982 ms +699 ms 1.283 ms

Mobile (390 px)

Phase Scan A Change Scan B
DNS 8 ms ≈ 0 12 ms
TCP connection 12 ms ≈ 0 12 ms
TTFB 507 ms +411 ms 96 ms
Transfer 2 ms ≈ 0 2 ms
DOM loaded 684 ms +305 ms 379 ms
Page loaded 1.161 ms +300 ms 861 ms

Findings comparison

Problems and warnings compared between the two scans (bad/warning only).

Resolved since scan B (1)

The main thread is noticeably blocked
The browser main thread was blocked for around 216 ms during page load (Total Blocking Time).

Unchanged (10)

A large image stands out during the real page load
club-night-1786805573834.png weighs around 2.13 MB.
34 images without width/height
34 of 41 images have no explicit dimensions and can cause layout shifts (CLS).
Server response can be improved
The server response takes around 557 ms.
Many assets are not cached well
15 first-party assets have no clear long-lived cache rules.
Many CSS and JavaScript files detected
The HTML directly references 1 CSS files and 38 external JavaScript files.
JavaScript payload is high
The statically detected JavaScript files add up to around 721.96 KB.
Many images detected on the page
HTML and CSS together reference 34 distinct images.
Image payload is high
The inspected images add up to around 6.56 MB.
A single image is noticeably large
club-night-1786805573834.png weighs around 2.13 MB.
Font payload can be improved
Detected 20 font files totalling around 194.06 KB.

Score breakdown

Which individual points influence the score the most.

Scan A Label Scan B
Speed
−8 pts Slightly elevated TTFB (Server response approx. 557 ms) −8 pts
−10 pts Many external JS files (38 detected in the HTML) −10 pts
−12 pts High JavaScript weight (721.96 KB) −12 pts
−4 pts One very large JavaScript file (messages-Cd_w_4OY.js – 465.87 KB) −4 pts
−5 pts Elevated runtime weight (3.81 MB) −5 pts
−4 pts Many font files (20 font files) −4 pts
— Elevated TBT (Total Blocking Time approx. 216 ms) −10 pts
Images
−12 pts Many images (34 images) −12 pts
−14 pts High image weight (6.56 MB) −14 pts
−6 pts One very large image (club-night-1786805573834.png – 2.13 MB) −6 pts
Caching
−6 pts Many poorly cacheable first-party assets (15 assets) −6 pts
−4 pts No clear page cache indicator (No HIT/Age indicators detected) −4 pts
Technical
−4 pts Images without dimensions (34 images without width/height) −4 pts