dandomain.dk speed test — 20 Oct 2026

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

https://dandomain.dk/

20 October 2026 at 15:42 UTC · Free test · report pt_6ce4ca3b17b6
Grade
B
81/100
Performance81/100
Structure82/100

13 audit(s) passed, 3 need work

First byte (TTFB)735 msmeasured from this server
Fully loaded2.60 sfirst byte + slowest asset
Requests26document + assets
Page weight396.3 KBcompressed transfer
HTML document37.3 KBgzip
ProtocolHTTP/3server not sent

Where the first byte went

  • DNS lookup 85 ms 12%
  • TCP connect 203 ms 28%
  • Server wait 447 ms 61%

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 72% of 4,999 pages tested here735 ms against a median of 448 ms
Page weightlighter than 65% of 4,999 pages tested here396.3 KB against a median of 650.5 KB
Fully loadedslower than 76% of 4,999 pages tested here2.60 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 735 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 396.3 KB over 26 request(s). Images files are 91% 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 476 ms, inside the 2.5 s Google calls good.
  • The main thread was blocked for 205 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 dandomain.dk
Mobile 390 × 844 · 59.6 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 paint476 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time205 mslong tasks during load
First contentful paint476 msfirst content on screen
Browser page weight1.83 MB250 request(s), scripts included
Failed requests4blocked or unreachable
Largest contentful paint476 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time205 ms
Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests
359.0 KB 91%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 735 ms. Of that, 447 ms was the server thinking and 288 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

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

Render-blocking resources

high impact

3 render-blocking resource(s) in the document head (1 script(s), 2 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.

Waterfall

Slowest requests

IMAGESdandomain.dk/assets/images/logos/dandomain.svg
1.87 s
IMAGESdandomain.dk/assets/images/products/menu/onpay.svg
1.57 s
IMAGESdandomain.dk/assets/images/products/menu/e-mail.svg
1.57 s
IMAGESdandomain.dk/assets/images/products/menu/woocommerc…
1.50 s
IMAGESdandomain.dk/assets/images/products/menu/webshop.svg
1.49 s
IMAGESdandomain.dk/assets/images/products/menu/bookingsys…
1.44 s
IMAGESdandomain.dk/assets/images/products/menu/webhotel.svg
1.43 s
IMAGESdandomain.dk/assets/images/products/menu/macaly.svg
1.43 s
IMAGESdandomain.dk/assets/images/products/menu/ssl.svg
1.43 s
IMAGESdandomain.dk/assets/images/logos/microsoft/excel.svg
1.43 s

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://dandomain.dk/assets/images/logos/dandomain.svgimages2001.87 s4.0 KB
https://dandomain.dk/assets/images/products/menu/onpay.svgimages2001.57 s2.4 KB
https://dandomain.dk/assets/images/products/menu/e-mail.svgimages2001.57 s530 B
https://dandomain.dk/assets/images/products/menu/woocommerce.svgimages2001.50 s787 B
https://dandomain.dk/assets/images/products/menu/webshop.svgimages2001.49 s810 B
https://dandomain.dk/assets/images/products/menu/bookingsystem.svgimages2001.44 s651 B
https://dandomain.dk/assets/images/products/menu/webhotel.svgimages2001.43 s384 B
https://dandomain.dk/assets/images/products/menu/macaly.svgimages2001.43 s878 B
https://dandomain.dk/assets/images/products/menu/ssl.svgimages2001.43 s810 B
https://dandomain.dk/assets/images/logos/microsoft/excel.svgimages2001.43 s755 B
https://dandomain.dk/assets/images/logos/microsoft/word.svgimages2001.42 s765 B
https://dandomain.dk/assets/images/pages/index/wordpress.webpimages2001.42 s44.3 KB
https://dandomain.dk/assets/images/pages/index/hjemmesideprogram-area.webpimages2001.42 s28.7 KB
https://dandomain.dk/assets/images/shared/quotes/nordiccoffeehouse.webpimages2001.42 s12.2 KB
https://dandomain.dk/assets/images/products/menu/wordpress.svgimages2001.42 s979 B
https://dandomain.dk/assets/images/products/menu/hjemmesideprogram.svgimages2001.42 s523 B
https://dandomain.dk/assets/images/logos/microsoft/powerpoint.svgimages2001.41 s809 B
https://dandomain.dk/assets/images/products/menu/waywidget.svgimages2001.41 s645 B
https://dandomain.dk/assets/images/products/menu/iubenda.svgimages2001.41 s555 B
https://dandomain.dk/assets/images/pages/index/webhotel-image.webpimages2001.41 s12.3 KB
https://dandomain.dk/assets/images/products/menu/social-coach.svgimages2001.41 s1.2 KB
https://dandomain.dk/assets/images/icons/ai-color.svgimages2001.40 s2.0 KB
https://dandomain.dk/assets/images/pages/home/banner/macaly-banner.webpimages2001.40 s240.9 KB
https://dandomain.dk/assets/images/products/menu/leadinfo.svgimages2001.40 s491 B
https://dandomain.dk/assets/images/products/menu/microsoft365.svgimages2001.39 s802 B
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.