www.jstor.org speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 12:43 UTC. Grade A (98/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 54 ms 30%
- TCP connect 15 ms 8%
- Server wait 109 ms 61%
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
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 178 ms, which is fast: almost all of the wait is the page itself, not the host.
- The page transfers 81.5 KB over 4 request(s), which is lean. Fonts files are 94% of it, so subset the fonts and stop preloading the weights you do not render.
- It runs over HTTP/3, so the assets share a connection instead of opening one each.
Fix first: Avoid extra redirects - 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.
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.
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
Transfer size, compressed as sent. 4 request(s) in total, 81.5 KB across all of them.
Top issues
Avoid extra redirects
medium impact1 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 impactHSTS 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
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
| Request | Type | Status | Time | Size |
|---|---|---|---|---|
| https://www.jstor.org/_fs-ch-1T1wmsGaOgGaSxcX/assets/styles.css | css | 200 | 261 ms | 1.4 KB |
| https://www.jstor.org/_fs-ch-1T1wmsGaOgGaSxcX/assets/inter-var.woff2 | fonts | 200 | 229 ms | 76.6 KB |
| https://www.jstor.org/_fs-ch-1T1wmsGaOgGaSxcX/assets/errorIcon.svg | images | 200 | 216 ms | 535 B |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.