5 / 10←→

/legal

Unripe

https://stripe.com/legal ↗

Mobile

1/1 runs

Perf

A11y

SEO

100

Best

LCP

≤ 2.5 s

2.4 s

CLS

≤ 0.1

0.000

TBT

≤ 200 ms

793 ms

FCP

≤ 1.8 s

2.1 s

TTFB

≤ 800 ms

4 ms

≤ 3.4 s

2.1 s

Page weight

1.2 MB · 160 requests · third-party 1.2 MB

JavaScript1.0 MB83%

Images37 KB3%

CSS60 KB5%

Fonts58 KB5%

Failing performance checks

8 items

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.6 s
Covered by: Cut and defer JavaScript →
−800 ms
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 1,900 ms
Covered by: Unblock the initial render →
−1.9 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 →
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.
1.6 s
Covered by: Cut and defer JavaScript →
−850 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 264 KiB
Covered by: Cut and defer JavaScript →

Show 2 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 86 KiB
Covered by: Set long cache lifetimes for static assets →
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 14 KiB
Covered by: Cut and defer JavaScript →

Failing accessibility checks

2 items

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 →
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing best-practices checks

2 items

Uses third-party cookies
Third-party cookies may be blocked in some contexts. Learn more about preparing for third-party cookie restrictions.
9 cookies found
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.

75/100

6 pass · 3 warn · 1 fail

✓
HTTPS
Served over HTTPS
!
Title tag
5 chars — aim for 30–60
!
Meta description
5 chars — aim for 70–160
✓
Canonical URL
https://stripe.com/legal
✓
Open Graph
Complete
✓
Twitter Card
summary_large_image
✕
Structured data (JSON-LD)
No JSON-LD on this page
!
H1 heading
9 H1s — should be one
✓
Language declaration
<html lang="en-US">
✓
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
397 words in initial HTML
✓
Semantic HTML
Uses main, header, footer, nav
✓
Heading outline
9 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
397 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

Google Tag Manager676 KBblocking 733 ms
reddit26 KBblocking 23 ms
Twitter Online Conversion Tracking19 KBblocking 20 ms
LinkedIn Ads24 KBblocking 18 ms
Bing Ads17 KBblocking 11 ms