AvocadoScore Free preview
ReportPagesTasks

AvocadoScore audit · vercel.com

vercel.com

Almost ripe

Real users are mostly fine — a focused round of fixes will get the site fully healthy.

Fix this firstUnblock the initial rendercritical · medium effort · 3 pages

This verdict weights real-user data (Chrome UX Report). Cold lab first-visits shown below run slower.

Mobile perf
63/100
Almost ripe
SEO ready
96/100
Ripe
AI ready
94/100
Ripe

Scanned 11 days ago3 pages31 views

What you’re not seeing yet

Your 3 sampled pages averaged 63 on mobile performance — we don’t know which of the other 7,940 pages are dragging that median. The full audit scans up to 100 of your most important pages so you can find the templates costing you traffic.

Pages we found but didn’t scan

/kb/fastify/docs/flags/sandbox/kb/bulletin/kb/ai-sdk/blog/edge-functions-generally-available/docs/agent/kb/guide/avoiding-duplicate-content-with-vercel-app-urls+4 more

7-day refund · no questions

Overview

Key findings

The headline takeaways, in plain English.

  1. 1In cold lab tests, 3 of 3 scanned pages render in the "Unripe" band (the overall verdict above weights real-user data, which is faster).
  2. 2Median mobile LCP is 6.1 s — about 2.4× the 2.5 s target.
  3. 3The biggest opportunity: Unblock the initial render — affects 3 pages.
  4. 4The heaviest page ships 1.4 MB of JavaScript — a primary cause of slow loads.
  5. 5Strengths: accessibility, SEO and best practices score well — focus effort on performance.
See the prioritized action plan →
Performance
63/100
9 issue types
Accessibility
92/100
5 issue types
On-page SEO
100/100
0 issue types
Best Practices
96/100
1 issue type
0Ripe0Almost ripe3Unripe

AI & search visibility

Can AI answer engines find, read and cite your site?

More people now ask ChatGPT, Perplexity and Claude instead of Googling. This section answers whether those answer engines can reach your content, understand it, and cite you — the audit other tools skip.

AI visibility verdict

AI agents can read your site; a few quick additions would make it easier to cite.

Fix next: declare a bot policy · add structured data — see the action plan for copy-paste fixes.

OG image quality

100/100

https://lishhsx6kmthaacj.public.blob.vercel-storage.com/og-home-not-x.png

Open Graph preview image as social platforms and AI answer engines see it
  • Reachable
    HTTP 200
  • Content-Type
    image/png
  • File size
    826.9 KB

Crawl-as-bot diff

Homepage · GPTBot UA

GPTBot sees 3,329 chars · browser sees 3,329 chars

100%

GPTBot sees 100% of the content a browser sees — essentially identical.

llms.txt content

1693 links · 21 sections

100/100
  • /llms.txt present
    HTTP 200
  • Has main heading
    # Title found
  • Link coverage
    1693 markdown links
  • Sections
    21 `##` sections
  • /llms-full.txt
    HTTP 200 — richer LLM context
> Full documentation content: https://vercel.com/docs/llms-full.txt # Documentation # Vercel Documentation [Vercel Documentation](https://vercel.com/docs): Vercel is the AI Cloud - a unified platform for building, deploying, and scaling AI-powered applications and agentic workloads. - [Getting S…

Robots.txt advisor

1 group · 1 sitemap ref

80/100
  • robots.txt present
    1 user-agent group
  • Allows crawlers
    `User-agent: *` permits standard crawling
  • Sitemap declared
    1 sitemap ref
  • AI bot policies
    No explicit policy for GPTBot, ClaudeBot, Google-Extended, etc. — decide and declare
  • Crawl-delay
    No crawl-delay — crawlers use their own pacing

Schema.org coverage

1/3 pages (33%)
Schema typePagesCoverage
SoftwareApplication133%

Readiness

SEO & AI Readiness

Two scorecards derived from the homepage HTML, robots.txt and AI-specific well-known files. The differentiating analysis no other tool does.

SEO Readiness
96/100
11 pass · 1 warn · 0 fail
AI Readiness
94/100
15 pass · 2 warn · 0 fail

Both scorecards are in good shape — the site is well-prepared for search and AI-era discovery.

SEO checklist

11/12 passing
  • !
    Meta description
    45 chars — aim for 70–160
