www.doi.org speed test — 20 Oct 2026

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

https://www.doi.org/

20 October 2026 at 12:35 UTC · Free test · report pt_005aafd72cbc
Grade
A
90/100
Performance98/100
Structure77/100

12 audit(s) passed, 4 need work

First byte (TTFB)281 msmeasured from this server
Fully loaded1.24 sfirst byte + slowest asset
Requests19document + assets
Page weight465.4 KBcompressed transfer
HTML document6.8 KBgzip
ProtocolHTTP/3cloudflare
Third-party46.4 KBother hosts

Where the first byte went

  • DNS lookup 74 ms 26%
  • TCP connect 51 ms 18%
  • Server wait 155 ms 55%

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 78% of 4,999 pages tested here281 ms against a median of 449 ms
Page weightlighter than 61% of 4,999 pages tested here465.4 KB against a median of 650.5 KB
Fully loadedfaster than 86% of 4,999 pages tested here1.24 s against a median of 1.84 s
Requestssends fewer requests than 80% of 4,999 pages tested here19 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 281 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 465.4 KB over 19 request(s). Images files are 75% 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 864 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.002), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 23 ms in total, which is not enough to feel.

Fix first: Image delivery and format - 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.

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.doi.org
Mobile 390 × 844 · 45.3 KB · page is 5234 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 paint864 msgood is under 2.5 s
Cumulative layout shift0.002under 0.1 is stable
Total blocking time23 mslong tasks during load
First contentful paint636 msfirst content on screen
Browser page weight831.7 KB23 request(s), scripts included
Largest contentful paint864 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.002
Goodgood under 0.1, poor over 0.25
Total blocking time23 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 10 requests
351.2 KB 75%
Javascript 3 requests
56.0 KB 12%
Css 5 requests
51.4 KB 11%

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

Top issues

Image delivery and format

high impact

1 image(s) over 200 KB and 1 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

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

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.

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.

Waterfall

Slowest requests

JAVASCRIPTcdn.jsdelivr.net/npm/[email protected]/dist/js/bootstrap.…
961 ms
JAVASCRIPTwww.doi.org/js/jquery-3.6.1.min.js
876 ms
CSScdn.jsdelivr.net/npm/[email protected]/dist/css/bootstrap…
875 ms
IMAGESwww.doi.org/images/globe.svg
863 ms
IMAGESwww.doi.org/images/dot-pattern.svg
862 ms
IMAGESwww.doi.org/images/board/jclark.jpg
852 ms
IMAGESwww.doi.org/images/target.svg
852 ms
JAVASCRIPTwww.doi.org/js/script.js
851 ms
CSSwww.doi.org/css/fontawesome-free-6.7.2-web/css/sol…
851 ms
IMAGESwww.doi.org/images/[email protected]
850 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://cdn.jsdelivr.net/npm/[email protected]/dist/js/bootstrap.bundle.min.js 3rd partyjavascript200961 ms22.7 KB
https://www.doi.org/js/jquery-3.6.1.min.jsjavascript200876 ms30.4 KB
https://cdn.jsdelivr.net/npm/[email protected]/dist/css/bootstrap.min.css 3rd partycss200875 ms23.7 KB
https://www.doi.org/images/globe.svgimages200863 ms828 B
https://www.doi.org/images/dot-pattern.svgimages200862 ms45.1 KB
https://www.doi.org/images/board/jclark.jpgimages200852 ms30.4 KB
https://www.doi.org/images/target.svgimages200852 ms748 B
https://www.doi.org/js/script.jsjavascript200851 ms2.9 KB
https://www.doi.org/css/fontawesome-free-6.7.2-web/css/solid.min.csscss200851 ms335 B
https://www.doi.org/images/[email protected]images200850 ms256.8 KB
https://www.doi.org/css/fontawesome-free-6.7.2-web/css/fontawesome.min.csscss200850 ms15.9 KB
https://www.doi.org/images/favicons/favicon.icoimages200850 ms15.0 KB
https://www.doi.org/css/style.c9da778930845ca2b520440a16208e8d25f7cb3416af167b59bf33e30b0c6afb.css?v=sha256-ydp3iTCEXKK1IEQKFiCOjSX3yzQWrxZ7Wb8z4wsMavs%3dcss200850 ms6.8 KB
https://www.doi.org/css/fontawesome-free-6.7.2-web/css/brands.min.csscss200850 ms4.6 KB
https://www.doi.org/images/favicons/favicon-32x32.pngimages200850 ms1.6 KB
https://www.doi.org/images/favicons/favicon-16x16.pngimages200850 ms698 B
https://www.doi.org/images/logos/ header_logo_cropped_registered.svgimages00 ms0 B
https://www.doi.org/images/logos/ footer_logo_cropped_registered.svgimages00 ms0 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.