linear.app speed test — 20 Oct 2026

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

https://linear.app/

20 October 2026 at 16:25 UTC · Free test · report pt_b0b1c265363d

Re-test this page Test your own site

Grade

69/100

Performance70/100

Structure68/100

11 audit(s) passed, 5 need work

First byte (TTFB)614 msmeasured from this server

Fully loaded1.60 sfirst byte + slowest asset

Requests26document + assets

Page weight3.15 MBcompressed transfer

HTML document168.1 KBbr

ProtocolHTTP/3cloudflare

Third-party23.7 KBother hosts

Where the first byte went

DNS lookup 53 ms 9%
TCP connect 3 ms 0%
Server wait 558 ms 91%

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 byteslower than 64% of 4,999 pages tested here614 ms against a median of 448 ms

Page weightheavier than 89% of 4,999 pages tested here3.15 MB against a median of 650.3 KB

Fully loadedfaster than 64% of 4,999 pages tested here1.60 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 took 614 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
The page transfers 3.15 MB over 26 request(s). Images files are 95% of it, so resize and recompress the largest images before anything else.
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 took 2.50 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
The main thread was blocked for 514 ms, so taps and scrolling wait while scripts run.

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.

Mobile screenshot of linear.app — **Mobile** 390 × 844 · 83.5 KB · page is 5876 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 paint2.50 sgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time514 mslong tasks during load

First contentful paint1.12 sfirst content on screen

Browser page weight2.90 MB412 request(s), scripts included

Largest contentful paint2.50 s

Needs improvementgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time514 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

2.98 MB 95%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 614 ms. Of that, 558 ms was the server thinking and 56 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.

Image delivery and format

high impact

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

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

Total page weight

high impact

The page transfers 3.15 MB across 26 request(s), with the document itself at 168.1 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

HTML document size

medium impact

The document transfers 168.1 KB. A bloated document delays every other request, because nothing else can start until it is parsed.

Fix: Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.