1 / 3←→

Home page

Unripe

https://linear.app/ ↗

Mobile

1/1 runs

Perf

A11y

SEO

Best

LCP

≤ 2.5 s

14.4 s

CLS

≤ 0.1

0.000

TBT

≤ 200 ms

1.2 s

FCP

≤ 1.8 s

12.2 s

TTFB

≤ 800 ms

53 ms

≤ 3.4 s

12.2 s

Desktop

1/1 runs

Perf

A11y

SEO

100

Best

LCP

≤ 2.5 s

2.5 s

CLS

≤ 0.1

0.000

TBT

≤ 200 ms

377 ms

FCP

≤ 1.8 s

2.2 s

TTFB

≤ 800 ms

49 ms

≤ 3.4 s

3.2 s

Page weight

4.2 MB · 406 requests · third-party 0 B

JavaScript1.5 MB35%

Images260 KB6%

CSS169 KB4%

Fonts504 KB12%

Failing performance checks

13 items

Forced reflow
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Covered by: Cut and defer JavaScript →
Reduce JavaScript execution time
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
2.0 s
Covered by: Cut and defer JavaScript →
−650 ms
Minimize main-thread work
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
5.6 s
Covered by: Cut and defer JavaScript →
−1.2 s
Render-blocking requests
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Est savings of 3,830 ms
Covered by: Unblock the initial render →
−3.9 s
Reduce unused JavaScript
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Est savings of 174 KiB
Covered by: Cut and defer JavaScript →
−900 ms
Network dependency tree
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Covered by: Unblock the initial render →

Show 7 more checks ↓

Use efficient cache lifetimes
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Est savings of 78 KiB
Covered by: Set long cache lifetimes for static assets →
Avoid enormous network payloads
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Total size was 4,280 KiB
Covered by: Reduce total page weight →
Improve image delivery
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Est savings of 151 KiB
Covered by: Right-size and modernize images →
Reduce unused CSS
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Est savings of 74 KiB
Covered by: Unblock the initial render →
Duplicated JavaScript
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Est savings of 13 KiB
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Est savings of 19 KiB
Covered by: Unblock the initial render →
Legacy JavaScript
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Est savings of 9 KiB
Covered by: Cut and defer JavaScript →

Failing accessibility checks

4 items

Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Covered by: Address accessibility gaps →
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Covered by: Address accessibility gaps →
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Covered by: Address accessibility gaps →
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Covered by: Address accessibility gaps →

Failing SEO checks (Lighthouse)

1 item

Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Covered by: Fix crawlability issues →

Failing best-practices checks

4 items

Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

SEO Readiness (this page)

Title, meta, canonical, structured data, etc.

90/100

9 pass · 0 warn · 1 fail

✓
HTTPS
Served over HTTPS
✓
Title tag
43 chars
✓
Meta description
64 chars
✓
Canonical URL
https://linear.app
✓
Open Graph
Complete
✓
Twitter Card
summary_large_image
✕
Structured data (JSON-LD)
No JSON-LD on this page
✓
H1 heading
Exactly one H1
✓
Language declaration
<html lang="en">
✓
Viewport meta
Set

AI Readiness (this page)

Structured data, server-rendered content, semantic HTML.

75/100

5 pass · 2 warn · 1 fail

✓
Snippet directives
No nosnippet / max-snippet / noai restrictions
✕
Structured data (validated)
No JSON-LD — answer engines have nothing structured to parse
✓
Server-rendered content
35437 words in initial HTML
✓
Semantic HTML
Uses main, header, footer, nav
!
Heading outline
Level skips (H1→H3) — broken hierarchy confuses chunk-based retrieval
✓
Open Graph metadata
Complete
✓
Consent wall
No consent-manager wall detected
!
Author / Organization markup
No author meta tag or Person/Organization schema

Citation-friendliness

How citable this page looks to an LLM answer engine.

58/100

✓
Canonical URL
Page has a stable URL to cite
✕
Author identity
No author meta or schema — citation confidence drops without a named source
✕
Publication date
No publication or modification date in JSON-LD — answer engines deprioritize undated content
!
Article schema
No Article / NewsArticle / BlogPosting schema — limits rich-snippet eligibility
✓
Content depth
35437 words — substantial for a citation source
✓
Semantic structure
Uses <main>, <article> or <header>

✓ All 20 internal links we sampled on this page resolved.