https://vercel.com·Oct 7, 2026, 02:06 PM UTC·26 technologies·AI

vercel.com

Built with Css3, Experiment Framework, Geist Font, Geist Pixel Font, Html5 and 21 more

https://vercel.com
Screenshot of vercel.com

Performance

TTFB

127ms

DOM Ready

657ms

Load Complete

694ms

Requests

110

Total Size

5746KB

Domains

3

Errors

3

4xx/5xx responses

Technologies

Other

Css3
AIhigh
Experiment Framework
Scripthigh
Geist Font
Script + AIhigh
Geist Pixel Font
AIhigh
Html5
Script + AIhigh
Inline Svgv1.1
Scripthigh
Inter Font
Scripthigh
Javascript
Script + AIhigh
Next Image Optimizationv16.4.0-canary.61
Scripthigh
Next Js
AIhigh
Nextjsv16.4.0
Scripthigh
Node Js
AIhigh
Nodejs
Scripthigh
Open Graphv1.0
Scripthigh
React
AIhigh
React Aria
Script + AIhigh
Roboto
Scripthigh
StripeassetsvNext.js
Scripthigh
Turbopack
Script + AIhigh
Vercelviad1
Scripthigh
Vercel Analytics
Script + AIhigh
Vercel Blob Storagev0.0.0
Scripthigh
Vercel Edge Network
Script + AIhigh
Vercel Hosting
AIhigh
Web App Manifest
Script + AIhigh
Typescript
AImedium

Company estimate

Company

Vercel

Cloud platform for deploying and hosting frontend applications and AI agents

AI valuation estimatemedium

$3.25B

Estimated annual tech spend

$25M

Founded

2015

HQ

San Francisco, California, USA

Employees

~500

The page title reads 'Agentic Infrastructure - Vercel' and the content/tech stack (Next.js, Vercel Edge Network, Vercel Hosting, Vercel Analytics, Vercel Blob Storage) unambiguously identify Vercel, the well-known private cloud hosting platform. Valuation of ~$3.25B and HQ/founding details come from prior knowledge of this confirmed company; page itself does not state financials.

SEO recommendations

62

SEO health score

