Website review, no card needed
jet-hot.com website review
Visit site (opens in a new tab)Reviewed 7 November 202633 issues · 83 checks
This review found 33 issues worth fixing on jet-hot.com, 12 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
81B- #38,518 of 113,395 reviewed websitesbeats 60%
- #26,040 of 65,366 online storesbeats 54%
- #101 of 1,337 Squarespace websitesbeats 91%
Closest competitors among online stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 97 ms |
| May 23, 2026 | 89 ms |
| May 30, 2026 | 88 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 87 ms |
| Jun 27, 2026 | 85 ms |
| Jul 4, 2026 | 82 ms |
| Jul 11, 2026 | 79 ms |
| Jul 18, 2026 | 79 ms |
| Jul 25, 2026 | 87 ms |
| Aug 1, 2026 | 89 ms |
| Aug 8, 2026 | 87 ms |
| Aug 15, 2026 | 93 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 97 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 98 ms |
| Sep 19, 2026 | 93 ms |
| Sep 26, 2026 | 88 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 96 ms |
| Oct 17, 2026 | 94 ms |
| Oct 24, 2026 | 92 ms |
| Oct 31, 2026 | 89 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.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
7.3 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.3 s faster on a phone.
Improve image delivery
2.5 s · 730 KiB9 images could be 730 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.
Use efficient cache lifetimes
1.6 s · 219 KiB9 files are served with short cache lifetimes, so returning visitors download them again (219 KiB).
Render-blocking requests
1.6 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 41
41/100Your mobile performance score is 41. 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 (Squarespace, Google Tag Manager and Facebook and others), adding 2.9 MB and 1.3 s of main-thread time.
Reduce unused CSS
910 ms · 134 KiBAbout 134 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 910 ms faster on a phone.
Legacy JavaScript
600 ms · 137 KiBPolyfills for old browsers add 137 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 600 ms faster on a phone.
Squarespace adds 564 ms
564 msSquarespace costs a phone 564 ms of main-thread work and 1.3 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.
Google Tag Manager adds 509 ms
509 msGoogle Tag Manager costs a phone 509 ms of main-thread work and 973 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: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
sqspcdn.com adds 63 ms
63 mssqspcdn.com costs a phone 63 ms of main-thread work and 392 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 244 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.
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: 50 ms
50 msYour server sent the HTML in 50 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 23.5 s
23.5 sYour largest element takes 23.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 23.6 s
23.6 sThe page becomes fully interactive after 23.6 s. Good is under 3.8 s.
First Contentful Paint: 6.3 s
6.3 sThe first text or image appears after 6.3 s on a phone. Good is under 1.8 s.
Speed Index: 10.4 s
10.4 sVisually, the page fills in at 10.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 609 ms
609 msScripts block taps and scrolling for 609 ms in total while the page loads. Good is under 200 ms.
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
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 97 ms to 89 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.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 87 ms
87 msReal visitors wait 87 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.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 642 ms
642 msReal visitors wait 642 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.9 MB in 127 requests
3.9 MBYour homepage downloads 3.9 MB in 127 requests on a phone: scripts 2.6 MB (70), images 938 KiB (26) and stylesheets 176 KiB (16). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
120 KiB1 image is downloaded at several times the size a phone draws it, for example JetHot_Fire_04.jpg at 1,620 px wide, shown at 343 px. Resized copies would save about 120 KiB.
2 images below the first screen load straight away
2 images further down the page (243 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.12 g of CO₂e: 134.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
25 text elements with low contrast
25 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious 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.
Headings skip levels
Headings skip levels (h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 29 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“Keeping you cool for 40+ years!”, “HOW TO GET Our Coatings” and “WE BELIEVE craft MATTERs.So do the people behind …”). One clear main headline is easier for people and search engines.
Meta description is long (192 characters)
Your meta description is 192 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5915def0d1758ec88ab…”.
91 internal links, 20 external
The homepage links to 91 pages on jet-hot.com and 20 external pages.
5 checks passed
Title: 42 characters
Your title is a healthy 42 characters: “Ceramic Header & Exhaust Coating | Jet-Hot”.
Canonical URL set
The canonical URL is https://www.jet-hot.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.jet-hot.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing name, url, logo and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.jet-hot.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 (629 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://www.jet-hot.com/coatingsoverview and https://www.jet-hot.com/dealers have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://www.jet-hot.com/american-muscle and https://www.jet-hot.com/annual-car-and-bike-show use the same meta description. A description written for each page earns more clicks.
10 pages without an H1
https://www.jet-hot.com/hot-rods-classics, https://www.jet-hot.com/off-road, https://www.jet-hot.com/american-muscle, https://www.jet-hot.com/motorcycle, https://www.jet-hot.com/marine-1 and https://www.jet-hot.com/competitiongalleries and 4 others have 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 29 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.
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 15 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 “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/5915def0d1758ec88ab41ee2/205/5c5…”.
2 checks passed
Tap targets are thumb-sized
9 of 10 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: “Over 50,000 satisfied customers”. Pairing it with named testimonials or customer logos makes it far more convincing.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 458 words of copy
The homepage carries about 458 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CALL” and “GET MY COATING”.
17 calls to action
The homepage has 17 calls to action, for example “Get My Coating”, “Contact Us” and “Get a Quick Quote”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
8 cookies set on arrival
8Opening the homepage sets 8 cookies (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.
20 other companies contacted
Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 jet-hot.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
- Squarespace
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Squarespace
Company
- Headquarters
- Burlington
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 jet-hot.com, including 18 speed issues, 3 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.