sciencedaily.com speed test — 20 Oct 2026

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

https://sciencedaily.com/

20 October 2026 at 12:57 UTC · Free test · report pt_24baa752c233
Grade
A
97/100
Performance100/100
Structure92/100

14 audit(s) passed, 2 need work

First byte (TTFB)184 msmeasured from this server
Fully loaded928 msfirst byte + slowest asset
Requests14document + assets
Page weight312.8 KBcompressed transfer
HTML document31.5 KBbr
ProtocolHTTP/3cloudflare
Third-party198.3 KBother hosts

Where the first byte went

  • DNS lookup 38 ms 21%
  • TCP connect 7 ms 4%
  • Server wait 139 ms 76%

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 95% of 4,999 pages tested here184 ms against a median of 449 ms
Page weightlighter than 71% of 4,999 pages tested here312.8 KB against a median of 650.5 KB
Fully loadedfaster than 93% of 4,999 pages tested here928 ms against a median of 1.84 s
Requestssends fewer requests than 84% of 4,999 pages tested here14 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 server answered in 184 ms, which is fast: almost all of the wait is the page itself, not the host.
  • The page transfers 312.8 KB over 14 request(s), which is lean. Javascript files are 79% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 63% 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 200 ms, inside the 2.5 s Google calls good.
  • The main thread was blocked for 2 ms in total, which is not enough to feel.

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 sciencedaily.com
Mobile 390 × 844 · 80.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 paint200 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time2 mslong tasks during load
First contentful paint200 msfirst content on screen
Browser page weight523.0 KB24 request(s), scripts included
Largest contentful paint200 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time2 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 7 requests
247.7 KB 79%
Css 5 requests
26.8 KB 9%
Images 1 request
6.8 KB 2%

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

Top issues

Render-blocking resources

high impact

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

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

JAVASCRIPTsciencedaily.com/js/bootstrap-3.4.1.min.js
744 ms
CSSsciencedaily.com/css/custom-202404121350.css
673 ms
CSSsciencedaily.com/css/social-share-kit.css
670 ms
JAVASCRIPTsciencedaily.com/js/jquery-3.6.0.min.js
596 ms
JAVASCRIPTscripts.pubnation.com/tags/197d605c-8b0a-4d0c-8229-cd0e28a78…
594 ms
JAVASCRIPTwww.googletagmanager.com/gtag/js
591 ms
IMAGESsciencedaily.com/images/sd-logo.png
591 ms
CSSsciencedaily.com/css/bootstrap.min.css
590 ms
CSSsciencedaily.com/css/font-awesome.min.css
590 ms
JAVASCRIPTsciencedaily.com/js/social-share-kit.min.js
590 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://sciencedaily.com/js/bootstrap-3.4.1.min.jsjavascript200744 ms11.0 KB
https://sciencedaily.com/css/custom-202404121350.csscss200673 ms5.3 KB
https://sciencedaily.com/css/social-share-kit.csscss200670 ms2.7 KB
https://sciencedaily.com/js/jquery-3.6.0.min.jsjavascript200596 ms31.2 KB
https://scripts.pubnation.com/tags/197d605c-8b0a-4d0c-8229-cd0e28a78762.js 3rd partyjavascript200594 ms18.9 KB
https://www.googletagmanager.com/gtag/js?id=G-GT6V1PPT8H 3rd partyjavascript200591 ms179.3 KB
https://sciencedaily.com/images/sd-logo.pngimages200591 ms6.8 KB
https://sciencedaily.com/css/bootstrap.min.csscss200590 ms13.7 KB
https://sciencedaily.com/css/font-awesome.min.csscss200590 ms4.9 KB
https://sciencedaily.com/js/social-share-kit.min.jsjavascript200590 ms2.5 KB
https://sciencedaily.com/js/jQuery.print.jsjavascript200590 ms2.4 KB
https://sciencedaily.com/js/custom-202307301940.jsjavascript200590 ms2.3 KB
https://sciencedaily.com/css/yamm.csscss200590 ms248 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.