Website review, no card needed

avon.pl logo

avon.pl website review

Visit site (opens in a new tab)Reviewed 4 November 202649 issues · 88 checks

This review found 49 issues worth fixing on avon.pl, 23 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.4 s2.7 sMay 16Oct 312.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20263.0 s
Aug 15, 20263.2 s
Aug 22, 20263.2 s
Aug 29, 20263.3 s
Sep 5, 20263.2 s
Sep 12, 20263.1 s
Sep 19, 20263.0 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Oct 17, 20262.9 s
Oct 24, 20262.8 s
Oct 31, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
298 ms222 msMay 16Oct 31289 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026236 ms
May 23, 2026234 ms
May 30, 2026234 ms
Jun 6, 2026231 ms
Jun 13, 2026232 ms
Jun 20, 2026232 ms
Jun 27, 2026234 ms
Jul 4, 2026236 ms
Jul 11, 2026234 ms
Jul 18, 2026235 ms
Jul 25, 2026235 ms
Aug 1, 2026238 ms
Aug 8, 2026244 ms
Aug 15, 2026248 ms
Aug 22, 2026249 ms
Aug 29, 2026249 ms
Sep 5, 2026249 ms
Sep 12, 2026251 ms
Sep 19, 2026254 ms
Sep 26, 2026261 ms
Oct 3, 2026265 ms
Oct 10, 2026275 ms
Oct 17, 2026280 ms
Oct 24, 2026287 ms
Oct 31, 2026289 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

Full-page screenshot of avon.pl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. avon.pl at 0.4 s0.4 s
  2. avon.pl at 0.9 s0.9 s
  3. avon.pl at 1.3 s1.3 s
  4. avon.pl at 1.8 s1.8 s
  5. avon.pl at 2.2 s2.2 s
  6. avon.pl at 2.7 s2.7 s
  7. avon.pl at 3.1 s3.1 s
  8. avon.pl at 3.6 s3.6 s

Speed

12 to fix38
  • Use efficient cache lifetimes

    5.0 s · 1.8 MB

    69 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).

  • Improve image delivery

    1.8 s · 831 KiB

    22 images could be 831 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

  • Google Tag Manager adds 1.4 s

    1.4 s

    Google Tag Manager costs a phone 1.4 s of main-thread work and 1.3 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.4 s

    10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

  • Mobile performance score: 38

    38/100

    Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.5 s

    A phone's processor spends 4.5 s on main-thread work while loading, 2.2 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, Google CDN and Optanon and others), adding 2.0 MB and 1.9 s of main-thread time.

  • Reduce unused JavaScript

    750 ms · 756 KiB

    About 756 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 93 KiB

    About 93 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.

  • 17 long tasks on the main thread

    17 long tasks block the main thread while loading, the longest for 288 ms. During a long task the page ignores taps.

  • Google CDN adds 268 ms

    268 ms

    Google CDN costs a phone 268 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.

  • 1,896 HTML elements

    The page has 1,896 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    200 ms · 20 KiB

    Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • 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

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 17 ms

    17 ms

    Your server sent the HTML in 17 ms, well inside Google's 600 ms guideline.

Core Web Vitals

13 to fix0
  • 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 CLS: 0.27

    0.27

    For real visitors the layout shifts by 0.27 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 11.5 s

    11.5 s

    Your largest element takes 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NOWOŚĆ Każdy prezent tworzy wspomnienia. Niech te od Ciebie…”.

  • Time to Interactive: 26.9 s

    26.9 s

    The page becomes fully interactive after 26.9 s. Good is under 3.8 s.

  • Speed Index: 10.9 s

    10.9 s

    Visually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 4.1 s

    4.1 s

    The first text or image appears after 4.1 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 732 ms

    732 ms

    Scripts block taps and scrolling for 732 ms in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 3.0 s

    3.0 s

    Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 287 ms

    287 ms

    Real visitors wait 287 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 23% slower for real visitors

    +23%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 236 ms to 289 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.9 s

    2.9 s

    Real visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 906 ms

    906 ms

    Real visitors wait 906 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • 13 images without width and height

    13 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    -4%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1 checks passed
  • Cumulative Layout Shift: 0.074

    0.074

    The layout barely moves while loading (CLS 0.074, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 4.8 MB in 141 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 141 requests on a phone: scripts 2.1 MB (44), images 1.6 MB (37) and fonts 569 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    171 KiB

    4 images are downloaded at several times the size a phone draws them, for example mini-banner-pl-41_unq_f0097a6e44414510912048565d9649ce.jpg at 1,000 px wide, shown at 232 px. Resized copies would save about 171 KiB.

  • 4 images in older formats

    4 images (333 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.

  • About 1.3 g of CO₂ per visit

    1.35 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.35 g of CO₂e: 161.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

9 to fixGoogle 7989
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 5 text elements with low contrast

    5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

    2 frames have no title, so screen-reader users cannot tell what they contain.

  • Links must have discernible text (2 elements)

    Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

  • All page content should be contained by landmarks (5 elements)

    All page content should be contained by landmarks: 5 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.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Positive tabindex

    2 elements have a tabindex above 0, which scrambles the keyboard order.

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. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8581
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 21 links crawlers can't follow

    21 links have no real href, so search engines can't follow them.

  • 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.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 55 internal links, 0 external

    The homepage links to 55 pages on avon.pl and 0 external pages.

5 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “Wybierz AVON - sklep online z szerokim wyborem kosmetyków do makijażu, perfum i pielęgnacji. Sprawdź ofertę już dziś i …”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Kosmetyki AVON na wyciągnięcie ręki - sklep online | AVON”.

  • Canonical URL set

    The canonical URL is https://www.avon.pl/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.avon.pl/sitemap.xml.

AI search readiness

1 to fix88
  • 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://www.avon.pl/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 (328 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix67
  • 1 linked page is broken

    Your homepage links to https://www.avon.pl/confidentiality, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 3 pages share a title

    https://www.avon.pl/oferty-specjalne/43193, https://www.avon.pl/oferty-specjalne/43194 and https://www.avon.pl/oferty-specjalne/43192 all use the title “Oferty specjalne”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages share a meta description

    https://www.avon.pl/oferty-specjalne/43193, https://www.avon.pl/oferty-specjalne/43194 and https://www.avon.pl/oferty-specjalne/43192 use the same meta description. A description written for each page earns more clicks.

  • 14 pages with very little text

    https://www.avon.pl/6696/pomysly-na-prezenty, https://www.avon.pl/oferty-specjalne/43193, https://www.avon.pl/oferty-specjalne/43194, https://www.avon.pl/6696-8415/pomysly-na-prezenty/zestawy-upominkowe, https://www.avon.pl/305-5944/pielegnacja-ciala/rytualy-i-kolekcje-sezonowe and https://www.avon.pl/302/makijaz and 8 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 18 found) and read each the way a search engine does.

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7797
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    26 of 32 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 287 words of copy

    The homepage carries about 287 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics 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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies (measured from a US location before any click).

  • 25 other companies contacted

    Loading the homepage contacts 25 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.pl, 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
Akamai

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.pl, including 25 speed issues, 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25