Mobile
1/1 runs
Perf
59
A11y
90
SEO
100
Best
96
LCP
โค 2.5 s
6.3 s
CLS
โค 0.1
0.000
TBT
โค 200 ms
642 ms
FCP
โค 1.8 s
2.0 s
TTFB
โค 800 ms
96 ms
SI
โค 3.4 s
2.8 s
Largest Contentful Paint element
Type: imagediv#page-content > div.[&_[data-slot=note]_p]:my-0 > figure.m-0 > img.h-auto!
<img alt="Flags in Vercel Dashboard" data-docs-image="" loading="lazy" width="1337" height="860" decoding="async" data-nimg="1" class="h-auto! max-w-full rounded-(--geist-marketing-radius) border border-solid โฆ" style="color:transparent" srcset="/vc-ap-vercel-docs/_next/image?url=https%3A%2F%2F7nyt0uhk7sse4zvn.public.bโฆ" src="/vc-ap-vercel-docs/_next/image?url=https%3A%2F%2F7nyt0uhk7sse4zvn.public.bโฆ">
Page weight
1.9 MB ยท 119 requests ยท third-party 8 KB
JavaScript1.3 MB65%
Images56 KB3%
CSS148 KB7%
Fonts96 KB5%
Failing performance checks
9 items- โ700 msReduce JavaScript execution timeConsider 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.2.5ย sCovered by: Cut and defer JavaScript โ
- LCP request discoveryOptimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loadingCovered by: Unblock the initial render โ
- โ750 msRender-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 750ย msCovered 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 51ย KiBCovered by: Cut and defer JavaScript โ
- โ650 msMinimize main-thread workConsider 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 work4.0ย sCovered by: Cut and defer JavaScript โ
- 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.
Show 3 more checks โShow fewer โ
- Reduce unused CSSReduce 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 12ย KiBCovered by: Unblock the initial render โ
- Reduce 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 716ย KiBCovered by: Cut and defer JavaScript โ
- Improve image deliveryReducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image sizeEst savings of 42ย KiBCovered by: Right-size and modernize images โ
Failing accessibility checks
3 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.
- 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 โ
- 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 โ
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
8 pass ยท 2 warn ยท 0 fail
- โHTTPSServed over HTTPS
- !Title tag5 chars โ aim for 30โ60
- โMeta description108 chars
- โCanonical URLhttps://vercel.com/docs/flags
- !Open GraphPartial โ missing one of title/desc/image
- โTwitter Cardsummary_large_image
- โStructured data (JSON-LD)3 blocks
- โH1 headingExactly one H1
- โLanguage declaration<html lang="en">
- โViewport metaSet
AI Readiness (this page)
Structured data, server-rendered content, semantic HTML.
81/100
5 pass ยท 3 warn ยท 0 fail
- โSnippet directivesNo nosnippet / max-snippet / noai restrictions
- !Structured data (validated)TechArticle missing datePublished
- โServer-rendered content10716 words in initial HTML
- โSemantic HTMLUses main, header, footer, nav
- !Heading outlineLevel skips (H2โH4) โ broken hierarchy confuses chunk-based retrieval
- !Open Graph metadataPartial โ improves AI link previews
- โConsent wallNo consent-manager wall detected
- โAuthor / Organization markupPerson/Organization schema present
Citation-friendliness
How citable this page looks to an LLM answer engine.
100/100
- โCanonical URLPage has a stable URL to cite
- โAuthor identityPerson/Organization markup found
- โPublication datedatePublished / dateModified present
- โArticle schemaArticle-shaped JSON-LD present
- โContent depth10716 words โ substantial for a citation source
- โSemantic structureUses <main>, <article> or <header>
Schema.org types on this page
Vocabulary the page exposes to search engines and LLMs through JSON-LD blocks.
BreadcrumbListTechArticleWebSite
โ All 20 internal links we sampled on this page resolved.
Top third-party vendors
- vercel.sh7 KB
- Sentry1 KB