Scan comparison

Scan A (current)
70 scenegenerator.io
10 Sep 2026 3:40 AM · 🇩🇪 Falkenstein
vs. -4
Scan B (comparison)
scenegenerator.io 74
12 Sep 2026 4:04 AM · 🇩🇪 Falkenstein

Filmstrip comparison

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

Scores

Category Scan A Change Scan B
Total 70 -4 74
Speed 47 -10 57
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 789 ms +232 ms 557 ms
FCP i 464 ms -316 ms 780 ms
LCP i 584 ms -380 ms 964 ms
CLS i 0.05 ≈ 0 0.05
TBT i 216 ms +130 ms 86 ms
Requests i 64 ≈ 0 66
Data volume i 3.879,7 KB ≈ 0 3.902,2 KB

Page build timing

Navigation timing from the real page load in the browser.

Desktop (1440 px)

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

Mobile (390 px)

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

Findings comparison

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

New in scan A (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.
32 images without width/height
32 of 39 images have no explicit dimensions and can cause layout shifts (CLS).
Server response can be improved
The server response takes around 789 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 36 external JavaScript files.
JavaScript payload is high
The statically detected JavaScript files add up to around 708.30 KB.
Many images detected on the page
HTML and CSS together reference 32 distinct images.
Image payload is high
The inspected images add up to around 5.75 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. 789 ms) −8 pts
−10 pts Many external JS files (36 detected in the HTML) −10 pts
−12 pts High JavaScript weight (708.30 KB) −12 pts
−4 pts One very large JavaScript file (messages-m22pKBWF.js – 448.13 KB) −4 pts
−10 pts Elevated TBT (Total Blocking Time approx. 216 ms)
−5 pts Elevated runtime weight (3.79 MB) −5 pts
−4 pts Many font files (20 font files) −4 pts
Images
−12 pts Many images (32 images) −12 pts
−14 pts High image weight (5.75 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 (32 images without width/height) −4 pts