Website review, no card needed
beautyzir.com website review
Visit site (opens in a new tab)Reviewed 5 November 202634 issues · 83 checks
This review found 34 issues worth fixing on beautyzir.com, 7 of them high impact, across 83 checks. The most urgent: fails Core Web Vitals for real visitors. 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
73C- #91,551 of 123,940 reviewed websitesbeats 23%
- #57,047 of 69,726 online storesbeats 15%
- #53,363 of 63,424 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.2 s |
| Oct 17, 2026 | 3.2 s |
| Oct 24, 2026 | 3.2 s |
| Oct 31, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 115 ms |
| May 30, 2026 | 115 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 110 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 115 ms |
| Jul 18, 2026 | 114 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 138 ms |
| Aug 8, 2026 | 149 ms |
| Aug 15, 2026 | 176 ms |
| Aug 22, 2026 | 203 ms |
| Aug 29, 2026 | 230 ms |
| Sep 5, 2026 | 261 ms |
| Sep 12, 2026 | 266 ms |
| Sep 19, 2026 | 247 ms |
| Sep 26, 2026 | 265 ms |
| Oct 3, 2026 | 246 ms |
| Oct 10, 2026 | 246 ms |
| Oct 17, 2026 | 247 ms |
| Oct 24, 2026 | 243 ms |
| Oct 31, 2026 | 228 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
1.3 s
2.7 s
4.0 s
5.4 s
6.7 s
8.1 s
9.4 s
10.8 s
Speed
4,494 HTML elements
The page has 4,494 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
650 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Reduce unused JavaScript
300 ms · 330 KiBAbout 330 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused CSS
300 ms · 63 KiBAbout 63 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 499 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 108 ms
108 msShopify costs a phone 108 ms of main-thread work and 424 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.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Klarna and Google CDN and others), adding 738 KiB and 183 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 52 KiB9 files are served with short cache lifetimes, so returning visitors download them again (52 KiB).
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 79 ms. During a long task the page ignores taps.
Improve image delivery
50 ms · 18 KiB2 images could be 18 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
Legacy JavaScript
50 ms · 7 KiBPolyfills for old browsers add 7 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Duplicated JavaScript
11 KiB11 KiB JavaScript is shipped twice across bundles.
Minify JavaScript
9 KiB9 KiB could be saved by minifying JavaScript.
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 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: 6.3 s
6.3 sYour largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load duration (3.1 s).
Time to Interactive: 9.4 s
9.4 sThe page becomes fully interactive after 9.4 s. Good is under 3.8 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 224 ms
224 msReal visitors wait 224 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 105% slower for real visitors
+105%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 115 ms to 228 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 60% slower for real visitors
+60%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.7 s
5.7 sVisually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.
4 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.047
0.047The layout barely moves while loading (CLS 0.047, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 18 ms
18 msScripts block the page for only 18 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.2 MB in 200 requests
2.2 MBYour homepage downloads 2.2 MB in 200 requests on a phone: scripts 857 KiB (43), other files 807 KiB (116) and images 311 KiB (25). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.61 g of CO₂e: 73.5 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 text elements with low contrast
3 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 (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (13 elements)
Alternative text of images should not be repeated as text: 13 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and 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. (1 element).
2 checks passed
Every image has alt text
All 35 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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
Title is long (85 characters)
Your title is 85 characters, so Google will cut it off around 60: “BeautyZir Professional Dental Laboratory Materials & CAD/CAM Supplies – New Beautyzir”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“New Beautyzir” and “New Beautyzir”). One clear main headline is easier for people and search engines.
Meta description is long (238 characters)
Your meta description is 238 characters; Google truncates after about 160, so the end of your pitch is cut.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
228 internal links, 11 external
The homepage links to 228 pages on beautyzir.com and 11 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.beautyzir.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.beautyzir.com/sitemap.xml.
AI search readiness
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (2,612 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.beautyzir.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
13 pages share a meta description
https://www.beautyzir.com/policies/shipping-policy, https://www.beautyzir.com/policies/refund-policy, https://www.beautyzir.com/policies/privacy-policy, https://www.beautyzir.com/policies/terms-of-service, https://www.beautyzir.com/collections/all and https://www.beautyzir.com/collections/3d-pro-multilayer and 7 others use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.beautyzir.com/collections/all and https://www.beautyzir.com/collections/zirconia 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 66 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 15 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 15 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
21 of 22 tappable elements near the top are at least 24 px.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
About 307 words of copy
The homepage carries about 307 words of visible text.
4 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact us”, “Register / Login” and “Subscribe”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: LinkedIn Insight.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight 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.
11 cookies set on arrival
11Opening the homepage sets 11 cookies, 1 of them by other companies (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.
23 other companies contacted
Loading the homepage contacts 23 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 beautyzir.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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Whatsapp Chat Button · Ecomsend · amazonaws.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
- 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 beautyzir.com, including 17 speed issues, 5 SEO issues and 2 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.