Mobile
1/1 runs
Perf
83
A11y
87
SEO
100
Best
96
LCP
โค 2.5 s
4.4 s
CLS
โค 0.1
0.000
TBT
โค 200 ms
0 ms
FCP
โค 1.8 s
2.1 s
TTFB
โค 800 ms
19 ms
SI
โค 3.4 s
2.1 s
Page weight
824 KB ยท 47 requests ยท third-party 0 B
JavaScript501 KB61%
Images2 KB0%
CSS150 KB18%
Fonts92 KB11%
Failing performance checks
5 items- Network dependency treeAvoid 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 โ
- โ150 msLegacy JavaScriptPolyfills 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 transpilingEst savings of 27ย KiBCovered by: Cut and defer JavaScript โ
- โ1.2 sRender-blocking requestsRequests 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,200ย msCovered by: Unblock the initial render โ
- Forced reflowA forced reflow occurs when JavaScript queries geometric properties (such asCovered by: Cut and defer JavaScript โ
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. - โ300 msReduce unused JavaScriptReduce 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 187ย KiBCovered by: Cut and defer JavaScript โ
Failing accessibility checks
4 items- Touch targets do not have sufficient size or spacing.Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
- 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 โ
- Heading elements are not in a sequentially-descending orderProperly 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 โ
- `[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.
Failing best-practices checks
1 item- Browser errors were logged to the consoleErrors 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.
90/100
9 pass ยท 0 warn ยท 1 fail
- โHTTPSServed over HTTPS
- โTitle tag48 chars
- โMeta description109 chars
- โCanonical URLhttps://vercel.com/pricing
- โOpen GraphComplete
- โTwitter Cardsummary_large_image
- โStructured data (JSON-LD)No JSON-LD on this page
- โH1 headingExactly one H1
- โLanguage declaration<html lang="en">
- โViewport metaSet
AI Readiness (this page)
Structured data, server-rendered content, semantic HTML.
75/100
5 pass ยท 2 warn ยท 1 fail
- โSnippet directivesNo nosnippet / max-snippet / noai restrictions
- โStructured data (validated)No JSON-LD โ answer engines have nothing structured to parse
- โServer-rendered content8611 words in initial HTML
- โSemantic HTMLUses main, header, footer, nav
- !Heading outlineLevel skips (H1โH3) โ broken hierarchy confuses chunk-based retrieval
- โOpen Graph metadataComplete
- โConsent wallNo consent-manager wall detected
- !Author / Organization markupNo author meta tag or Person/Organization schema
Citation-friendliness
How citable this page looks to an LLM answer engine.
58/100
- โCanonical URLPage has a stable URL to cite
- โAuthor identityNo author meta or schema โ citation confidence drops without a named source
- โPublication dateNo publication or modification date in JSON-LD โ answer engines deprioritize undated content
- !Article schemaNo Article / NewsArticle / BlogPosting schema โ limits rich-snippet eligibility
- โContent depth8611 words โ substantial for a citation source
- โSemantic structureUses <main>, <article> or <header>
โ All 20 internal links we sampled on this page resolved.