www.dlink.com/us/en speed test — 20 Oct 2026

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

https://www.dlink.com/us/en

20 October 2026 at 15:11 UTC · Free test · report pt_f58ad8a370d6

Re-test this page Test your own site

Grade

58/100

Performance51/100

Structure68/100

10 audit(s) passed, 6 need work

First byte (TTFB)956 msmeasured from this server

Fully loaded2.36 sfirst byte + slowest asset

Requests26document + assets

Page weight7.14 MBcompressed transfer

HTML document15.2 KBbr

ProtocolHTTP/3cloudflare

Third-party7.01 MBother hosts

Where the first byte went

DNS lookup 53 ms 6%
TCP connect 51 ms 5%
Server wait 853 ms 89%

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

Page weightheavier than 96% of 4,999 pages tested here7.14 MB against a median of 650.3 KB

Fully loadedslower than 70% of 4,999 pages tested here2.36 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 956 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 7.14 MB over 26 request(s). Media files are 97% of it, so let video load on demand instead of on first paint.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
98% 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 2.12 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.095), so nothing jumps under the reader's cursor.
The main thread was blocked for 27 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.dlink.com — **Mobile** 390 × 844 · 84.9 KB · page is 3516 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.12 sgood is under 2.5 s

Cumulative layout shift0.095under 0.1 is stable

Total blocking time27 mslong tasks during load

First contentful paint1.69 sfirst content on screen

Browser page weight21.70 MB50 request(s), scripts included

Largest contentful paint2.12 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.095

Goodgood under 0.1, poor over 0.25

Total blocking time27 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Media 1 request

6.95 MB 97%

Images 9 requests

120.1 KB 2%

Javascript 3 requests

56.8 KB 1%

Html 12 requests

92 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 956 ms. Of that, 853 ms was the server thinking and 104 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.

Render-blocking resources

high impact

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

Total page weight

high impact

The page transfers 7.14 MB across 26 request(s), with the document itself at 15.2 KB.

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

Third-party weight

medium impact

4 third-party host(s) serve 7.01 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

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.