instapaper.com speed test — 20 Oct 2026

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

https://instapaper.com/

20 October 2026 at 16:07 UTC · Free test · report pt_a1b5d348f71a
Grade
A
90/100
Performance93/100
Structure85/100

13 audit(s) passed, 3 need work

First byte (TTFB)443 msmeasured from this server
Fully loaded1.29 sfirst byte + slowest asset
Requests14document + assets
Page weight329.6 KBcompressed transfer
HTML document2.3 KBbr
ProtocolHTTP/3AmazonS3

Where the first byte went

  • DNS lookup 134 ms 30%
  • TCP connect 53 ms 12%
  • Server wait 256 ms 58%

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 51% of 4,999 pages tested here443 ms against a median of 449 ms
Page weightlighter than 70% of 4,999 pages tested here329.6 KB against a median of 650.5 KB
Fully loadedfaster than 83% of 4,999 pages tested here1.29 s 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 first byte arrived in 443 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 329.6 KB over 14 request(s), which is lean. Fonts files are 56% of it, so subset the fonts and stop preloading the weights you do not render.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 788 ms, inside the 2.5 s Google calls good.
  • The main thread was blocked for 7 ms in total, which is not enough to feel.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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.

Desktop screenshot of instapaper.com
Desktop 1366 × 768 · 40.9 KB · page is 2700 px tall
Mobile screenshot of instapaper.com
Mobile 390 × 844 · 29.9 KB · page is 2582 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 paint788 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time7 mslong tasks during load
First contentful paint788 msfirst content on screen
Browser page weight1.49 MB26 request(s), scripts included
Largest contentful paint788 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time7 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Fonts 3 requests
183.3 KB 56%
Images 6 requests
92.7 KB 28%
Css 2 requests
27.0 KB 8%
Javascript 2 requests
24.2 KB 7%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 443 ms. Of that, 256 ms was the server thinking and 187 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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.

Cache static assets

medium impact

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

Waterfall

Slowest requests

JAVASCRIPTinstapaper.com/js/polyfills-legacy-2_grxVzE.js
849 ms
IMAGESinstapaper.com/assets/landing_video_poster-tOGu2CgL.png
828 ms
FONTSinstapaper.com/fonts/LyonText-Bold-Web.woff
783 ms
JAVASCRIPTinstapaper.com/js/main-oBjO2yTX.js
774 ms
IMAGESinstapaper.com/static/img/apple-icon-72x72.png
773 ms
FONTSinstapaper.com/fonts/LyonDisplay-Regular-Web.woff
772 ms
CSSinstapaper.com/css/main-CTC2YTCX.min.css
766 ms
FONTSinstapaper.com/fonts/LyonText-Regular-Web.woff
764 ms
IMAGESinstapaper.com/static/img/apple-icon-144x144.png
764 ms
IMAGESinstapaper.com/static/img/apple-icon-57x57.png
764 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://instapaper.com/js/polyfills-legacy-2_grxVzE.jsjavascript200849 ms23.7 KB
https://instapaper.com/assets/landing_video_poster-tOGu2CgL.pngimages200828 ms58.2 KB
https://instapaper.com/fonts/LyonText-Bold-Web.wofffonts200783 ms57.8 KB
https://instapaper.com/js/main-oBjO2yTX.jsjavascript200774 ms569 B
https://instapaper.com/static/img/apple-icon-72x72.pngimages200773 ms4.9 KB
https://instapaper.com/fonts/LyonDisplay-Regular-Web.wofffonts200772 ms68.8 KB
https://instapaper.com/css/main-CTC2YTCX.min.csscss200766 ms23.5 KB
https://instapaper.com/fonts/LyonText-Regular-Web.wofffonts200764 ms56.7 KB
https://instapaper.com/static/img/apple-icon-144x144.pngimages200764 ms15.0 KB
https://instapaper.com/static/img/apple-icon-57x57.pngimages200764 ms3.6 KB
https://instapaper.com/static/img/apple-icon-114x114.pngimages200761 ms10.2 KB
https://instapaper.com/css/appCollectionManagement-D6o-EtzG.min.csscss200758 ms3.5 KB
https://instapaper.com/static/img/favicon.pngimages200753 ms957 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.