Website review, no card needed
breathelio.com website review
Visit site (opens in a new tab)Reviewed 20 November 202634 issues · 78 checks
This review found 34 issues worth fixing on breathelio.com, 10 of them high impact, across 78 checks. The most urgent: improve image delivery. 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
78C- #62,123 of 123,940 reviewed websitesbeats 44%
- #40,543 of 69,719 online storesbeats 36%
- #38,716 of 63,424 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
| Nov 7, 2026 | 1.8 s |
| Nov 14, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Oct 3, 2026 | 210 ms |
| Oct 10, 2026 | 212 ms |
| Oct 31, 2026 | 203 ms |
| Nov 7, 2026 | 205 ms |
| Nov 14, 2026 | 204 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
Improve image delivery
1.1 s · 401 KiB15 images could be 401 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Main-thread work: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,938 HTML elements
The page has 3,938 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Klaviyo and Bing Ads and others), adding 1.3 MB and 384 ms of main-thread time.
Render-blocking requests
450 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Reduce unused JavaScript
150 ms · 285 KiBAbout 285 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Shopify adds 319 ms
319 msShopify costs a phone 319 ms of main-thread work and 858 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
150 ms · 58 KiBAbout 58 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 136 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
122 KiB7 files are served with short cache lifetimes, so returning visitors download them again (122 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
44 KiBPolyfills for old browsers add 44 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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 112 ms
112 msYour server sent the HTML in 112 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.
Largest Contentful Paint: 10.7 s
10.7 sYour largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A couple at a window, each holding a Lio flavoured air devi…”.
Time to Interactive: 12.8 s
12.8 sThe page becomes fully interactive after 12.8 s. Good is under 3.8 s.
Speed Index: 8.8 s
8.8 sVisually, the page fills in at 8.8 s (Speed Index). Good is under 3.4 s.
Real-user INP: 203 ms
203 msReal visitors wait 203 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 918 ms
918 msReal visitors wait 918 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Total Blocking Time: 204 ms
204 msScripts block taps and scrolling for 204 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 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-11-14, real Chrome visitors' tap response (inp) went from 210 ms to 204 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-11-14, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.
Cumulative Layout Shift: 0.023
0.023The layout barely moves while loading (CLS 0.023, good is under 0.1).
Images and page weight
Page weight: 3.8 MB in 234 requests
3.8 MBYour homepage downloads 3.8 MB in 234 requests on a phone: images 1.5 MB (51), other files 899 KiB (113) and scripts 860 KiB (51). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.08 g of CO₂e: 129.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Delayed refresh under 20 hours must not be used (1 element)
Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.
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.
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.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), 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. (7 elements).
2 checks passed
Every image has alt text
All 70 images in the HTML carry an alt attribute.
20 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (290 characters)
Your meta description is 290 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (BreadcrumbList, FAQPage, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://breathelio.com)”.
57 internal links, 18 external
The homepage links to 57 pages on breathelio.com and 18 external pages.
6 checks passed
One H1 headline
Your main headline reads: “No vapor,no battery,no nic.”.
Title: 39 characters
Your title is a healthy 39 characters: “Lio® · The Original Flavored Air Device”.
Canonical URL set
The canonical URL is https://breathelio.us/.
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://breathelio.us/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. 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://breathelio.us/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://breathelio.us/products/the-quit-pack, https://breathelio.us/pages/bundle-builder and https://breathelio.us/pages/friends have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://breathelio.us/products/the-quit-pack, https://breathelio.us/apps/parcelpanel, https://breathelio.us/pages/contact-us, https://breathelio.us/pages/bundle-builder and https://breathelio.us/pages/friends have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://breathelio.us/products/the-quit-pack, https://breathelio.us/apps/parcelpanel, https://breathelio.us/pages/contact-us, https://breathelio.us/pages/bundle-builder and https://breathelio.us/pages/friends took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.
5 checks passed
Linked pages load
5 pages of 15 loaded without an error (the rest turned automated requests away).
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 5 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.
1 checks passed
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 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 10 words
The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.
4 checks passed
15 calls to action
The homepage has 15 calls to action, for example “Track my order”, “Contact” and “Shop”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 7 testimonial or review blocks, a star rating, 2 trust badges and “Over 150,000 customers”.
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
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.
2 other companies contacted
Loading the homepage contacts 2 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 breathelio.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
Triplewhale · Kaching Bundles · Microsoft Clarity · Klaviyo Email Marketing Sms · Upcart
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
- 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 34 issues on breathelio.com, including 17 speed issues, 2 SEO issues and 4 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.