Website review, no card needed
aziobeauty.com website review
Visit site (opens in a new tab)Reviewed 9 November 202633 issues · 78 checks
This review found 33 issues worth fixing on aziobeauty.com, 11 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. 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
86B- #12,289 of 126,178 reviewed websitesbeats 87%
- #7,340 of 70,389 online storesbeats 85%
- #7,107 of 63,910 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 195 ms |
| May 30, 2026 | 203 ms |
| Jun 6, 2026 | 207 ms |
| Jun 13, 2026 | 203 ms |
| Jun 20, 2026 | 194 ms |
| Jun 27, 2026 | 189 ms |
| Jul 4, 2026 | 185 ms |
| Jul 11, 2026 | 197 ms |
| Jul 18, 2026 | 202 ms |
| Jul 25, 2026 | 201 ms |
| Aug 1, 2026 | 197 ms |
| Aug 8, 2026 | 196 ms |
| Aug 15, 2026 | 195 ms |
| Aug 22, 2026 | 198 ms |
| Aug 29, 2026 | 199 ms |
| Sep 5, 2026 | 197 ms |
| Sep 12, 2026 | 198 ms |
| Sep 19, 2026 | 194 ms |
| Sep 26, 2026 | 198 ms |
| Oct 3, 2026 | 208 ms |
| Oct 10, 2026 | 211 ms |
| Oct 17, 2026 | 212 ms |
| Oct 24, 2026 | 209 ms |
| Oct 31, 2026 | 195 ms |
| Nov 7, 2026 | 187 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
Use efficient cache lifetimes
3.6 s · 584 KiB15 files are served with short cache lifetimes, so returning visitors download them again (584 KiB).
Reduce unused JavaScript
2.3 s · 449 KiBAbout 449 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Improve image delivery
2.1 s · 475 KiB8 images could be 475 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.
Render-blocking requests
1.9 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Facebook and alia-prod.com and others), adding 2.2 MB and 782 ms of main-thread time.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Legacy JavaScript
300 ms · 71 KiBPolyfills for old browsers add 71 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Shopify adds 217 ms
217 msShopify costs a phone 217 ms of main-thread work and 1.0 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 189 ms. During a long task the page ignores taps.
Reduce unused CSS
41 KiBAbout 41 KiB of CSS is downloaded but never applied on this page.
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.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 928 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 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: 18.7 s
18.7 sYour largest element takes 18.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Azio Beauty Skin Complex”.
Time to Interactive: 18.8 s
18.8 sThe page becomes fully interactive after 18.8 s. Good is under 3.8 s.
Speed Index: 8.1 s
8.1 sVisually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 937 ms
937 msReal visitors wait 937 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 195 ms to 187 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 187 ms
187 msReal visitors wait 187 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 101 ms
101 msScripts block the page for only 101 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 137 requests
2.9 MBYour homepage downloads 2.9 MB in 137 requests on a phone: scripts 1.5 MB (66), images 774 KiB (16) and fonts 546 KiB (5). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (519 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
2 images far larger than shown
274 KiB2 images are downloaded at several times the size a phone draws them, for example hero-summer-lineup-hd.jpg at 2,048 px wide, shown at 390 px. Resized copies would save about 274 KiB.
1 image below the first screen load straight away
1 image further down the page (152 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.83 g of CO₂e: 99.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
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.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
44 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: 44 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (179 characters)
Your meta description is 179 characters; Google truncates after about 160, so the end of your pitch is cut.
38 internal links, 8 external
The homepage links to 38 pages on aziobeauty.com and 8 external pages.
7 checks passed
One H1 headline
Your main headline reads: “The routine, simplifiedto what actually works.”.
Title: 65 characters
Your title is a healthy 65 characters: “Azio Beauty | Skin longevity skincare with clinical-grade actives”.
Canonical URL set
The canonical URL is https://aziobeauty.com/.
Structured data in place
Structured data found: FAQPage, ItemList, Organization and WebSite.
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://aziobeauty.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 description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (864 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://aziobeauty.com/llms.txt (3 KiB, 12 links), a plain-text guide to the site for AI tools.
Other pages
4 linked pages are broken
Your homepage links to https://aziobeauty.com/pages/support, https://aziobeauty.com/pages/our-story, https://aziobeauty.com/pages/ingredients and https://aziobeauty.com/pages/sustainability, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages share a title
https://aziobeauty.com/pages/beauty-simplified and https://aziobeauty.com/collections/all all use the title “Shop Azio Beauty | Anti-ageing skincare and sets from £24”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://aziobeauty.com/products/the-ultimate-collection-3 and https://aziobeauty.com/blogs have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://aziobeauty.com/pages/beauty-simplified and https://aziobeauty.com/collections/all use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://aziobeauty.com/blogs, whose canonical is https://aziobeauty.com/blogs/azio. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 found) and read each the way a search engine does.
3 checks passed
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://analytics.google.com/g/collect?v=2&tid=G-8QZCVZJG4V>m=45je6b41h1v895877853za200zd895877853xf1&…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
Tap targets are thumb-sized
6 of 7 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: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
About 781 words of copy
The homepage carries about 781 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW →”.
8 calls to action
The homepage has 8 calls to action, for example “SHOP”, “BLACK FRIDAY SIGN UP” and “Shop”.
8 short forms
8 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics, Meta Pixel and TikTok Pixel.
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 Tag Manager, Klaviyo, Meta Pixel and TikTok 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.
20 cookies set on arrival
20Opening the homepage sets 20 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.
21 other companies contacted
Loading the homepage contacts 21 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 aziobeauty.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
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 aziobeauty.com, including 15 speed issues, 1 SEO issue 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.