www.berlin.de speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 14:21 UTC. Grade B (84/100), with the screenshots, the timings and the fixes that matter.

https://www.berlin.de/

20 October 2026 at 14:21 UTC · Free test · report pt_d2ee21daf57e
Grade
B
84/100
Performance83/100
Structure85/100

12 audit(s) passed, 4 need work

First byte (TTFB)685 msmeasured from this server
Fully loaded1.96 sfirst byte + slowest asset
Requests26document + assets
Page weight1.13 MBcompressed transfer
HTML document8.2 KBgzip
ProtocolHTTP/3server not sent

Where the first byte went

  • DNS lookup 73 ms 11%
  • TCP connect 188 ms 27%
  • Server wait 424 ms 62%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First byteslower than 69% of 4,999 pages tested here685 ms against a median of 448 ms
Page weightheavier than 67% of 4,999 pages tested here1.13 MB against a median of 650.3 KB
Fully loadedslower than 55% of 4,999 pages tested here1.96 s against a median of 1.84 s
Requestssends more requests than 100% of 4,999 pages tested here26 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

  • The first byte took 685 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 1.13 MB over 26 request(s). Images files are 80% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 1.49 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.053), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 28 ms in total, which is not enough to feel.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of www.berlin.de
Mobile 390 × 844 · 172.5 KB · page is 5611 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint1.49 sgood is under 2.5 s
Cumulative layout shift0.053under 0.1 is stable
Total blocking time28 mslong tasks during load
First contentful paint1.49 sfirst content on screen
Browser page weight1.56 MB41 request(s), scripts included
Largest contentful paint1.49 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.053
Goodgood under 0.1, poor over 0.25
Total blocking time28 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 14 requests
933.8 KB 80%
Javascript 2 requests
147.5 KB 13%
Css 2 requests
71.8 KB 6%
Html 7 requests
257 B 0%

Transfer size, compressed as sent. 26 request(s) in total, 1.13 MB across all of them.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 685 ms. Of that, 424 ms was the server thinking and 261 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Total page weight

medium impact

The page transfers 1.13 MB across 26 request(s), with the document itself at 8.2 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

Cache static assets

medium impact

6 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

Waterfall

Slowest requests

IMAGESwww.berlin.de/binaries/asset/image_assets/10605521/r…
1.27 s
HTMLwww.berlin.de/binaries/asset/image_assets/10585076/r…
1.27 s
IMAGESwww.berlin.de/binaries/asset/image_assets/10608031/r…
1.22 s
HTMLwww.berlin.de/binaries/asset/image_assets/9831706/ra…
1.22 s
IMAGESwww.berlin.de/binaries/asset/image_assets/10634128/r…
1.19 s
HTMLwww.berlin.de/binaries/asset/image_assets/10638127/r…
1.18 s
IMAGESwww.berlin.de/binaries/asset/image_assets/8215610/ra…
1.16 s
IMAGESwww.berlin.de/css/berlin_de/foxtrot/images/logo_berl…
1.16 s
HTMLwww.berlin.de/binaries/asset/image_assets/8215538/ra…
1.16 s
IMAGESwww.berlin.de/binaries/asset/image_assets/8215661/ra…
1.16 s

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://www.berlin.de/binaries/asset/image_assets/10605521/ratio_4_3/1789030172/800x600/images2001.27 s123.5 KB
https://www.berlin.de/binaries/asset/image_assets/10585076/ratio_4_3/1787319018/800x600/html4291.27 s257 B
https://www.berlin.de/binaries/asset/image_assets/10608031/ratio_4_3/1788337526/800x600/images2001.22 s61.4 KB
https://www.berlin.de/binaries/asset/image_assets/9831706/ratio_4_3/1754823726/800x600/html5031.22 s0 B
https://www.berlin.de/binaries/asset/image_assets/10634128/ratio_4_3/1789391833/800x600/images2001.19 s74.9 KB
https://www.berlin.de/binaries/asset/image_assets/10638127/ratio_4_3/1789560642/800x600/html5031.18 s0 B
https://www.berlin.de/binaries/asset/image_assets/8215610/ratio_4_3/1763987184/800x600/images2001.16 s56.9 KB
https://www.berlin.de/css/berlin_de/foxtrot/images/logo_berlin_m_srgb.svgimages2001.16 s4.2 KB
https://www.berlin.de/binaries/asset/image_assets/8215538/ratio_4_3/1774260000/800x600/html5031.16 s0 B
https://www.berlin.de/binaries/asset/image_assets/8215661/ratio_4_3/1760961406/800x600/images2001.16 s101.6 KB
https://www.berlin.de/binaries/asset/image_assets/8158745/ratio_4_3/1775650409/800x600/html5031.15 s0 B
https://www.berlin.de/css/berlin_de/foxtrot/bundle/portal.js?1792059301javascript2001.15 s76.9 KB
https://www.berlin.de/binaries/link/file/1693399435/8423724.svgimages2001.14 s1.3 KB
https://www.berlin.de/binaries/link/file/1693399665/8423730.svgimages2001.14 s5.4 KB
https://www.berlin.de/favicon.icoimages2001.14 s7.2 KB
https://www.berlin.de/css/berlin_de/foxtrot/images/logo_berlin_m_negativ.svgimages2001.14 s4.1 KB
https://www.berlin.de/css/berlin_de/foxtrot/bundle/berlin_organization.css?_ts=1792059301css2001.13 s54.2 KB
https://www.berlin.de/binaries/asset/image_assets/5546119/ratio_4_3/1730115870/800x600/images2001.13 s179.5 KB
https://www.berlin.de/css/berlin_de/foxtrot/bundle/portal.css?_ts=1792059301css2001.13 s17.6 KB
https://www.berlin.de/css/berlin_de/foxtrot/bundle/berlin_organization.js?1792059301javascript2001.12 s70.5 KB
https://www.berlin.de/binaries/asset/image_assets/10297120/ratio_4_3/1787822444/800x600/images2001.12 s124.6 KB
https://www.berlin.de/binaries/asset/image_assets/10354975/ratio_4_3/1786690337/800x600/images2001.12 s135.4 KB
https://www.berlin.de/binaries/asset/image_assets/8158625/ratio_4_3/1760961409/800x600/html5031.11 s0 B
https://www.berlin.de/binaries/asset/image_assets/6643159/ratio_4_3/1641565285/800x600/html5031.11 s0 B
https://www.berlin.de/binaries/asset/image_assets/5214789/ratio_4_3/1615821563/800x600/images2001.10 s53.6 KB
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.