Vercel's homepage has a clean technical baseline: a concise, keyworded title ("Agentic Infrastructure - Vercel"), a present meta description, explicit index/robots guidance, and well-optimized asset delivery (font/image preloads, srcset images, async JS). However, the provided HTML shows no structured data markup, and canonicalization, sitemap linking, internal-link depth, and OpenGraph tags could not be verified, so those areas need follow-up.

  • Add structured data to your websiteVery High

    No JSON-LD or schema.org markup of any kind appears in the provided HTML, so search engines receive no structured description of the organization, website, or primary entities on this page.

    → Add a JSON-LD block (WebSite + Organization with logo, sameAs social profiles, and SearchAction if Vercel has site search) in the <head> via Next.js metadata API.

    80%

    impact

  • Improve internal linkingHigh

    Body content was not included in the supplied HTML, so internal link depth and anchor quality on this homepage cannot be verified.

    → Confirm core destinations (Docs, Pricing, Templates, Dashboard) are reachable within two clicks of the homepage and use descriptive, keyword-bearing anchor text.

    45%

    impact

  • Trailing slashes may cause duplicate contentHigh

    No canonical link tag is visible in the supplied (trimmed) head, so canonicalization between 'vercel.com' and 'vercel.com/' cannot be confirmed for this page.

    → Ensure every page emits a self-referencing <link rel="canonical"> pointing to https://vercel.com/ and keep slash handling consistent sitewide.

    35%

    impact

  • Optimize your sitemapMedium

    No sitemap link element or robots.txt reference exists in the provided HTML (sitemap discovery normally happens via robots.txt, which was not supplied).

    → Verify https://vercel.com/sitemap.xml is served, is referenced in robots.txt, and lists this homepage with its canonical URL and a correct lastmod.

    30%

    impact

  • Review similar contentMedium

    Body content was not supplied to check for thin or duplicate text, and the homepage's broad "Agentic Infrastructure" positioning risks cannibalizing subpages that target similar developer keywords.

    → Audit overlap between the homepage and near-duplicate marketing/product pages so each URL provides distinct value and unique intent coverage.

    30%

    impact

  • Avoid internal redirectsMedium

    HTML alone cannot reveal server-side redirects; no crawl evidence for redirect chains on vercel.com paths was provided.

    → Crawl https://vercel.com and adjacent URLs to confirm the homepage returns 200 directly without redirect chains that would waste crawl budget.

    25%

    impact

  • Improve meta descriptionsMedium

    A meta description is present but only ~44 characters versus the ~150-160 character ideal, and "The autonomous stack for every app and agent." lacks distinct keyword or CTR hooks.

    → Expand it toward ~150 characters with concrete hooks and keywords, e.g., 'Deploy apps, preview every change, and run agents on one autonomous stack — Vercel.'

    25%

    impact

  • Content to-do listMedium

    Semantic content depth cannot be assessed from the provided HTML alone, but a homepage of this importance should lead with a clear H1 and sections mapped to core use cases.

    → Ensure the homepage has exactly one H1 and descriptive H2 sections covering deploy, preview, functions, and agents to reinforce topical relevance.

    20%

    impact

  • Add OpenGraph tagsLow

    No og:/twitter: meta tags are visible in the provided HTML, so link previews on X, LinkedIn, and Slack may render without a title, image, or description.

    → Add og:title, og:description, og:image, and twitter:card meta tags (via the Next.js metadata API) so shared links display complete rich cards.

    15%

    impact

  • Improve page titlesLow

    Title tag is present, 33 characters long, with the primary keyword phrase "Agentic Infrastructure" front-loaded and the "Vercel" brand at the end — well inside the ideal length window.

    → Keep the current format but monitor head-term coverage (e.g., deploy, hosting, cloud platform) so the homepage still surfaces for broad developer-platform queries.

    10%

    impact

  • Improve page speedLow

    The page shows strong asset-delivery signals: woff2 font and image preloads, imagesrcset-based responsive images, and dozens of JS chunks loaded asynchronously with fetchpriority="low".

    → Validate Core Web Vitals (LCP, CLS, INP) in PageSpeed Insights and ensure the many async chunks never block the render-critical path on slow connections.

    10%

    impact

AI-generated SEO assessment · impact = estimated priority for this page

Specification compliance (3 shortcomings)

94

Specification compliance score

24/27 required and 33/37 recommended practices implemented. 3 shortcomings to address.

24/27

Required

33/37

Recommended

3

Shortcomings

94%

