www.mpg.de/de speed test — 20 Oct 2026

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

https://www.mpg.de/de

20 October 2026 at 13:10 UTC · Free test · report pt_2132eb9c88e7

Re-test this page Test your own site

Grade

81/100

Performance78/100

Structure86/100

12 audit(s) passed, 4 need work

First byte (TTFB)839 msmeasured from this server

Fully loaded2.72 sfirst byte + slowest asset

Requests26document + assets

Page weight126.7 KBcompressed transfer

HTML document107.1 KBgzip

ProtocolHTTP/2Apache

Third-party19.6 KBother hosts

Where the first byte went

DNS lookup 73 ms 9%
TCP connect 192 ms 23%
Server wait 574 ms 68%

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 78% of 4,999 pages tested here839 ms against a median of 448 ms

Page weightlighter than 85% of 4,999 pages tested here126.7 KB against a median of 650.5 KB

Fully loadedslower than 78% of 4,999 pages tested here2.72 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 839 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 126.7 KB over 26 request(s).
The HTML itself arrives gzip-compressed.
It runs over HTTP/2, so the assets share a connection instead of opening one each.

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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Javascript 1 request

19.5 KB 15%

Images 24 requests

43 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 839 ms. Of that, 574 ms was the server thinking and 265 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.

HTML document size

medium impact

The document transfers 107.1 KB. A bloated document delays every other request, because nothing else can start until it is parsed.

Fix: Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.

Avoid extra redirects

medium impact

2 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.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.