www.nasdaq.com speed test — 20 Oct 2026

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

https://www.nasdaq.com/

20 October 2026 at 13:25 UTC · Free test · report pt_5096f665db3a

Re-test this page Test your own site

Grade

93/100

Performance95/100

Structure91/100

13 audit(s) passed, 3 need work

First byte (TTFB)365 msmeasured from this server

Fully loaded1.57 sfirst byte + slowest asset

Requests26document + assets

Page weight175.8 KBcompressed transfer

HTML document38.9 KBgzip

ProtocolHTTP/3Rendering-Platform

Third-party55.2 KBother hosts

Where the first byte went

DNS lookup 68 ms 19%
TCP connect 54 ms 15%
Server wait 243 ms 67%

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

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

Fully loadedfaster than 66% of 4,999 pages tested here1.57 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 365 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 175.8 KB over 26 request(s). Javascript files are 78% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
31% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Javascript 23 requests

136.9 KB 78%

Html 2 requests

20 B 0%

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

Top issues

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.

Avoid extra redirects

medium impact

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

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

JAVASCRIPTwww.nasdaq.com/sites/acquia.prod/files/js/js_f5XCIS0C…

1.20 s

HTMLwww.nasdaq.com/akam/13/38b51242

1.01 s

JAVASCRIPTcdn.jwplayer.com/libraries/UINd0LJW.js

989 ms