Overall

  • robots.txtRecommended

    robots.txt is served.

    100%

    Implemented

  • XML sitemapsRecommended

    An XML sitemap is present or referenced.

    100%

    Implemented

  • Sitemap index filesRecommended

    No sitemap index — only needed once you exceed 50k URLs / 50MB.

    —

    Needs review

  • Image and video sitemap extensionsOptional

    No image/video sitemap extensions detected.

    —

    Needs review

  • URL structureRecommended

    URL path is clean and readable.

    100%

    Implemented

  • Redirects (301/302/308)Required

    http:// redirects to https with a 3xx status.

    100%

    Implemented

  • Soft 404sAvoid

    Nonexistent paths return a real 404/410.

    100%

    Implemented

  • Meta robots and X-Robots-TagRequired

    Indexing is not being blocked by robots meta / X-Robots-Tag.

    100%

    Implemented

  • Heading hierarchyRequired

    Exactly one <h1> heading.

    100%

    Implemented

  • Internal linkingRecommended

    153 internal links found.

    100%

    Implemented

  • Structured data (JSON-LD)Recommended

    JSON-LD structured data present.

    100%

    Implemented

  • BreadcrumbsRecommended

    No breadcrumb structured data or navigation found.

    0%

    Not implemented

  • IndexNowOptional

    IndexNow integration cannot be detected from a page scan.

    —

    Needs review

  • HTTPS and TLSRequired

    Page is served over HTTPS.

    100%

    Implemented

  • HSTS (Strict-Transport-Security)Required

    No Strict-Transport-Security header — browsers will not enforce HTTPS.

    0%

    Not implemented

  • Content Security Policy (CSP)Recommended

    Content-Security-Policy header present.

    100%

    Implemented

  • /.well-known/security.txtRecommended

    security.txt is published.

    100%

    Implemented

  • X-Content-Type-Options: nosniffRequired

    nosniff header present.

    100%

    Implemented

  • Clickjacking protectionRequired

    Framing is restricted (frame-ancestors / X-Frame-Options).

    100%

    Implemented

  • Referrer-PolicyRecommended

    Referrer-Policy header present.

    100%

    Implemented

  • Permissions-PolicyRecommended

    Permissions-Policy header present.

    100%

    Implemented

  • Subresource Integrity (SRI)Recommended

    No cross-origin scripts requiring SRI.

    100%

    Implemented

  • Cookie attributes — Secure, HttpOnly, SameSiteRequired

    No cookies set on the document response.

    100%

    Implemented

  • DNS CAA recordsRecommended

    CAA records are not collected by the scanner — check your DNS provider.

    —

    Needs review

  • DNSSECOptional

    DNSSEC status is not collected by the scanner.

    —

    Needs review

  • Agent readinessRecommended

    Some agent-readiness signals present (llms.txt and/or structured data).

    100%

    Implemented

  • /llms.txtRecommended

    /llms.txt is published.

    100%

    Implemented

  • /llms-full.txtOptional

    /llms-full.txt is published.

    100%

    Implemented

  • Per-page Markdown source endpointsRecommended

    No Markdown source endpoint detected — recommended for content/doc sites.

    —

    Needs review

  • robots.txt for AI crawlersRecommended

    robots.txt has no explicit AI-crawler rules — state your stance on GPTBot/ClaudeBot/etc.

    0%

    Not implemented

  • Content Signals in robots.txtOptional

    Content Signals present in robots.txt.

    100%

    Implemented

  • Web Bot Auth — verifiable bot identityOptional

    Web Bot Auth support cannot be detected from a scan.

    —

    Needs review

  • Stable URLsRequired

    URL has no obvious session/volatile parameters.

    100%

    Implemented

  • Structured data for agentsRecommended

    JSON-LD structured data present for agents.

    100%

    Implemented

  • Machine-readable formatsRecommended

    No machine-readable alternates detected — recommended for listings/data pages.

    —

    Needs review

  • HTTP Link headers for discoveryRecommended

    HTTP Link header present for discovery.

    100%

    Implemented

  • MCP and tool discoveryOptional

    No MCP/tool discovery endpoint — optional.

    —

    Needs review

  • A2A agent cardsOptional

    No A2A agent card — optional.

    —

    Needs review

  • Agent Skills discoveryRecommended

    Agent Skills discovery cannot be detected automatically.

    —

    Needs review

  • DNS for AI Discovery (DNS-AID)Optional

    DNS-AID records are not collected by the scanner.

    —

    Needs review

  • NLWeb — conversational interface discoveryOptional

    NLWeb support cannot be detected automatically.

    —

    Needs review

  • WebMCP — browser-native tools for agentsOptional

    WebMCP support cannot be detected automatically.

    —

    Needs review

  • Schemamap — discoverable JSON-LD endpointsOptional

    Schemamap support cannot be detected automatically.

    —

    Needs review

  • Core Web Vitals (LCP, INP, CLS)Required

    Lab load completed in 694ms (a proxy). Confirm LCP/INP/CLS with field data.

    85%

    Partial

  • Image optimisationRequired

    2/2 raster images use modern formats (WebP/AVIF).

    100%

    Implemented

  • Lazy loading images, iframes, and videoRecommended

    loading="lazy" is used.

    100%

    Implemented

  • Preload, prefetch, preconnectRecommended

    Resource hints (preload/preconnect/…) present.

    100%

    Implemented

  • Cache-Control headersRequired

    Cache-Control set on the document (public, max-age=0, must-revalidate).

    100%

    Implemented

  • No-Vary-Search response headerRecommended

    Not set — optional; helps cache/prefetch URLs that differ only by tracking params.

    —

    Needs review

  • Compression (gzip, brotli, zstd)Required

    Document is compressed (br).

    100%

    Implemented

  • Web font loadingRecommended

    Font-display/font preload optimisation detected.

    100%

    Implemented

  • Critical CSS and render-blocking resourcesRecommended

    3 render-blocking stylesheets in <head> — inline critical CSS and defer the rest.

    64%

    Partial

  • Script loading — defer, async, moduleRecommended

    44/74 external scripts use defer/async/module — add defer to the rest.

    59%

    Partial

  • HTTP/2 and HTTP/3Recommended

    Protocol version not captured — verify HTTP/2/3 is enabled at your edge/CDN.

    —

    Needs review

  • Speculation RulesRecommended

    Speculation Rules present for instant navigations.

    100%

    Implemented

  • Resource hints overviewRecommended

    Resource hints are in use.

    100%

    Implemented

  • View TransitionsRecommended

    No View Transitions detected — optional polish for navigations.

    —

    Needs review

  • Back/forward cache (BFCache)Recommended

    BFCache eligibility needs runtime testing.

    —

    Needs review

  • Visibility-aware renderingRecommended

    content-visibility used to skip offscreen rendering.

    100%

    Implemented

  • CSS containmentOptional

    CSS containment in use.

    100%

    Implemented

  • Scroll-driven animationsOptional

    Not detected — optional.

    —

    Needs review

  • Scrollbar gutterRecommended

    No scrollbar-gutter — optional; prevents layout shift when scrollbars toggle.

    —

    Needs review

  • Custom error pages (404, 500)Required

    404 status is correct but the body is sparse — add a branded, helpful 404 page.

    60%

    Partial

  • Maintenance pages and 503Recommended

    Maintenance behaviour can only be observed during downtime.

    —

    Needs review

  • Offline support and service workersOptional

    No service worker detected — optional offline/PWA support.

    —

    Needs review

  • Web app manifestRecommended

    Web app manifest linked and reachable.

    100%

    Implemented

  • Monitoring and uptimeRecommended

    Monitoring is operational and cannot be detected from the page.

    —

    Needs review