11 passing checks — show all
  • HTTPS
    Served over HTTPS
  • Sitemap
    sitemap.xml present
  • robots.txt
    Present
  • Title tag
    31 chars
  • Canonical URL
    https://vercel.com
  • Open Graph
    Complete (title, description, image)
  • Twitter Card
    summary_large_image
  • Structured data (JSON-LD)
    1 block
  • H1 heading
    Exactly one H1
  • Language declaration
    <html lang="en">
  • Viewport meta
    Set

AI readiness — three pillars

15/17 passing
Access100

Can AI crawlers fetch the site at all?

Comprehension95

Once fetched, can they parse and chunk it?

Trust75

Can they attribute and date the content?

Access — Can AI crawlers fetch the site at all?

5/5 passing

All 5 checks pass. Nothing to fix here.

5 passing checks — show all
  • AI answer-engine access
    No restrictions on any of the 5 search/citation crawlers (default-allowed)
  • Training-crawler stance
    No training opt-outs declared — content may be used for model training (5 tokens checked)
  • Search-index crawlers (AI surfaces)
    Googlebot and Bingbot can crawl — the indexes behind AI Overviews, ChatGPT search and Copilot can see the site
  • CDN / firewall gate
    GPTBot sees 100% of the content a browser sees — essentially identical.
  • Snippet directives
    No nosnippet / max-snippet / noai restrictions

Comprehension — Once fetched, can they parse and chunk it?

9/10 passing
  • !
    RSS/Atom feed
    No feed advertised in <head> — several AI systems ingest feeds for freshness
9 passing checks — show all
  • /llms.txt
    Present — AI-friendly content map
  • /llms-full.txt
    Present — expanded LLM context
  • Structured data (validated)
    1 block, all required properties present (Offer, Organization, SoftwareApplication)
  • Server-rendered content
    8143 words in initial HTML
  • Semantic HTML
    Uses main, header, footer, nav
  • Heading outline
    30 headings in a clean hierarchy
  • Open Graph metadata
    Complete
  • Sitemap freshness
    sitemap.xml carries <lastmod> dates — recrawl prioritization works
  • Consent wall
    No consent-manager wall detected

Trust — Can they attribute and date the content?

1/2 passing
  • !
    Content dates
    No datePublished/dateModified in structured data — answer engines can't judge freshness
1 passing check — show all
  • Author / Organization markup
    Person/Organization schema present

AI bot policies (robots.txt)

10 bots tracked
No explicit policy for any of 10 tracked AI bots — implicit allow.
Show all 10 bots
BotVendorStatus
GPTBotOpenAINot specified
OAI-SearchBotOpenAINot specified
ChatGPT-UserOpenAINot specified
ClaudeBotAnthropicNot specified
Claude-UserAnthropicNot specified
Google-ExtendedGoogleNot specified
PerplexityBotPerplexityNot specified
Perplexity-UserPerplexityNot specified
Applebot-ExtendedAppleNot specified
CCBotCommon CrawlNot specified

Declare a policy either way so the intent is clear — see the action plan for a copy-paste robots.txt block.

Readiness is sampled on the site homepage; deeper pages may differ. AI bot policies follow the llms.txt proposal and the established robots.txt convention.

Deep dive

Performance analysis

Where this site stands against its peers, which viewport is the weak link, the slowest pages, and the issues that recur most.

Performance vs peers

At 63/100, this site is above the Next.js site (peer median 55).

64th
percentile (est.)
WorstNext.js siteBest

Mobile vs desktop

Mobile
63/100
Desktop
97/100

Mobile runs 34 points behind desktop — most of the slowness lives on phones.

  • /about5799 −42
  • /pricing5694 −38
  • /7697 −21

Slowest pages

  • 1
    /about
    perf 57/100
    10.9 s
  • 2
    /pricing
    perf 56/100
    6.1 s
  • 3
    /
    perf 76/100
    5.4 s

Ranked by mobile LCP (Largest Contentful Paint).

Most frequent issues

