Website review, no card needed
sanden.com website review
Visit site (opens in a new tab)Reviewed 4 November 202633 issues · 78 checks
This review found 33 issues worth fixing on sanden.com, 8 of them high impact, across 78 checks. The most urgent: fails Core Web Vitals for real visitors. 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 4.0 s |
| Aug 29, 2026 | 4.0 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.7 s |
| Oct 24, 2026 | 3.8 s |
| Oct 31, 2026 | 3.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 79 ms |
| May 23, 2026 | 85 ms |
| May 30, 2026 | 84 ms |
| Jun 6, 2026 | 83 ms |
| Jun 13, 2026 | 83 ms |
| Jun 20, 2026 | 79 ms |
| Jun 27, 2026 | 79 ms |
| Jul 4, 2026 | 79 ms |
| Jul 11, 2026 | 78 ms |
| Jul 18, 2026 | 79 ms |
| Jul 25, 2026 | 78 ms |
| Aug 1, 2026 | 79 ms |
| Aug 8, 2026 | 79 ms |
| Aug 15, 2026 | 77 ms |
| Aug 22, 2026 | 79 ms |
| Aug 29, 2026 | 78 ms |
| Sep 5, 2026 | 78 ms |
| Sep 12, 2026 | 80 ms |
| Sep 19, 2026 | 87 ms |
| Sep 26, 2026 | 94 ms |
| Oct 3, 2026 | 92 ms |
| Oct 10, 2026 | 94 ms |
| Oct 17, 2026 | 79 ms |
| Oct 24, 2026 | 78 ms |
| Oct 31, 2026 | 78 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
Speed
Mobile performance score: 89
89/100Your mobile performance score is 89. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
950 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Improve image delivery
700 ms · 149 KiB5 images could be 149 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
Use efficient cache lifetimes
550 ms · 85 KiB18 files are served with short cache lifetimes, so returning visitors download them again (85 KiB).
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 108 ms. During a long task the page ignores taps.
2 third-party services on the page
2 third-party services load with your homepage (FoxyCart and Google Fonts), adding 200 KiB and 75 ms of main-thread time.
Reduce unused CSS
74 KiBAbout 74 KiB of CSS is downloaded but never applied on this page.
Reduce unused JavaScript
35 KiBAbout 35 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
Minify CSS
9 KiB9 KiB could be saved by minifying CSS.
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: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 236 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 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.
Real-user LCP: 4.4 s
4.4 sReal visitors wait 4.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.3 s
4.3 sReal visitors see the first content after 4.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.0 s
3.0 sReal visitors wait 3.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 43% slower for real visitors
+43%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.7 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 3.2 s
3.2 sYour largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We are the creative, innovative leaders in technology, deli…”. Most of its time is element render delay (2.8 s).
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 79 ms to 78 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 68 ms
68 msReal visitors wait 68 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Time to Interactive: 3.8 s
3.8 sThe page is fully interactive after 3.8 s.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 46 ms
46 msScripts block the page for only 46 ms while loading. Good is under 200 ms.
Images and page weight
1 image far larger than shown
44 KiB1 image is downloaded at several times the size a phone draws it, for example futurecar-9x6-1-768x512.jpg at 390 px wide, shown at 68 px. Resized copies would save about 44 KiB.
About 0.1 g of CO₂ per visit
0.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.14 g of CO₂e: 16.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 499 KiB in 25 requests
499 KiBYour homepage downloads 499 KiB in 25 requests on a phone: images 207 KiB (9), scripts 142 KiB (8) and stylesheets 92 KiB (6). 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.
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.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 11 images in the HTML carry an alt attribute.
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (17 characters)
Your title is only 17 characters: “Home - Sanden USA”. Between 30 and 65 characters leaves room to say what you do and for whom.
Canonical points to another host
Your canonical URL points to dev.sanden.com, not sanden.com, so Google may credit that host instead.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
Only 4 internal links
The homepage links to only 4 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
4 checks passed
One H1 headline
Your main headline reads: “The Leader inAutomotive Air Conditioning”.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
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://sanden.com/sitemap_index.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://sanden.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 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.
Other pages
3 pages without a meta description
https://sanden.com/productsearch, https://sanden.com/security and https://sanden.com/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://sanden.com/security and https://sanden.com/privacy-policy have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://sanden.com/productsearch has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
3 internal pages checked
We fetched 3 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 3 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 3 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
5 of 5 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 69 words
The homepage has only about 69 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 sanden.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Hosting
- H5colo
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on sanden.com, including 12 speed issues, 6 SEO issues and 6 conversion gaps. 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.