Deterministic audit against the website specification checklist. “Needs review” items can't be confirmed from a headless scan and are excluded from the score.

DNS & Infrastructure

DNSVercel
EmailGoogle Workspace
HostingAmazon (AS16509, Vercel edge)

IP Addresses

64.239.109.65
Vercel, Inc
🇺🇸Walnut, United States
64.239.123.129
Vercel, Inc
🇺🇸Walnut, United States

Nameservers

ns1.vercel-dns.com
ns2.vercel-dns.com

Mail Servers (MX)

1aspmx.l.google.com
5alt1.aspmx.l.google.com
5alt2.aspmx.l.google.com
10aspmx2.googlemail.com
10aspmx3.googlemail.com

AI Analysis Notes

  • ·DNS hosted on Vercel's own nameservers (ns1/ns2.vercel-dns.com)
  • ·Email handled by Google Workspace (aspmx.l.google.com, alt1/alt2, aspmx2/3.googlemail.com)
  • ·A records resolve to Vercel's edge on Amazon AS16509 (Vercel, Inc org)
  • ·No SPF (v=spf1) or DMARC records present in the provided TXT data
  • ·TXT records are almost entirely third-party domain verifications: Cursor, DocuSign (x2), Sourcegraph Amp, Zoom, Apple, Stripe (x2), Gather, H1, Notion, Remote, Plain, Anthropic, Salesforce Marketing Cloud (SFMC), Whimsical, and a SAML domain challenge
  • ·Vercel's own platform is fronted by its edge network on AWS

