Website review, no card needed

calmingheat.com logo

calmingheat.com website review

Visit site (opens in a new tab)Reviewed 9 November 202633 issues · 74 checks

This review found 33 issues worth fixing on calmingheat.com, 11 of them high impact, across 74 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of calmingheat.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. calmingheat.com at 0.4 s0.4 s
  2. calmingheat.com at 0.8 s0.8 s
  3. calmingheat.com at 1.1 s1.1 s
  4. calmingheat.com at 1.5 s1.5 s
  5. calmingheat.com at 1.9 s1.9 s
  6. calmingheat.com at 2.3 s2.3 s
  7. calmingheat.com at 2.6 s2.6 s
  8. calmingheat.com at 3.0 s3.0 s

Speed

8 to fix32
  • Reduce unused JavaScript

    4.3 s · 848 KiB

    About 848 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.

  • Mobile performance score: 32

    32/100

    Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Hotjar and Accessibe Accessibility Overlay and others), adding 1.8 MB and 1.1 s of main-thread time.

  • Render-blocking requests

    950 ms

    9 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

  • Use efficient cache lifetimes

    500 ms · 240 KiB

    25 files are served with short cache lifetimes, so returning visitors download them again (240 KiB).

  • Google Tag Manager adds 358 ms

    358 ms

    Google Tag Manager costs a phone 358 ms of main-thread work and 690 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.

  • Main-thread work: 3.6 s

    A phone's processor spends 3.6 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Accessibe Accessibility Overlay adds 204 ms

    204 ms

    Accessibe Accessibility Overlay costs a phone 204 ms of main-thread work and 499 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.

  • Reduce unused CSS

    280 ms · 42 KiB

    About 42 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.

  • 12 long tasks on the main thread

    12 long tasks block the main thread while loading, the longest for 243 ms. During a long task the page ignores taps.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    39 KiB

    Polyfills for old browsers add 39 KiB JavaScript that modern phones do not need.

  • Improve image delivery

    9 KiB

    2 images could be 9 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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.

1 checks passed
  • Server response: 9 ms

    9 ms

    Your server sent the HTML in 9 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix29
  • Largest Contentful Paint: 17.8 s

    17.8 s

    Your largest element takes 17.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 23.7 s

    23.7 s

    The page becomes fully interactive after 23.7 s. Good is under 3.8 s.

  • Speed Index: 8.9 s

    8.9 s

    Visually, the page fills in at 8.9 s (Speed Index). Good is under 3.4 s.

  • Cumulative Layout Shift: 0.28

    0.28

    The layout shifts by 0.28 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 677 ms

    677 ms

    Scripts block taps and scrolling for 677 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.4 s

    2.4 s

    The first text or image appears after 2.4 s on a phone. Good is under 1.8 s.

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Images and page weight

1 to fix85
  • Page weight: 3.6 MB in 358 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 358 requests on a phone: scripts 2.2 MB (116), other files 1.0 MB (197) and images 217 KiB (32). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    1.01 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.01 g of CO₂e: 120.8 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

3 to fixGoogle 9696
  • 8 text elements with low contrast

    8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10074
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (12 characters)

    Your title is only 12 characters: “Calming Heat”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (252 characters)

    Your meta description is 252 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 54 internal links, 3 external

    The homepage links to 54 pages on calmingheat.com and 3 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.calmingheat.com/.

  • 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.calmingheat.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

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.

  • llms.txt published

    The site publishes https://www.calmingheat.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix69
  • 3 linked pages are broken

    Your homepage links to https://www.calmingheat.com/products/calming-heat-tm-deluxe, https://www.calmingheat.com/products/calming-heat-massaging-neck-wrap-power-pack-9-settings and https://www.calmingheat.com/products/calming-heat, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 5 pages share a meta description

    https://www.calmingheat.com/products/calming-heat-tm-1, https://www.calmingheat.com/products/calming-heat-knee-wrap and https://www.calmingheat.com/products/calming-heat-back-wrap-1 use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.calmingheat.com/products/calming-heat-tm-1 has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.calmingheat.com/products/calming-heat-tm-1 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 12 pages that loaded have a meta description.

  • 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 12 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 8 small tap targets

    8 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • 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.

  • Only about 129 words

    The homepage has only about 129 words of visible text; thin pages give Google and first-time buyers little to go on.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “shop new sauna wrap”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop Now” and “Start Shopping”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity, Hotjar and Matomo.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 4 mores (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.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 2 of them by other companies (measured from a US location before any click).

  • 46 other companies contacted

    Loading the homepage contacts 46 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 calmingheat.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Social Widget · stamped.io · pepperjam.com · adroll.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Tag Manager | Hotjar | Matomo | Microsoft Clarity
Hosting
Shopify

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 calmingheat.com, including 15 speed issues, 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25