ladies.de speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 12:48 UTC. Grade A (96/100), with the screenshots, the timings and the fixes that matter.

https://ladies.de/

20 October 2026 at 12:48 UTC · Free test · report pt_2e9f7eb8bf7f
Grade
A
96/100
Performance98/100
Structure94/100

14 audit(s) passed, 2 need work

First byte (TTFB)272 msmeasured from this server
Fully loaded644 msfirst byte + slowest asset
Requests4document + assets
Page weight12.5 KBcompressed transfer
HTML document2.4 KBbr
ProtocolHTTP/3cloudflare
Third-party10.1 KBother hosts

Where the first byte went

  • DNS lookup 45 ms 17%
  • TCP connect 7 ms 3%
  • Server wait 220 ms 81%

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 80% of 4,999 pages tested here272 ms against a median of 449 ms
Page weightlighter than 95% of 4,999 pages tested here12.5 KB against a median of 650.5 KB
Fully loadedfaster than 97% of 4,999 pages tested here644 ms against a median of 1.84 s
Requestssends fewer requests than 94% of 4,999 pages tested here4 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 272 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 12.5 KB over 4 request(s), which is lean. Images files are 81% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 80% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element painted at 1.16 s, inside the 2.5 s Google calls good.
  • Layout shift is 0.138 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
  • The main thread was blocked for 38 ms in total, which is not enough to feel.

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

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 ladies.de
Mobile 390 × 844 · 103.0 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.16 sgood is under 2.5 s
Cumulative layout shift0.138under 0.1 is stable
Total blocking time38 mslong tasks during load
First contentful paint1.08 sfirst content on screen
Browser page weight2.16 MB76 request(s), scripts included
Largest contentful paint1.16 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.138
Needs improvementgood under 0.1, poor over 0.25
Total blocking time38 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 3 requests
10.1 KB 81%

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

Top issues

Cache static assets

medium impact

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

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.

Waterfall

Slowest requests

IMAGESladies.de/nojs.gif
372 ms
IMAGESstatic.ladies-cdn.de/shared/ladies/img/icons/favicon.webp
342 ms
IMAGESstatic.ladies-cdn.de/shared/ladies/img/icons/favicon.ico
199 ms

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://ladies.de/nojs.gif?request_path=%2Fimages200372 ms42 B
https://static.ladies-cdn.de/shared/ladies/img/icons/favicon.webp 3rd partyimages200342 ms8.8 KB
https://static.ladies-cdn.de/shared/ladies/img/icons/favicon.ico 3rd partyimages200199 ms1.3 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.