8 / 10←→

/geist/table

Unripe

https://vercel.com/geist/table ↗

Mobile

1/1 runs

Perf

A11y

SEO

100

Best

100

LCP

≤ 2.5 s

6.9 s

CLS

≤ 0.1

0.000

TBT

≤ 200 ms

298 ms

FCP

≤ 1.8 s

1.5 s

TTFB

≤ 800 ms

5 ms

≤ 3.4 s

5.0 s

Page weight

1.1 MB · 68 requests · third-party 0 B

JavaScript740 KB64%

Images38 KB3%

CSS85 KB7%

Fonts235 KB20%

Failing performance checks

5 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 →
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 42 KiB
Covered by: Cut and defer JavaScript →
−300 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 193 KiB
Covered by: Cut and defer JavaScript →
−1.1 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 890 ms
Covered by: Unblock the initial render →
−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 →

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

SEO Readiness (this page)

Title, meta, canonical, structured data, etc.

80/100

7 pass · 2 warn · 1 fail

✓
HTTPS
Served over HTTPS
!
Title tag
5 chars — aim for 30–60
!
Meta description
31 chars — aim for 70–160
✓
Canonical URL
https://vercel.com/geist/table
✓
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
3045 words in initial HTML
✓
Semantic HTML
Uses main, header, nav
✓
Heading outline
11 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
3045 words — substantial for a citation source
✓
Semantic structure
Uses <main>, <article> or <header>

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