udn.com speed test — 20 Oct 2026

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

https://udn.com/

20 October 2026 at 13:53 UTC · Free test · report pt_cc94b7391c7d

Re-test this page Test your own site

Grade

91/100

Performance97/100

Structure82/100

12 audit(s) passed, 4 need work

First byte (TTFB)247 msmeasured from this server

Fully loaded1.88 sfirst byte + slowest asset

Requests26document + assets

Page weight481.8 KBcompressed transfer

HTML document76.9 KBgzip

ProtocolHTTP/3nginx

Third-party391.6 KBother hosts

Where the first byte went

DNS lookup 52 ms 21%
TCP connect 41 ms 17%
Server wait 154 ms 62%

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 85% of 4,999 pages tested here247 ms against a median of 449 ms

Page weightlighter than 59% of 4,999 pages tested here481.8 KB against a median of 650.5 KB

Fully loadedslower than 52% of 4,999 pages tested here1.88 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 arrived in 247 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 481.8 KB over 26 request(s). Images files are 84% 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.
81% 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.00 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 886 ms, so taps and scrolling wait while scripts run.

Fix first: Render-blocking resources - 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.

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 udn.com — **Mobile** 390 × 844 · 291.3 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.00 sgood is under 2.5 s

Cumulative layout shift0.001under 0.1 is stable

Total blocking time886 mslong tasks during load

First contentful paint660 msfirst content on screen

Browser page weight6.11 MB286 request(s), scripts included

Failed requests12blocked or unreachable

Largest contentful paint1.00 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.001

Goodgood under 0.1, poor over 0.25

Total blocking time886 ms

Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

404.9 KB 84%

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

Top issues

Render-blocking resources

high impact

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

Cache static assets

medium impact

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

Third-party weight

medium impact

2 third-party host(s) serve 391.6 KB 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.

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.