www.bfv.de speed test — 20 Oct 2026

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

https://www.bfv.de/

20 October 2026 at 14:17 UTC · Free test · report pt_9f6ab3c46d5d

Re-test this page Test your own site

Grade

84/100

Performance87/100

Structure80/100

11 audit(s) passed, 5 need work

First byte (TTFB)410 msmeasured from this server

Fully loaded2.22 sfirst byte + slowest asset

Requests26document + assets

Page weight1.47 MBcompressed transfer

HTML document24.9 KBgzip

ProtocolHTTP/3server not sent

Third-party1.45 MBother hosts

Where the first byte went

DNS lookup 63 ms 15%
TCP connect 28 ms 7%
Server wait 319 ms 78%

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 bytefaster than 55% of 4,999 pages tested here410 ms against a median of 449 ms

Page weightheavier than 74% of 4,999 pages tested here1.47 MB against a median of 650.3 KB

Fully loadedslower than 65% of 4,999 pages tested here2.22 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 arrived in 410 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 1.47 MB over 26 request(s). Images files are 98% 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.
98% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element took 3.06 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
Layout stayed still (CLS 0.003), so nothing jumps under the reader's cursor.
The main thread was blocked for 61 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.

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 paint3.06 sgood is under 2.5 s

Cumulative layout shift0.003under 0.1 is stable

Total blocking time61 mslong tasks during load

First contentful paint1.60 sfirst content on screen

Browser page weight1.58 MB31 request(s), scripts included

Largest contentful paint3.06 s

Needs improvementgood under 2.5 s, poor over 4 s

Cumulative layout shift0.003

Goodgood under 0.1, poor over 0.25

Total blocking time61 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

1.45 MB 98%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 410 ms. Of that, 319 ms was the server thinking and 91 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.

Render-blocking resources

high impact

3 render-blocking resource(s) in the document head (0 script(s), 3 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Total page weight

medium impact

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

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

Third-party weight

medium impact

1 third-party host(s) serve 1.45 MB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

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.