Website review, no card needed
klaviyo.com website review
Visit site (opens in a new tab)Reviewed 17 November 202640 issues · 86 checks
This review found 40 issues worth fixing on klaviyo.com, 17 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for Klaviyo
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
69D- #103,332 of 120,366 reviewed websitesbeats 12%
- #62,539 of 68,142 online storesbeats 7%
- #57,782 of 62,097 Shopify storesbeats 6%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.3 s |
| Nov 7, 2026 | 2.3 s |
| Nov 14, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 350 ms |
| Jun 6, 2026 | 352 ms |
| Jun 13, 2026 | 360 ms |
| Jun 20, 2026 | 351 ms |
| Jun 27, 2026 | 348 ms |
| Jul 4, 2026 | 338 ms |
| Jul 11, 2026 | 330 ms |
| Jul 18, 2026 | 338 ms |
| Jul 25, 2026 | 345 ms |
| Aug 1, 2026 | 348 ms |
| Aug 8, 2026 | 343 ms |
| Aug 15, 2026 | 322 ms |
| Aug 22, 2026 | 307 ms |
| Aug 29, 2026 | 295 ms |
| Sep 5, 2026 | 280 ms |
| Sep 12, 2026 | 282 ms |
| Sep 19, 2026 | 278 ms |
| Sep 26, 2026 | 270 ms |
| Oct 3, 2026 | 266 ms |
| Oct 10, 2026 | 261 ms |
| Oct 17, 2026 | 253 ms |
| Oct 24, 2026 | 249 ms |
| Oct 31, 2026 | 246 ms |
| Nov 7, 2026 | 231 ms |
| Nov 14, 2026 | 206 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.3 s
2.7 s
4.0 s
5.4 s
6.7 s
8.1 s
9.4 s
10.7 s
Speed
Reduce unused JavaScript
5.5 s · 2.2 MBAbout 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.5 s faster on a phone.
Use efficient cache lifetimes
2.6 s · 1.2 MB45 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).
Render-blocking requests
2.4 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Main-thread work: 16.6 s
A phone's processor spends 16.6 s on main-thread work while loading, 8.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
1.1 s · 182 KiBAbout 182 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 s of main-thread work and 1.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 28
28/100Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,115 HTML elements
The page has 3,115 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and transcend-cdn.com and others), adding 5.4 MB and 2.9 s of main-thread time.
Improve image delivery
600 ms · 422 KiB12 images could be 422 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Facebook adds 449 ms
449 msFacebook costs a phone 449 ms of main-thread work and 331 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Google CDN adds 351 ms
351 msGoogle CDN costs a phone 351 ms of main-thread work and 742 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Vimeo adds 152 ms
152 msVimeo costs a phone 152 ms of main-thread work and 2.4 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
transcend-cdn.com adds 353 ms
353 mstranscend-cdn.com costs a phone 353 ms of main-thread work and 139 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 326 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 159 KiBPolyfills for old browsers add 159 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 19.7 s
19.7 sYour largest element takes 19.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 46.1 s
46.1 sThe page becomes fully interactive after 46.1 s. Good is under 3.8 s.
Speed Index: 14.2 s
14.2 sVisually, the page fills in at 14.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 3.3 s
3.3 sScripts block taps and scrolling for 3.3 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 4.2 s
4.2 sThe first text or image appears after 4.2 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 278 ms
278 msReal visitors wait 278 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Tap response (INP) got 38% faster for real visitors
-38%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 350 ms to 206 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 34% faster for real visitors
-34%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.3 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.037
0.037The layout barely moves while loading (CLS 0.037, good is under 0.1).
Images and page weight
Page weight: 9.3 MB in 480 requests
9.3 MBYour homepage downloads 9.3 MB in 480 requests on a phone: scripts 5.3 MB (199), other files 2.8 MB (164) and images 698 KiB (87). Under 2 MB keeps phones on slow connections fast.
3 images below the first screen load straight away
3 images further down the page (331 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.6 g of CO₂ per visit
2.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.64 g of CO₂e: 316.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
129 links without text
129 visible links have no text or label, so screen readers cannot say where they go.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 193 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (201 characters)
Your meta description is 201 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (FAQPage, ItemList, Organization and WebPage) but with 1 problem, for example “ItemList: itemListElement is an empty list”.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
349 internal links, 90 external
The homepage links to 349 pages on klaviyo.com and 90 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Your AI marketing agent, always a step ahead”.
Title: 43 characters
Your title is a healthy 43 characters: “Klaviyo: AI Email Marketing & SMS | B2C CRM”.
Canonical URL set
The canonical URL is https://www.klaviyo.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.klaviyo.com/sitemap_index.xml.
AI search readiness
Parts of the site are closed to 6 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
3 checks passed
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,187 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.klaviyo.com/llms.txt (21 KiB, 101 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 127 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=73007428&Ver=2&mid=93ff99e6-2897-4afa-8e5e-9f9ededf9848&bo=2&sid=34c1c8a0e26211f1997cd7873d4178d1&vid=34c1f340e26211f19ed8e920c711e5e1&vids=1&msclkid=N&pi=918639831&lg.
4 third-party cookies
4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot assign to read only property 'open' of object '#<Window>'”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
33 of 35 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 729 words of copy
The homepage carries about 729 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Sign up” and “Sign up with Google”.
14 calls to action
The homepage has 14 calls to action, for example “Pricing”, “Sign up” and “Get a demo”.
Social proof on the page
Social proof on the homepage: 108 customer or partner logos and 6 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, HubSpot and Amplitude.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Tag Manager, HubSpot and Microsoft Ads (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.
30 cookies set on arrival
30Opening the homepage sets 30 cookies, 8 of them by other companies (measured from a US location before any click).
35 other companies contacted
Loading the homepage contacts 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Ketch
A consent management tool (Ketch) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at klaviyo.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Astro
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Amplitude
- Hosting
- Cloudflare
Hiring
- Hiring
- 141 open roles
- Teams
- Sales (45), Engineering (29), IT & Security (18), Marketing (15)
- Job board
- greenhouse
- Careers page
- www.klaviyo.com/careers (opens in a new tab)
Company
- Employees
- 1,803
- Founded
- 2012
- Headquarters
- Massachusetts
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on klaviyo.com, including 26 speed issues, 2 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.