app.datadoghq.eu/account/login?next=%2F speed test — 20 Oct 2026

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

https://app.datadoghq.eu/account/login?next=%2F

20 October 2026 at 16:19 UTC · Free test · report pt_f867b3164b1d
Grade
B
80/100
Performance81/100
Structure79/100

11 audit(s) passed, 5 need work

First byte (TTFB)826 msmeasured from this server
Fully loaded1.27 sfirst byte + slowest asset
Requests3document + assets
Page weight1.08 MBcompressed transfer
HTML document29.4 KBgzip
ProtocolHTTP/3server not sent
Third-party1.05 MBother hosts

Where the first byte went

  • DNS lookup 89 ms 11%
  • TCP connect 81 ms 10%
  • Server wait 656 ms 79%

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 77% of 4,999 pages tested here826 ms against a median of 448 ms
Page weightheavier than 65% of 4,999 pages tested here1.08 MB against a median of 650.3 KB
Fully loadedfaster than 84% of 4,999 pages tested here1.27 s against a median of 1.84 s
Requestssends fewer requests than 95% of 4,999 pages tested here3 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 826 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.08 MB over 3 request(s), which is lean. Css files are 90% of it, so split the stylesheet so the first screen does not download the whole site.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 97% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element took 2.92 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.009), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 230 ms, so taps and scrolling wait while scripts run.

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 app.datadoghq.eu
Mobile 390 × 844 · 67.1 KB · page is 844 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 paint2.92 sgood is under 2.5 s
Cumulative layout shift0.009under 0.1 is stable
Total blocking time230 mslong tasks during load
First contentful paint2.81 sfirst content on screen
Browser page weight1.40 MB40 request(s), scripts included
Largest contentful paint2.92 s
Needs improvementgood under 2.5 s, poor over 4 s
Cumulative layout shift0.009
Goodgood under 0.1, poor over 0.25
Total blocking time230 ms
Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Css 1 request
997.8 KB 90%
Javascript 1 request
78.6 KB 7%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 826 ms. Of that, 656 ms was the server thinking and 170 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.

Compress text responses

high impact

1 text response(s) of 10 KB or more are sent uncompressed, and the document itself is not compressed. That is 997.8 KB of compressible text.

Fix: Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

Total page weight

medium impact

The page transfers 1.08 MB across 3 request(s), with the document itself at 29.4 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.05 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

3 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

CSSstatic.datadoghq.com/static/v/35.146013292/js/dd-login-rspa…
444 ms
JAVASCRIPTstatic.datadoghq.com/static/v/35.146013292/js/polyfills-rsp…
308 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://static.datadoghq.com/static/v/35.146013292/js/dd-login-rspack.min.css 3rd partycss200444 ms997.8 KB
https://static.datadoghq.com/static/v/35.146013292/js/polyfills-rspack.min.js 3rd partyjavascript200308 ms78.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.