8 / 10←→

/changelog/ai-sdk-harness-native-subscription-authentication

Unripe

https://vercel.com/changelog/ai-sdk-harness-native-subscription-authentication ↗

Mobile

1/1 runs

Perf

A11y

SEO

100

Best

LCP

≤ 2.5 s

9.9 s

CLS

≤ 0.1

0.000

TBT

≤ 200 ms

222 ms

FCP

≤ 1.8 s

2.4 s

TTFB

≤ 800 ms

7 ms

≤ 3.4 s

5.1 s

Page weight

2.2 MB · 129 requests · third-party 1 KB

JavaScript1.6 MB74%

Images4 KB0%

CSS168 KB8%

Fonts226 KB10%

Failing performance checks

7 items

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 642 KiB
Covered by: Cut and defer JavaScript →
−2.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 990 ms
Covered by: Unblock the initial render →
−1.0 s
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 →
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 19 KiB
Covered by: Unblock the initial render →
−150 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
2.3 s
Covered by: Cut and defer JavaScript →
−200 ms
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 1 more check ↓

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 27 KiB
Covered by: Cut and defer JavaScript →

Failing accessibility checks

2 items

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Document does not have a main landmark.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing best-practices checks

1 item

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

SEO Readiness (this page)

Title, meta, canonical, structured data, etc.

85/100

8 pass · 1 warn · 1 fail

✓
HTTPS
Served over HTTPS
!
Title tag
77 chars — aim for 30–60
✓
Meta description
151 chars
✓
Canonical URL
https://vercel.com/changelog/ai-sdk-harness-native-subscription-authentication
✓
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
4278 words in initial HTML
✓
Semantic HTML
Uses header, footer, nav, article
✓
Heading outline
25 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
4278 words — substantial for a citation source
✓
Semantic structure
Uses <main>, <article> or <header>

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

Top third-party vendors

Sentry1 KB