7 / 10←→

/ai

Unripe

https://linear.app/ai ↗

Mobile

1/1 runs

Perf

A11y

SEO

Best

LCP

≤ 2.5 s

14.3 s

CLS

≤ 0.1

0.000

TBT

≤ 200 ms

321 ms

FCP

≤ 1.8 s

4.7 s

TTFB

≤ 800 ms

12 ms

≤ 3.4 s

6.5 s

Page weight

5.5 MB · 342 requests · third-party 0 B

JavaScript1.2 MB21%

Images229 KB4%

CSS163 KB3%

Fonts504 KB9%

Failing performance checks

11 items

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,400 ms
Covered by: Unblock the initial render →
−3.4 s
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
2.8 s
Covered by: Cut and defer JavaScript →
−300 ms
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Est savings of 2 KiB
Covered by: Unblock the initial render →
−150 ms
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 21 KiB
Covered by: Unblock the initial render →
−150 ms
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 167 KiB
Covered by: Cut and defer JavaScript →
−1.1 s
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 →

Show 5 more checks ↓

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 →
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 →
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 136 KiB
Covered by: Right-size and modernize images →
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 5,625 KiB
Covered by: Reduce total page weight →
Use efficient cache lifetimes
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Est savings of 67 KiB
Covered by: Set long cache lifetimes for static assets →

Failing accessibility checks

1 item

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 →

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

2 items

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

SEO Readiness (this page)

Title, meta, canonical, structured data, etc.

90/100

9 pass · 0 warn · 1 fail

✓
HTTPS
Served over HTTPS
✓
Title tag
58 chars
✓
Meta description
131 chars
✓
Canonical URL
https://linear.app/ai
✓
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.

81/100

6 pass · 1 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
3782 words in initial HTML
✓
Semantic HTML
Uses main, header, footer, nav
✓
Heading outline
29 headings in a clean hierarchy
✓
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
3782 words — substantial for a citation source
✓
Semantic structure
Uses <main>, <article> or <header>

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

/ai