www.uni-regensburg.de speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 16:04 UTC. Grade C (73/100), with the screenshots, the timings and the fixes that matter.

https://www.uni-regensburg.de/

20 October 2026 at 16:04 UTC · Free test · report pt_5661909ae863

Re-test this page Test your own site

Grade

73/100

Performance72/100

Structure74/100

11 audit(s) passed, 5 need work

First byte (TTFB)963 msmeasured from this server

Fully loaded2.17 sfirst byte + slowest asset

Requests23document + assets

Page weight1.41 MBcompressed transfer

HTML document17.6 KBgzip

ProtocolHTTP/3Apache

Where the first byte went

DNS lookup 411 ms 43%
TCP connect 174 ms 18%
Server wait 378 ms 39%

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

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

Fully loadedslower than 63% of 4,999 pages tested here2.17 s against a median of 1.84 s

Requestssends fewer requests than 77% of 4,999 pages tested here23 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 963 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.41 MB over 23 request(s). Images files are 82% 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.84 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.
The main thread was blocked for 18 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.uni-regensburg.de — **Mobile** 390 × 844 · 130.5 KB · page is 6000 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.84 sgood is under 2.5 s

Cumulative layout shift0.001under 0.1 is stable

Total blocking time18 mslong tasks during load

First contentful paint1.44 sfirst content on screen

Browser page weight920.5 KB22 request(s), scripts included

Largest contentful paint1.84 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.001

Goodgood under 0.1, poor over 0.25

Total blocking time18 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 17 requests

1.16 MB 82%

Fonts 2 requests

203.5 KB 14%

Css 2 requests

24.1 KB 2%

Javascript 1 request

16.4 KB 1%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 963 ms. Of that, 378 ms was the server thinking and 585 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.

Image delivery and format

high impact

3 image(s) over 200 KB and 0 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Total page weight

medium impact

The page transfers 1.41 MB across 23 request(s), with the document itself at 17.6 KB.

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

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.

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.