9 / 10←→

/kb/bulletin

Ripe

https://vercel.com/kb/bulletin ↗

Mobile

1/1 runs

Perf

A11y

100

SEO

100

Best

LCP

≤ 2.5 s

2.4 s

CLS

≤ 0.1

0.000

TBT

≤ 200 ms

143 ms

FCP

≤ 1.8 s

1.7 s

TTFB

≤ 800 ms

116 ms

≤ 3.4 s

3.1 s

Page weight

2.4 MB · 139 requests · third-party 4 KB

JavaScript1.7 MB69%

Images34 KB1%

CSS158 KB6%

Fonts96 KB4%

Failing performance checks

4 items

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 600 ms
Covered by: Unblock the initial render →
−600 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 585 KiB
Covered by: Cut and defer JavaScript →
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 12 KiB
Covered by: Unblock the initial render →
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 29 KiB
Covered by: Cut and defer JavaScript →

Failing best-practices checks

2 items

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
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

SEO Readiness (this page)

Title, meta, canonical, structured data, etc.

90/100

9 pass · 0 warn · 1 fail

✓
HTTPS
Served over HTTPS
✓
Title tag
42 chars
✓
Meta description
72 chars
✓
Canonical URL
https://vercel.com/kb/bulletin
✓
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-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
3325 words in initial HTML
✓
Semantic HTML
Uses main, header, footer, nav
✓
Heading outline
24 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
3325 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

vercel.sh2 KB
Sentry1 KB
ctfassets.net1 KB