Website review, no card needed
avon.co.za website review
Visit site (opens in a new tab)Reviewed 28 October 202649 issues · 91 checks
This review found 49 issues worth fixing on avon.co.za, 21 of them high impact, across 91 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
52FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.9 s |
| May 16, 2026 | 4.9 s |
| May 23, 2026 | 4.9 s |
| May 30, 2026 | 4.8 s |
| Jun 6, 2026 | 4.8 s |
| Jun 13, 2026 | 4.8 s |
| Jun 20, 2026 | 4.8 s |
| Jun 27, 2026 | 4.8 s |
| Jul 4, 2026 | 4.9 s |
| Jul 11, 2026 | 4.8 s |
| Jul 18, 2026 | 4.8 s |
| Jul 25, 2026 | 4.9 s |
| Aug 1, 2026 | 4.8 s |
| Aug 8, 2026 | 4.8 s |
| Aug 15, 2026 | 4.9 s |
| Aug 22, 2026 | 4.9 s |
| Aug 29, 2026 | 4.9 s |
| Sep 5, 2026 | 4.8 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 4.8 s |
| Oct 3, 2026 | 4.8 s |
| Oct 10, 2026 | 4.8 s |
| Oct 17, 2026 | 4.8 s |
| Oct 24, 2026 | 4.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 348 ms |
| May 16, 2026 | 346 ms |
| May 23, 2026 | 340 ms |
| May 30, 2026 | 339 ms |
| Jun 6, 2026 | 341 ms |
| Jun 13, 2026 | 341 ms |
| Jun 20, 2026 | 340 ms |
| Jun 27, 2026 | 337 ms |
| Jul 4, 2026 | 339 ms |
| Jul 11, 2026 | 334 ms |
| Jul 18, 2026 | 329 ms |
| Jul 25, 2026 | 331 ms |
| Aug 1, 2026 | 334 ms |
| Aug 8, 2026 | 341 ms |
| Aug 15, 2026 | 348 ms |
| Aug 22, 2026 | 356 ms |
| Aug 29, 2026 | 363 ms |
| Sep 5, 2026 | 369 ms |
| Sep 12, 2026 | 370 ms |
| Sep 19, 2026 | 373 ms |
| Sep 26, 2026 | 374 ms |
| Oct 3, 2026 | 381 ms |
| Oct 10, 2026 | 390 ms |
| Oct 17, 2026 | 396 ms |
| Oct 24, 2026 | 403 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
6.6 s · 1.9 MB66 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).
Reduce unused JavaScript
1.9 s · 953 KiBAbout 953 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.
Improve image delivery
1.4 s · 598 KiB20 images could be 598 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Google Tag Manager adds 1.9 s
1.9 sGoogle Tag Manager costs a phone 1.9 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.1 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 6
6/100Your mobile performance score is 6 (desktop: 24). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.7 s
A phone's processor spends 7.7 s on main-thread work while loading, 4.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Dynamic Yield and Google CDN and others), adding 2.2 MB and 3.1 s of main-thread time.
Reduce unused CSS
450 ms · 90 KiBAbout 90 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Dynamic Yield adds 364 ms
364 msDynamic Yield costs a phone 364 ms of main-thread work and 295 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 375 ms. During a long task the page ignores taps.
Google CDN adds 352 ms
352 msGoogle CDN costs a phone 352 ms of main-thread work and 102 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.
Google Maps adds 241 ms
241 msGoogle Maps costs a phone 241 ms of main-thread work and 375 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.
Optanon adds 251 ms
251 msOptanon costs a phone 251 ms of main-thread work and 230 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.
2,617 HTML elements
The page has 2,617 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
14 KiB14 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.
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: 14 ms
14 msYour server sent the HTML in 14 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.
Real-user LCP: 7.6 s
7.6 sReal visitors wait 7.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 6.4 s
6.4 sReal visitors see the first content after 6.4 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 16.4 s
16.4 sYour largest element takes 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Avon Her Wisdom”.
Time to Interactive: 27.9 s
27.9 sThe page becomes fully interactive after 27.9 s. Good is under 3.8 s.
Cumulative Layout Shift: 1.174
1.174The layout shifts by 1.174 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 2.3 s
2.3 sScripts block taps and scrolling for 2.3 s in total while the page loads. Good is under 200 ms.
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Real-user INP: 391 ms
391 msReal visitors wait 391 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.24
0.24For real visitors the layout shifts by 0.24 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 348 ms to 403 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.9 s to 4.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 4.6 MB in 144 requests
4.6 MBYour homepage downloads 4.6 MB in 144 requests on a phone: scripts 2.3 MB (36), images 1.3 MB (41) and fonts 608 KiB (8). Under 2 MB keeps phones on slow connections fast.
7 images in older formats
7 images (586 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.
4 images below the first screen load straight away
4 images further down the page (94 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.29 g of CO₂e: 155.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Images must have alternative text (10 elements)
Images must have alternative text: 10 elements on the page fail this check, rated critical by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
11 form fields without a label
11 form fields have no label, so screen readers announce an empty box and autofill guesses.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (19 characters)
Your title is only 19 characters: “AVON | South Africa”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
16 links crawlers can't follow
16 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
118 internal links, 4 external
The homepage links to 118 pages on avon.co.za and 4 external pages.
4 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “South Africa’s coolest make-up brand for all your beauty essentials online today! Free delivery to your door when you s…”.
Canonical URL set
The canonical URL is https://my.avon.co.za/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://my.avon.co.za/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.
No llms.txt
There is no https://my.avon.co.za/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.
2 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 (553 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share a meta description
https://my.avon.co.za/304-1072/bath-body/her-wisdom, https://my.avon.co.za/304-1073/bath-body/her-wisdom-baobab, https://my.avon.co.za/304-1075/bath-body/her-wisdom-sim-sim and https://my.avon.co.za/304-1074/bath-body/her-wisdom-osmanthus use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://my.avon.co.za/confidentiality and https://my.avon.co.za/product/22720/avon-nourishing-lip-oil-7ml have no <h1> headline, so visitors and search engines get no clear main topic.
15 pages with very little text
https://my.avon.co.za/confidentiality, https://my.avon.co.za/304-1072/bath-body/her-wisdom, https://my.avon.co.za/303-314/fragrance/far-away, https://my.avon.co.za/433-434/gifts/gifts-for-her, https://my.avon.co.za/433-435/gifts/gifts-for-him and https://my.avon.co.za/product/22720/avon-nourishing-lip-oil-7ml and 9 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 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
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
67 of 76 tappable elements near the top are at least 24 px.
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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
About 477 words of copy
The homepage carries about 477 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “JOIN TODAY”.
10 calls to action
The homepage has 10 calls to action, for example “Discover Her Wisdom Collection Shop Now” and “SHOP NOW”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
14 cookies set on arrival
14Opening the homepage sets 14 cookies (measured from a US location before any click).
17 other companies contacted
Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 avon.co.za, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Avon
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on avon.co.za, including 28 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.