Website review, no card needed
biomat.com website review
Visit site (opens in a new tab)Reviewed 5 November 202638 issues · 89 checks
This review found 38 issues worth fixing on biomat.com, 14 of them high impact, across 89 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
82B- #33,225 of 117,972 reviewed websitesbeats 66%
- #22,186 of 67,058 online storesbeats 60%
- #21,450 of 61,142 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 139 ms |
| May 23, 2026 | 136 ms |
| May 30, 2026 | 131 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 161 ms |
| Jun 20, 2026 | 163 ms |
| Jun 27, 2026 | 171 ms |
| Jul 4, 2026 | 171 ms |
| Jul 11, 2026 | 170 ms |
| Jul 18, 2026 | 170 ms |
| Jul 25, 2026 | 163 ms |
| Aug 1, 2026 | 152 ms |
| Aug 8, 2026 | 145 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 143 ms |
| Aug 29, 2026 | 138 ms |
| Sep 5, 2026 | 145 ms |
| Sep 12, 2026 | 145 ms |
| Sep 19, 2026 | 146 ms |
| Sep 26, 2026 | 150 ms |
| Oct 3, 2026 | 146 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 138 ms |
| Oct 24, 2026 | 145 ms |
| Oct 31, 2026 | 138 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
Reduce unused JavaScript
3.6 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
Mobile performance score: 38
38/100Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.1 s
A phone's processor spends 7.1 s on main-thread work while loading, 3.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
300 ms · 3.3 MB16 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, PayPal and Klaviyo and others), adding 2.6 MB and 1.9 s of main-thread time.
Use efficient cache lifetimes
900 ms · 225 KiB21 files are served with short cache lifetimes, so returning visitors download them again (225 KiB).
Render-blocking requests
750 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Google Tag Manager adds 630 ms
630 msGoogle Tag Manager costs a phone 630 ms of main-thread work and 828 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.
PayPal adds 355 ms
355 msPayPal costs a phone 355 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.
Legacy JavaScript
300 ms · 36 KiBPolyfills for old browsers add 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
2,775 HTML elements
The page has 2,775 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 260 ms. During a long task the page ignores taps.
Klaviyo adds 211 ms
211 msKlaviyo costs a phone 211 ms of main-thread work and 329 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.
rebuyengine.com adds 199 ms
199 msrebuyengine.com costs a phone 199 ms of main-thread work and 300 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.
Shopify adds 88 ms
88 msShopify costs a phone 88 ms of main-thread work and 306 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
76 KiBAbout 76 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
11 KiB11 KiB could be saved by minifying JavaScript.
Minify CSS
6 KiB6 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.
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: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 32.4 s
32.4 sYour largest element takes 32.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Man resting on a BioMat while wearing headphones in a home …”.
Speed Index: 19.0 s
19.0 sVisually, the page fills in at 19.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 40.0 s
40.0 sThe page becomes fully interactive after 40.0 s. Good is under 3.8 s.
First Contentful Paint: 5.0 s
5.0 sThe first text or image appears after 5.0 s on a phone. Good is under 1.8 s.
Total Blocking Time: 739 ms
739 msScripts block taps and scrolling for 739 ms in total while the page loads. Good is under 200 ms.
101 images without width and height
101 images 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 139 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 137 ms
137 msReal visitors wait 137 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.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 782 ms
782 msReal visitors wait 782 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 29% faster for real visitors
-29%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.0 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
Page weight: 10.5 MB in 405 requests
10.5 MBYour homepage downloads 10.5 MB in 405 requests on a phone: images 6.1 MB (88), scripts 2.6 MB (127) and other files 873 KiB (149). Under 2 MB keeps phones on slow connections fast.
17 images far larger than shown
2.5 MB17 images are downloaded at several times the size a phone draws them, for example 1_4.png at 2,048 px wide, shown at 80 px. Resized copies would save about 2.5 MB.
1 image over 500 KB
Group_1597879637.png weighs 1.7 MB. On a phone connection a single image that size takes seconds.
24 images below the first screen load straight away
24 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
WhatsApp_Image_2026-08-21_at_2.12.06_AM.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 3.0 g of CO₂ per visit
2.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.97 g of CO₂e: 356.6 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
21 text elements with low contrast
21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
16 tap targets too small
16 tap targets are too small or too close together to hit reliably with a finger.
11 images without alt text
11 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h3 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 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 social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
83 internal links, 6 external
The homepage links to 83 pages on biomat.com and 6 external pages.
7 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Experience the healing power of far infrared therapy and negative ions with BioMat. Science-backed, FDA-cleared mats fo…”.
One H1 headline
Your main headline reads: “BioMat® - Backed by Science, Inspired by Nature”.
Title: 60 characters
Your title is a healthy 60 characters: “BioMat® - Backed by Science, Inspired by Nature – BioMat.com”.
Canonical URL set
The canonical URL is https://biomat.com/.
Structured data in place
Structured data found: FAQPage, Organization 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://biomat.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,808 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://biomat.com/llms.txt (4 KiB, 4 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without an H1
https://biomat.com/collections/all, https://biomat.com/pages/learn, https://biomat.com/pages/practitioner-page and https://biomat.com/collections/accessories-for-biomat-pro 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 43 found) and read each the way a search engine does.
6 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 9 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 9 pages that loaded have a <title>.
Best practices
8 small tap targets
8 of 20 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 “Failed to load resource: net::ERR_CONNECTION_RESET”.
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
About 1,208 words of copy
The homepage carries about 1,208 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: “Shop Professional” and “Shop Mini”.
19 calls to action
The homepage has 19 calls to action, for example “SHOP - go to collection all”, “Top 8 Reasons to Buy a BioMat” and “Germanium Waterproof Cover SHOP NOW”.
10 short forms
10 short forms (4 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 42 testimonial or review blocks, 2 customer or partner logos, a star rating, 3 trust badges and “500,000+ Happy Customers”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Hotjar.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
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
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 mores (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.
26 cookies set on arrival
26Opening the homepage sets 26 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.
45 other companies contacted
Loading the homepage contacts 45 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 biomat.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Pagefly Ai Page Builder · Currency Converter · Gempages Builder · Patrol · Gempages Cro · trustedsite.com · nice-team.net · nfcube.com · myjshops.com · rebuyengine.com · bogos.io
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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on biomat.com, including 21 speed issues and 2 SEO issues. 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.