Email & Deliverability

75

Email health score

Google Workspace

vercel.com is hosted on Google Workspace (confirmed by MX records and the mx.google.com ESMTP banner) and has a solid baseline: SPF, DMARC p=quarantine with reporting, and working DKIM are all in place and mail is receiving correctly. The main remaining weaknesses are the permissive ~all SPF that allows spoofers to pass soft-fail checks (and risks exceeding the 10-lookup limit given 8 includes), plus the absence of MTA-STS/TLS-RPT; moving DMARC to p=reject would complete the hardening.

Mail configuration

  • Mail servers (MX)aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com

    5 MX records — the domain can receive mail.

  • SPFv=spf1 include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com include:mktomail.com include:amazonses.com include:sendgrid.net include:_spf.salesforce.com include:spf.mtasv.net ~all

    SPF present but uses a soft fail (~all) — consider tightening to -all once you confirm all senders.

  • DMARC policyv=DMARC1; p=quarantine; rua=mailto:df9481016e14030@rep.dmarcanalyzer.com; ruf=mailto:df9481016e14030@for.dmarcanalyzer.com; pct=100; fo=1;

    DMARC policy is p=quarantine — failing mail is sent to spam. Consider p=reject.

  • DKIMgoogle._domainkey, k1._domainkey, s1._domainkey, s2._domainkey

    DKIM signing keys found (selectors: google, k1, s1, s2).

  • MTA-STS

    No MTA-STS policy — optional, but it enforces encryption for mail delivery.

  • SMTP serverGoogle Workspace

    Primary mail server responded (Google Workspace).

Recommended improvements

  • Tighten SPF to -allHigh

    The current ~all soft fail tells receiving servers to accept mail that fails SPF, so spoofed mail still gets delivered to inboxes.

    → After confirming every legitimate sender (Marketo, Amazon SES, SendGrid, Salesforce, MTASV) passes SPF, change the record to v=spf1 include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com include:mktomail.com include:amazonses.com include:sendgrid.net include:_spf.salesforce.com include:spf.mtasv.net -all and monitor DMARC reports for false negatives.

    45%

    impact

  • Reduce SPF DNS lookup countHigh

    The record chains 8 include mechanisms whose nested includes can push vercel.com past the SPF 10-DNS-lookup limit, causing permerror and SPF neutral results.

    → Audit the include chain (e.g., check how many lookups amazonses.com, sendgrid.net, and spf.mtasv.net add) and consolidate/remove unused includes so the total stays below 10 lookups.

    40%

    impact

  • Enforce DMARC with p=rejectMedium

    p=quarantine sends aligned-but-failing mail to spam, while p=reject tells receivers to drop it outright — the strongest spoofing protection.

    → After confirming legitimate senders authenticate, change the DMARC record to v=DMARC1; p=reject; rua=mailto:df9481016e14030@rep.dmarcanalyzer.com; ruf=mailto:df9481016e14030@for.dmarcanalyzer.com; pct=100; fo=1; — optionally ramp via pct first.

    35%

    impact

  • Add an MTA-STS policyLow

    No MTA-STS policy means inbound mail can be downgraded from TLS to plaintext, exposing messages to interception in transit.

    → Publish a TXT record at _mta-sts.vercel.com: v=STSv1; id=20250101000000Z and host the matching policy at https://mta-sts.vercel.com/.well-known/mta-sts.txt with mode: enforce and mx: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com.

    15%

    impact

  • Add a TLS-RPT recordLow

    Without TLS-RPT you get no visibility into MTA-STS enforcement failures or TLS negotiation problems from remote senders.

    → Add a TXT record at _smtp._tls.vercel.com: v=TLSRPTv1; rua=mailto:df9481016e14030@rep.dmarcanalyzer.com to receive aggregate TLS failure reports.

    10%

    impact

