Website review, no card needed
mizulife.com website review
Visit site (opens in a new tab)Reviewed 20 October 202630 issues · 77 checks
This review found 30 issues worth fixing on mizulife.com, 11 of them high impact, across 77 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
82B- #30,134 of 106,187 reviewed websitesbeats 66%
- #19,986 of 59,843 online storesbeats 60%
- #19,326 of 54,557 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.5 s |
| May 9, 2026 | 1.4 s |
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 100 ms |
| May 9, 2026 | 97 ms |
| May 16, 2026 | 95 ms |
| May 23, 2026 | 95 ms |
| May 30, 2026 | 95 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 111 ms |
| Jul 11, 2026 | 110 ms |
| Jul 18, 2026 | 107 ms |
| Jul 25, 2026 | 110 ms |
| Aug 1, 2026 | 103 ms |
| Aug 8, 2026 | 104 ms |
| Aug 15, 2026 | 103 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 104 ms |
| Sep 5, 2026 | 101 ms |
| Sep 12, 2026 | 105 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 112 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 117 ms |
| Oct 17, 2026 | 114 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.9 s
1.3 s
1.7 s
2.2 s
2.6 s
3.0 s
3.5 s
Speed
Render-blocking requests
2.4 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Reduce unused JavaScript
1.9 s · 379 KiBAbout 379 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 75). 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 (Hotjar, Google Tag Manager and Shopify and others), adding 1.3 MB and 616 ms of main-thread time.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 153 ms
153 msGoogle Tag Manager costs a phone 153 ms of main-thread work and 311 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 110 ms
110 msShopify costs a phone 110 ms of main-thread work and 462 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.
Use efficient cache lifetimes
100 ms · 100 KiB16 files are served with short cache lifetimes, so returning visitors download them again (100 KiB).
Reduce unused CSS
150 ms · 38 KiBAbout 38 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.
Minify JavaScript
150 ms · 10 KiB10 KiB could be saved by minifying JavaScript.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 102 ms. During a long task the page ignores taps.
Improve image delivery
67 KiB2 images could be 67 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
39 KiBPolyfills for old browsers add 39 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.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.9 s
14.9 sYour largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 6.4 s
6.4 sThe first text or image appears after 6.4 s on a phone. Good is under 1.8 s.
Time to Interactive: 14.9 s
14.9 sThe page becomes fully interactive after 14.9 s. Good is under 3.8 s.
Speed Index: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 100 ms to 114 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 114 ms
114 msReal visitors wait 114 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: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 475 ms
475 msReal visitors wait 475 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 138 ms
138 msScripts block the page for only 138 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.9 MB in 326 requests
2.9 MBYour homepage downloads 2.9 MB in 326 requests on a phone: scripts 1.6 MB (136), other files 981 KiB (158) and images 137 KiB (8). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.81 g of CO₂e: 97.1 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
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 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.
2 checks passed
Every image has alt text
All 20 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (82 characters)
Your title is 82 characters, so Google will cut it off around 60: “Mizu Stainless Steel Water Bottles, Reusable Straws, Mugs and Tumblers – Mizu Life”.
Meta description is long (260 characters)
Your meta description is 260 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
59 internal links, 4 external
The homepage links to 59 pages on mizulife.com and 4 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Mizu Life”.
Canonical URL set
The canonical URL is https://www.mizulife.com/.
Structured data in place
Structured data found: Organization.
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.mizulife.com/sitemap.xml.
AI search readiness
3 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
llms.txt published
The site publishes https://www.mizulife.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.mizulife.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.mizulife.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
6 pages without a meta description
https://www.mizulife.com/collections/all-products, https://www.mizulife.com/collections/beer-wine, https://www.mizulife.com/blogs/blog, https://www.mizulife.com/pages/mizu-custom-quote, https://www.mizulife.com/customer_authentication/redirect and https://www.mizulife.com/collections/new-colors have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.mizulife.com/customer_authentication/redirect has 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 27 found) and read each the way a search engine does.
3 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.
Best practices
9 small tap targets
9 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 138 words
The homepage has only about 138 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP ESPRESSO” and “SHOP NOW”.
12 calls to action
The homepage has 12 calls to action, for example “SHOP”, “SHOP ALL” and “CONTACT”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Hotjar and LinkedIn Insight.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 2 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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
37 other companies contacted
Loading the homepage contacts 37 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 mizulife.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on mizulife.com, including 11 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.