linear.app website review

48 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.

About 250 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

Your mobile performance score is 40 (desktop: 43). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 4.5 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 4,427 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

13 long tasks block the main thread while loading, the longest for 319 ms. During a long task the page ignores taps.

6 images could be 214 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

11 files are served with short cache lifetimes, so returning visitors download them again (86 KiB).

About 26 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

8 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Your largest element takes 17.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

The page becomes fully interactive after 17.7 s. Good is under 3.8 s.

The first text or image appears after 4.9 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 9.6 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 674 ms in total while the page loads. Good is under 200 ms.

Real visitors wait 229 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 217 ms to 212 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 6.3 s to 6.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.9 MB in 385 requests on a phone: scripts 1.4 MB (290), fonts 504 KiB (2) and other files 325 KiB (11). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.82 g of CO₂e: 98.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

11 tap targets are too small or too close together to hit reliably with a finger.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 64 characters: “Purpose-built for planning and building products with AI agents.”. 70 to 160 characters is enough to sell the click.

The homepage links to 69 pages on linear.app and 4 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

/homepage declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and /homepage all use the title “Linear – The system for product development”. Search engines can't tell which page to show for a search, so each competes with the others.

/now/introducing-loops has no meta description, so Google writes the search snippet from whatever text it finds.

/changelog/2026-10-08-stacked-pull-requests, /changelog/2026-09-24-new-controls-for-linear-coding-agent, /changelog/2026-09-14-loops-for-product-management and /changelog/2026-09-03-priority-inbox use the same meta description. A description written for each page earns more clicks.

/changelog/2026-10-08-stacked-pull-requests, /changelog/2026-09-24-new-controls-for-linear-coding-agent, /changelog/2026-09-14-loops-for-product-management and /changelog/2026-09-03-priority-inbox have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.

27 of 43 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

Chrome logged issues while loading the page (“Content security policy”).

Large scripts ship without source maps.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

linear.app has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

linear.app's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 5 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 559 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.