Website review, no card needed
cadetheat.com website review
Visit site (opens in a new tab)Reviewed 5 November 202640 issues · 88 checks
This review found 40 issues worth fixing on cadetheat.com, 12 of them high impact, across 88 checks. The most urgent: render-blocking requests. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 71 ms |
| May 23, 2026 | 73 ms |
| May 30, 2026 | 72 ms |
| Jun 6, 2026 | 80 ms |
| Jun 13, 2026 | 85 ms |
| Jun 20, 2026 | 83 ms |
| Jun 27, 2026 | 83 ms |
| Jul 4, 2026 | 83 ms |
| Jul 11, 2026 | 79 ms |
| Jul 18, 2026 | 79 ms |
| Jul 25, 2026 | 79 ms |
| Aug 1, 2026 | 80 ms |
| Aug 8, 2026 | 81 ms |
| Aug 15, 2026 | 81 ms |
| Aug 22, 2026 | 86 ms |
| Aug 29, 2026 | 79 ms |
| Sep 5, 2026 | 80 ms |
| Sep 12, 2026 | 84 ms |
| Sep 19, 2026 | 79 ms |
| Sep 26, 2026 | 82 ms |
| Oct 3, 2026 | 81 ms |
| Oct 10, 2026 | 79 ms |
| Oct 17, 2026 | 79 ms |
| Oct 24, 2026 | 77 ms |
| Oct 31, 2026 | 73 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.0 s
1.9 s
2.9 s
3.8 s
4.8 s
5.8 s
6.7 s
7.7 s
Speed
Render-blocking requests
2.1 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
YouTube adds 1.7 s
1.7 sYouTube costs a phone 1.7 s of main-thread work and 987 KiB 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.
Main-thread work: 10.6 s
A phone's processor spends 10.6 s on main-thread work while loading, 6.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google CDN and Google Tag Manager and others), adding 2.9 MB and 3.5 s of main-thread time.
Reduce unused JavaScript
1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
250 ms · 812 KiB25 files are served with short cache lifetimes, so returning visitors download them again (812 KiB).
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 729 ms. During a long task the page ignores taps.
Reduce unused CSS
450 ms · 241 KiBAbout 241 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google CDN adds 594 ms
594 msGoogle CDN costs a phone 594 ms of main-thread work and 736 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 Tag Manager adds 463 ms
463 msGoogle Tag Manager costs a phone 463 ms of main-thread work and 290 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.
Font display
450 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).
gd-commerce-services.net adds 311 ms
311 msgd-commerce-services.net costs a phone 311 ms of main-thread work and 664 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.
Improve image delivery
60 KiB2 images could be 60 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need.
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: 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.
Time to Interactive: 25.2 s
25.2 sThe page becomes fully interactive after 25.2 s. Good is under 3.8 s.
Total Blocking Time: 3.7 s
3.7 sScripts block taps and scrolling for 3.7 s in total while the page loads. Good is under 200 ms.
Speed Index: 13.3 s
13.3 sVisually, the page fills in at 13.3 s (Speed Index). Good is under 3.4 s.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.7 s
3.7 sYour largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “cadet”.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 71 ms to 73 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 73 ms
73 msReal visitors wait 73 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.047
0.047The layout barely moves while loading (CLS 0.047, good is under 0.1).
Images and page weight
Page weight: 4.2 MB in 76 requests
4.2 MBYour homepage downloads 4.2 MB in 76 requests on a phone: scripts 2.8 MB (25), other files 478 KiB (27) and fonts 336 KiB (6). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.18 g of CO₂e: 141.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
82 internal links, 16 external
The homepage links to 82 pages on cadetheat.com and 16 external pages.
6 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Cadet Heat has provided electric heaters and heating solutions for over 40 years. We are your trusted partner for creat…”.
One H1 headline
Your main headline reads: “Effortless Control Starts Here”.
Title: 39 characters
Your title is a healthy 39 characters: “Electric Heating Solutions | Cadet Heat”.
Canonical URL set
The canonical URL is https://www.cadetheat.com/en-us.
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.cadetheat.com/sitemap.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://www.cadetheat.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (377 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.cadetheat.com/en-us and / all use the title “Electric Heating Solutions | Cadet Heat”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://www.cadetheat.com/en-us/electric-heating-solutions/fan-forced-heaters, https://www.cadetheat.com/en-us/electric-heating-solutions/baseboard-heaters, https://www.cadetheat.com/en-us/electric-heating-solutions/garage-and-workshop-heaters, https://www.cadetheat.com/en-us/electric-heating-solutions/thermostats, https://www.cadetheat.com/en-us/electric-heating-solutions/heater-accessories and https://www.cadetheat.com/en-us/articles and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.cadetheat.com/en-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.
4 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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 14 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Framing 'https://www.google.com/' violates the following report-only Content Security Policy directive: "frame-ancestor…”.
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
22 of 25 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 255 words of copy
The homepage carries about 255 words of visible text.
3 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Register your product”, “Subscribe to the newsletter” and “Contact Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
6 cookies set on arrival
6Opening the homepage sets 6 cookies, 1 of them by other companies (measured from a US location before any click).
24 other companies contacted
Loading the homepage contacts 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 cadetheat.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
- Drupal
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- AWS
Company
- Headquarters
- Cambridge
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 cadetheat.com, including 21 speed issues, 3 SEO issues and 3 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.