Website review, no card needed
kustomer.com website review
Visit site (opens in a new tab)Reviewed 29 October 202621 issues · 75 checks
This review found 21 issues worth fixing on kustomer.com, 4 of them high impact, across 75 checks. The most urgent: 4 text elements with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
88B- #4,332 of 89,925 reviewed websitesbeats 93%
- #2,233 of 47,117 online storesbeats 93%
- #2,160 of 42,347 Shopify storesbeats 92%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.6 s |
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 280 ms |
| May 16, 2026 | 288 ms |
| May 23, 2026 | 288 ms |
| May 30, 2026 | 308 ms |
| Jun 6, 2026 | 322 ms |
| Jun 13, 2026 | 314 ms |
| Jun 20, 2026 | 309 ms |
| Jun 27, 2026 | 289 ms |
| Jul 4, 2026 | 270 ms |
| Jul 11, 2026 | 254 ms |
| Jul 18, 2026 | 242 ms |
| Jul 25, 2026 | 238 ms |
| Aug 1, 2026 | 233 ms |
| Aug 8, 2026 | 244 ms |
| Aug 15, 2026 | 251 ms |
| Aug 22, 2026 | 256 ms |
| Aug 29, 2026 | 257 ms |
| Sep 5, 2026 | 262 ms |
| Sep 12, 2026 | 284 ms |
| Sep 19, 2026 | 281 ms |
| Sep 26, 2026 | 252 ms |
| Oct 3, 2026 | 216 ms |
| Oct 10, 2026 | 196 ms |
| Oct 17, 2026 | 200 ms |
| Oct 24, 2026 | 227 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
0.4 s
0.9 s
1.3 s
1.7 s
2.1 s
2.6 s
3.0 s
3.4 s
Speed
Reduce unused JavaScript
990 ms · 284 KiBAbout 284 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 990 ms faster on a phone.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
550 ms · 208 KiB9 images could be 208 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.
Render-blocking requests
550 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Legacy JavaScript
400 ms · 14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
Google Tag Manager adds 283 ms
283 msGoogle Tag Manager costs a phone 283 ms of main-thread work and 376 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.
2,495 HTML elements
The page has 2,495 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Adobe TypeKit adds 0 ms
0 msAdobe TypeKit costs a phone 0 ms of main-thread work and 317 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.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Crazy Egg and cdn-cookieyes.com and others), adding 986 KiB and 412 ms of main-thread time.
Use efficient cache lifetimes
200 ms · 6 KiB4 files are served with short cache lifetimes, so returning visitors download them again (6 KiB).
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 164 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 709 ms of it running JavaScript. That is comfortably low.
Server response: 23 ms
23 msYour server sent the HTML in 23 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.5 s
11.5 sYour largest element takes 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our 8 partners use cookies and other tracking techno…”.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Time to Interactive: 11.6 s
11.6 sThe page becomes fully interactive after 11.6 s. Good is under 3.8 s.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 259 ms
259 msScripts block taps and scrolling for 259 ms in total while the page loads. Good is under 200 ms.
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 194 ms
194 msReal visitors wait 194 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 659 ms
659 msReal visitors wait 659 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 280 ms to 227 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 37% faster for real visitors
-37%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.6 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.5 g of CO₂ per visit
0.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.47 g of CO₂e: 56.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.6 MB in 86 requests
1.6 MBYour homepage downloads 1.6 MB in 86 requests on a phone: scripts 748 KiB (22), images 385 KiB (29) and fonts 314 KiB (10). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 95 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
92 internal links, 11 external
The homepage links to 92 pages on kustomer.com and 11 external pages.
8 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Deliver faster, personalized support with Kustomer's AI customer service CRM. Unify conversations, automate workflows, …”.
One H1 headline
Your main headline reads: “Yourintelligent CX”.
Title: 45 characters
Your title is a healthy 45 characters: “AI Customer Service Platform & CRM | Kustomer”.
Canonical URL set
The canonical URL is https://www.kustomer.com/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.kustomer.com/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (995 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (5 KiB, 36 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
/see-it-live is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without an H1
/see-it-live has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 61 found) and read each the way a search engine does.
5 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 a title
All 15 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://use.typekit.net/prm3jmb.css' violates the following Content Security Policy directive: "connect-…”.
1 checks passed
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 757 words of copy
The homepage carries about 757 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: “Schedule demo”.
19 calls to action
The homepage has 19 calls to action, for example “Pricing”, “Schedule Demo” and “Schedule demo”.
Social proof on the page
Social proof on the homepage: 70 testimonial or review blocks, 21 customer or partner logos, 13 trust badges and “500+ reviews”.
Analytics in place
Analytics detected: Google Tag Manager and HubSpot.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) 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 kustomer.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
- Next.js
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Vercel
Company
- Employees
- 250
- Headquarters
- Millburn
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 21 issues on kustomer.com, including 13 speed issues, 1 SEO issue 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.