Performance: 9Accessibility: 5Best practices: 1
  • Render-blocking requests
    3 pages · 100%
  • `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
    3 pages · 100%
  • Browser errors were logged to the console
    3 pages · 100%
  • Forced reflow
    3 pages · 100%
  • Legacy JavaScript
    3 pages · 100%
  • Network dependency tree
    3 pages · 100%
  • Reduce unused CSS
    3 pages · 100%
  • Reduce unused JavaScript
    3 pages · 100%

Core Web Vitals

How fast your site really is

Real-user experience from the Chrome UX Report (p75, 28-day window). Lab metrics below show cold first-visit timings.

Real users · page-level
LCP
≤ 2.5 s
1.8 s
FAST
CLS
≤ 0.1
0.000
FAST
INP
≤ 200 ms
no data
Lab · median of scanned pages
LCP
≤ 2.5 s
6.1 s
CLS
≤ 0.1
0.000
TBT
≤ 200 ms
457 ms
FCP
≤ 1.8 s
1.9 s
TTFB
≤ 800 ms
14 ms
SI
≤ 3.4 s
4.7 s

Page Weight

Resource breakdown

Pages average 2.1 MB across 124 requests. Third-party scripts add 20 KB on top.

  • JavaScript1.3 MB62%
  • Images177 KB8%
  • CSS147 KB7%
  • Fonts226 KB11%
  • Other258 KB12%

Heaviest page: /about at 2.5 MB over 155 requests.

Deep dive

Resource intelligence

Where time and bytes are going across your site — the specific vendors and code paths behind the totals.

Top third-party vendors

Site-wide totals
VendorTotal bytesBlockingPages
Sentry4 KB0 ms3
vercel-storage.com57 KB0 ms1

Main-thread time

Average per page · 3.0 s
  • Script evaluation1.6 s51%
  • Style + layout511 ms17%
  • Script parse / compile422 ms14%
  • Other379 ms12%
  • Parse HTML66 ms2%
  • Garbage collection61 ms2%
  • Paint + composite34 ms1%

Image format breakdown

13% modern (WebP / AVIF)
  • png382 KB
  • svg79 KB
  • webp57 KB
  • avif13 KB

Technology

Detected stack

What we recognised from the homepage HTML, response headers and DNS. Used to tailor stack-specific recommendations.

Framework
Next.js
Hosting
Vercel

Site health

Security, compression and SEO hygiene

Headers, compression and cross-page duplicates checked on the homepage. These are the basics a professional site is expected to get right.

Security headers

7 pass · 3 warn · 0 fail

85/100
  • Strict-Transport-Security
    max-age=31536000 · includeSubDomains · preload
  • !
    Content-Security-Policy
    Present but uses 'unsafe-inline' or 'unsafe-eval' — weakens protection
  • X-Frame-Options
    DENY
  • X-Content-Type-Options
    nosniff
  • Referrer-Policy
    origin-when-cross-origin
  • !
    Permissions-Policy
    Missing — no explicit restriction on browser features (camera, geo, etc.)
  • Exposed secrets
    No live API keys or private keys found in the served HTML
  • Mixed content
    No insecure http:// subresources on the page
  • Outdated JS libraries
    No known-vulnerable library versions detected in page scripts
  • !
    Cookie security flags
    Homepage cookie is missing HttpOnly — session cookies without these are exposed to theft / CSRF

Compression & cache

Content-Encoding
Brotli
Cache-Control
good
public, max-age=0, must-revalidate

Action Plan

Root-cause groupings, sequenced by effort. Each card opens a ready-to-paste task you can create in Jira or Linear with one click.

Quick wins
Under a day each — start here.
  1. 01Address accessibility gaps⚡ quick win
  2. 02Declare a policy for AI crawlers⚡ quick win
Moderate effort
A few days each — book this sprint.
  1. 01Unblock the initial render
  2. 02Right-size and modernize images
  3. 03Add Schema.org structured data
Larger projects
A week+ each — scope and plan.
  1. 01Cut and defer JavaScript
Filter·Sort
01 / 06

Unblock the initial render

Critical·Medium effort·Affects 3 pages·~820 ms faster
Create ticket →

CSS and JavaScript in the critical path delay first paint — visitors stare at a blank screen, and Largest Contentful Paint (a Google ranking signal) suffers.

Impact — Largest Contentful Paint is a Google ranking signal. Sites in the slowest quartile of their category see 30–50% less organic search traffic than faster peers.

Found on this site~820 ms faster if fixed
  • ·Render-blocking requests — Est savings of 1,380 ms
  • ·Reduce unused CSS — Est savings of 38 KiB
Seen on:/about/pricing/
Steps (4)
  1. 1.Inline critical above-the-fold CSS and defer the rest.
  2. 2.Add async or defer to render-blocking scripts.
  3. 3.Preload the LCP image and key fonts so the browser discovers them early.
  4. 4.Remove unused CSS rules from above-the-fold stylesheets.
  5. For your stack
  6. 1.Use next/font so fonts do not block render.
  7. 2.Avoid importing large global CSS; prefer per-component styles.
03 / 06

Cut and defer JavaScript

Critical·Large effort·Affects 3 pages·~1.5 s faster
Create ticket →

Large scripts block the browser’s main thread, so the page looks loaded but does not respond to taps or clicks. This is the most common cause of a slow mobile experience and directly drives up bounce rate.

Impact — Heavy JavaScript is the #1 driver of slow mobile sites — 53% of mobile users abandon pages that take longer than 3 seconds to load (Google mobile-speed research).

Found on this site~1.5 s faster if fixed
  • ·Reduce unused JavaScript — Est savings of 503 KiB
  • ·Minimize main-thread work — 3.7 s
  • ·Reduce JavaScript execution time — 1.9 s
  • ·Legacy JavaScript — Est savings of 26 KiB
Seen on:/about/pricing/
Steps (4)
  1. 1.Audit the bundle to find the largest dependencies (a bundle analyzer or source-map-explorer).
  2. 2.Code-split so route- and below-the-fold code loads on demand instead of upfront.
  3. 3.Remove or replace heavy third-party scripts; load non-critical ones with async/defer or after first interaction.
  4. 4.Drop legacy polyfills and transpilation targets that modern browsers no longer need.
  5. For your stack
  6. 1.Use next/dynamic to lazy-load heavy components.
  7. 2.Run @next/bundle-analyzer to find oversized chunks.
  8. 3.Set a modern browserslist so Next.js stops shipping legacy transforms.
02 / 06

Address accessibility gaps

High·Small effort·Affects 1 page·⚡ Quick win
Create ticket →

Accessibility issues exclude users of assistive technology and create legal exposure (ADA / European Accessibility Act). Many fixes also help SEO.

Impact — About 15% of users have a disability (WHO). Accessibility gaps both exclude these users and create ADA/EAA compliance risk in the US and EU.

Steps (3)
  1. 1.Give interactive elements and dialogs accessible names (aria-label or visible text).
  2. 2.Ensure every meaningful image has descriptive alt text.
  3. 3.Check color contrast meets WCAG AA.
04 / 06

Declare a policy for AI crawlers

Medium·Small effort·Affects 1 page·⚡ Quick win
Create ticket →

Answer engines like ChatGPT, Perplexity and Claude crawl with named bots (GPTBot, ClaudeBot, Google-Extended…). With no explicit robots.txt rule you have made no decision — you neither invited them in to be cited nor kept them out. Either choice is fine; silence isn’t.

Impact — AI answer engines are a fast-growing discovery channel. Sites they can’t identify a policy for are crawled on the bot’s terms, and sites that block them forfeit citations — both are decisions worth making deliberately.

Found on this site
  • ·Unspecified: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, Google-Extended, PerplexityBot, Perplexity-User, Applebot-Extended, CCBot
Seen on:/robots.txt
Copy-paste fix
# Allow AI answer engines to read and cite your content:
User-agent: GPTBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Claude-User
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Perplexity-User
Allow: /

User-agent: Applebot-Extended
Allow: /

User-agent: CCBot
Allow: /

# …or block them from training/crawling instead — pick one:
# (replace "Allow: /" with "Disallow: /" above)
Steps (4)
  1. 1.Decide whether you want AI answer engines to read and cite your content.
  2. 2.Add an explicit Allow or Disallow rule for each major AI bot in robots.txt.
  3. 3.If you allow them, make sure your key content is server-rendered so they can actually read it.
  4. 4.Re-run the readiness checker to confirm the policy is detected.
05 / 06

Right-size and modernize images

Medium·Medium effort·Affects 2 pages
Create ticket →

Oversized images waste bandwidth and slow the largest element on the page. On mobile connections this is often the single biggest load-time cost.

Impact — Images account for roughly 25% of an average mobile page (HTTP Archive). Every MB of unoptimized images adds 1–2 seconds of mobile load time.

Found on this site
  • ·Improve image delivery — Est savings of 349 KiB
Seen on:/about/
Steps (4)
  1. 1.Serve images at the dimensions they are displayed, with srcset for different screen sizes.
  2. 2.Use modern formats (WebP/AVIF) with fallbacks.
  3. 3.Lazy-load below-the-fold images.
  4. 4.Compress images — aim well under 200 KB for most photos.
  5. For your stack
  6. 1.Use the next/image component — it handles sizing, modern formats and lazy-loading automatically.
06 / 06

Add Schema.org structured data

Medium·Medium effort·Affects 2 pages
Create ticket →

Schema.org JSON-LD tells search engines and answer engines what each page is — an Organization, an Article, a Product, an FAQ. Pages with structured data earn richer search results and are easier for LLMs to summarize and cite accurately.

Impact — Structured data is a low-risk SEO and AI-visibility win: it doesn’t change your design but materially improves how engines understand and present your pages.

Found on this site
  • ·Present: SoftwareApplication (1)
Copy-paste fix
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "vercel.com",
  "url": "https://vercel.com",
  "logo": "https://vercel.com/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/your-company",
    "https://twitter.com/your-handle"
  ]
}
</script>
Steps (4)
  1. 1.Add an Organization + WebSite schema to your homepage (identity for the whole site).
  2. 2.Add BreadcrumbList to section pages so engines understand your hierarchy.
  3. 3.Add page-type schema where it fits — Article/BlogPosting on posts, FAQPage on Q&A, Product on product pages.
  4. 4.Validate with Google’s Rich Results Test before shipping.

Shipped a fix? Open the task list or hit ↻ Re-scan in the header — the comparison shows what moved.

Detail

Per-page results

Mobile metrics shown. Click a row for the full per-page deep dive — LCP element, page weight breakdown, top failing checks.

PagePerf
/about57
/pricing56
/76

3 of 3 pages scanned successfully. Each row links to the full per-page report with mobile + desktop side by side.

Coverage

Scan coverage

Pages were discovered via sitemap and sampled across URL patterns. Issues found on a sampled page very likely affect the rest of its pattern group.

Discovered
7943
Sampled
3
Scanned OK
3
Failed
0

Methodology

How we measured this

Every page measured with Google PageSpeed Insights (1 run per page per viewport — quick scan). Real-user data, where shown, comes from the Chrome UX Report.

  • Lab data is a cold first visit from Google's US infrastructure; real users with warm caches and in other regions will differ.
  • Mobile is emulated on throttled slow-4G; desktop is unthrottled. Only public pages are scanned.
  • Quick scan (1 run/page) — upgrade to a paid scan for median-of-3 accuracy.

Full deep-dive on every check at /methodology.

Share

Embed this badge anywhere

A live SVG badge — embeds in your README, site footer, or blog post. Updates whenever you re-scan.

Public report URL

https://avocadoscore.io/r/509903f8-ee6d-4d7d-9c19-1e27de86fb0c

Markdown (for README)

[![AvocadoScore — overall verdict](https://avocadoscore.io/api/scans/509903f8-ee6d-4d7d-9c19-1e27de86fb0c/badge?metric=verdict)](https://avocadoscore.io/r/509903f8-ee6d-4d7d-9c19-1e27de86fb0c)

HTML (for site footer)

<a href="https://avocadoscore.io/r/509903f8-ee6d-4d7d-9c19-1e27de86fb0c"><img src="https://avocadoscore.io/api/scans/509903f8-ee6d-4d7d-9c19-1e27de86fb0c/badge?metric=verdict" alt="AvocadoScore — overall verdict" /></a>

Next Steps

Where to go from here

  1. 1Start this week. Knock out the 2 quick wins from the Action Plan — small effort, immediate gain.
  2. 2Re-scan after each round of fixes. Hit Re-scan in the header after each round — the comparison shows what moved and what didn’t.

Free preview · 3 of 7,943 pages

Want this depth on every page?

You've seen the format. The Full audit takes the same lens across 7,940 more pages you can't see yet — and ships the result as one ranked fix list your engineer can act on.

  • Median of 3 PageSpeed runs per page (vs 1 in the preview) — stable numbers you can ship from
  • Up to 100 pages — covers /pricing, /checkout, and every template that matters
  • Per-page deep dives: LCP element, named offenders, third-party impact
  • Plain-English fix list with effort estimates in dev-weeks
  • 3 free re-runs included — re-scan after every release at no extra cost
  • 7-day refund, no questions, no “please tell us why”

One-time · No subscription · 7-day refund

This audit was run on AvocadoScore

vercel.com scored 63 on Mobile Perf. What about yours?

Performance, SEO, and how Claude, GPT and Gemini see your site. $29, one-time. Same report format, your domain.