Auto-rated from DNS & SMTP records · improvements suggested by AI

Loaded Resources (110 requests · sorted by load time)

ResourceSizeTimeStatus
Vvercel.com/api/stream/internal
55B
498ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1w6avfn27r7dl.js
25.3KB
307ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2zuzj3mqf9ch2.js
26.2KB
307ms
200
Vvercel.com/api/client-only-flags/show-platform-status-indicator
16B
305ms
200
Vvercel.com/contact/sales?_rsc=-QjoK3I80grVcLio
640B
238ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3ulr1i0u4bxll.js
46.6KB
224ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/media/eve-light.1e3bxs4
396B
222ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/28__39usj-94i.js
44.5KB
222ms
200
Vvercel.com/contact/sales?_rsc=_fDdqU0KrgjCxydC
48.4KB
219ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3grqow4dru7pn.js
47.5KB
215ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/30ns5iflrwnrx.js
81.7KB
215ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0ddm9ywq1w8m0.js
26.8KB
215ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/44gcujx1xxunq.js
30.7KB
215ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2cm8yig7mqhd4.js
31.2KB
214ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0i1u6jqeomyob.js
13.5KB
214ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/39_z7n6ro0f0b.js
45.3KB
213ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0rui598i6xskc.js
205.0KB
212ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3or9uaia_4gy8.js
67.7KB
212ms
200
Vvercel.com/api/jwt
12B
211ms
403
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3lg_l9su1n-4g.js
31.5KB
209ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1o775a5qw1qlh.js
1.7KB
208ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0x9ag6ja6wegg.js
51.2KB
208ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3t6u9lnoht2h4.js
7.7KB
207ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1k25oupflt1bt.js
21.5KB
206ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2-af6crt_62n_.js
51.0KB
205ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3xb79u9_6hv_1.js
25.8KB
204ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1rsigfr4ugntp.js
22.3KB
204ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3xifkfax_sa92.js
9.7KB
203ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/393_nla9x9_l7.js
155.8KB
203ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3py30t0m-prjy.js
18.5KB
202ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2z7cdhq-iz64i.js
38.6KB
202ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/007j3vc3pxs3k.js
25.8KB
201ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3jdgs-4g923me.js
9.8KB
201ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1phvwjh-5m-km.js
18.7KB
200ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3dtok9_dxff-n.js
13.7KB
199ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0rkr6ds9q7xsd.js
30.3KB
198ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0ueovtf1qiq13.js
25.6KB
198ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0_hmwg6l1ef9y.js
30.6KB
197ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/29cduq3dbs0j-.js
202.8KB
196ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/turbopack-2dtan9
13.0KB
195ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1z8ji7ga_5or7.js
31.8KB
193ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/31f6a7ktnvt0y.js
14.0KB
191ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2p3dkqquyh13l.js
11.7KB
190ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2yph0bc5flowg.js
128.7KB
183ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/media/eve-dark.2l_s1mlv
396B
182ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1baz_5ekkbe1f.js
38.3KB
181ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0uduo-qwpju_q.js
34.0KB
180ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1zzaql67p9shu.js
31.3KB
177ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3i0x7-tjzq4b9.js
13.7KB
176ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/media/vercel-dark.1f3cg
223B
164ms
200
Llishhsx6kmthaacj.public.blob.vercel-storage.com/zapier-desktop-light.webp
—
143ms
200
Llishhsx6kmthaacj.public.blob.vercel-storage.com/notion-desktop-light.webp
—
139ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/41lbhof5ccpyu.cs
782.4KB
133ms
200
Vvercel.com/e62b3a9e28ed8bca/script.js
4.4KB
133ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3qq_0m3pojp1j.js
35.1KB
131ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/media/vercel-light.3_gx
223B
128ms
200
Vvercel.com/.well-known/vercel/microfrontends/client-config
9.0KB
91ms
200
Vvercel.com/pricing?_rsc=6W5OtAywJPw1UciO
298.3KB
83ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/05p_uqdk1a_t7.js
36.1KB
82ms
200
Vvercel.com/enterprise?_rsc=-XuESpiHRnm5AqJc
122.6KB
67ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/image?url=%2Fvc-ap-vercel-marketing%2F_n
4.8KB
62ms
200
Vvercel.com/enterprise?_rsc=-QjoK3I80grVcLio
1.8KB
62ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/image?url=%2Fvc-ap-vercel-marketing%2F_n
4.5KB
61ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3q0vnyt1kp9o4.js
22.7KB
60ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2e7zh15uiyprq.js
50.1KB
59ms
200
Vvercel.com/.well-known/vercel/microfrontends/client-config
9.0KB
56ms
200
Vvercel.com/enterprise?_rsc=J70azmldkH22Q2ML
322.8KB
56ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/41_b-7ndp-1sn.js
315.3KB
50ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/06gk0jgbtwe4o.js
280.3KB
49ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/media/Geist_Variable-s.
68.1KB
46ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/media/GeistPixel_Grid.p
27.9KB
45ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/4416df5k5txri.cs
174B
44ms
200
Vvercel.com/pricing?_rsc=-QjoK3I80grVcLio
1.9KB
44ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/media/797e433ab948586e.
22.6KB
43ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2sxbj2wfyw7f1.js
7.8KB
43ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3zsqyryt031dj.js
5.1KB
43ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1pjz80h48pibn.js
148.9KB
43ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3zuc_h9dsor1y.cs
113.4KB
42ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/media/GeistPixel_Square
28.0KB
41ms
200
Vvercel.com/home?_rsc=-QjoK3I80grVcLio
1.9KB
41ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/115lear8-ypx6.js
60.3KB
40ms
200
Vvercel.com/3628f7ea4ecd82e3/script.js
12.3KB
39ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/media/GeistPixel_Line.p
17.7KB
38ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3u82rwmj_1n8p.cs
7.2KB
37ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0xeft96e1_yan.js
82.8KB
34ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3ej93d4kcx5ng.js
71.1KB
33ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3cs4tua0r544c.js
23.4KB
32ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0q5ceae4h1nmo.js
213.7KB
32ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2lyxlrg4-so7x.js
17.5KB
32ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1vw6xmduip-y4.js
113.1KB
32ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1s9214m_oxc3_.js
33.2KB
31ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0zt6d9px1bv38.js
63.9KB
30ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/181b0w64co174.js
45.6KB
26ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3_1lmf91nafgz.js
19.8KB
25ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2xk4u_28w_thu.js
34.1KB
25ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/media/GeistPixel_Triang
28.2KB
24ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1utu2mgec40e4.js
144.3KB
24ms
200
Oo205439.ingest.us.sentry.io/api/4507726617772032/envelope/?sentry_key=285c776421
—
24ms
429
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1xk-u8x59tc58.js
55.9KB
24ms
200
Vvercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0iuq5lu_r6_le.js
7.4KB
24ms
200
Showing 100 of 110 resources

Scan History (2 scans)

Page load time

694ms

TTFB

127ms
DateTTFBDOMLoadRequestsSizeErrorsScripts
Oct 7, 02:06 PM UTC127ms657ms694ms1105746KB337AI
Sep 30, 01:58 PM UTC83ms367ms440ms1115959KB10AI

Embed a badge

Pick what to show — your detected tech stack, the social-trend valuation, or both.

Badge style

Brand · detected technologies.

Preview
badge preview
HTML embed
<a href="https://madewith.tech/s/vercel.com"><img src="https://madewith.tech/s/vercel.com/badge.svg" alt="vercel.com on MadeWithTech" /></a>
Markdown
[![vercel.com on MadeWithTech](https://madewith.tech/s/vercel.com/badge.svg)](https://madewith.tech/s/vercel.com)
Share link
https://madewith.tech/s/vercel.com
vercel.com is built with Css3, Experiment Framework, Geist Font · MadeWithTech