ahava.com website review

A phone's processor spends 13.7 s on main-thread work while loading, 7.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

8 third-party services load with your homepage (Other Google APIs/SDKs, Google Tag Manager and osano.com and others), adding 2.7 MB and 2.2 s of main-thread time.

About 947 KiB of JavaScript is downloaded but never used on this page.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

Other Google APIs/SDKs costs a phone 515 ms of main-thread work and 940 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 Tag Manager costs a phone 448 ms of main-thread work and 336 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.

28 files are served with short cache lifetimes, so returning visitors download them again (409 KiB).

Yotpo costs a phone 327 ms of main-thread work and 468 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 block the main thread while loading, the longest for 369 ms. During a long task the page ignores taps.

osano.com costs a phone 353 ms of main-thread work and 92 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.

Klaviyo costs a phone 203 ms of main-thread work and 336 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.

3 images could be 55 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 55 KiB of CSS is downloaded but never applied on this page.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need.

17 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 4.5 MB in 368 requests on a phone: scripts 2.7 MB (126), other files 866 KiB (172) and fonts 350 KiB (14). Under 2 MB keeps phones on slow connections fast.

1 image (35 KiB) is 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.

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

14 images have no alt text, which hurts accessibility and image search.

1 button has no accessible name, so screen readers announce just “button”.

All page content should be contained by landmarks: 10 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 on the page fails this check, rated moderate by axe-core.

6 visible links have no text or label, so screen readers cannot say where they go.

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (2 elements).

There are 3 <h1> headlines (“#sticky-header-content .logo-normal, #sticky-head…”, “30% OFF $100+ 40% OFF $200+” and “ABOUT AHAVA”). One clear main headline is easier for people and search engines.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 249 pages on ahava.com and 9 external pages.

/pages/sms has no meta description, so Google writes the search snippet from whatever text it finds.

/pages/find-your-product and /pages/rewards have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 96 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://www.ahava.com/.

19 of 58 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

3 errors were logged to the browser console while the page loaded, for example “show_more is not defined”.

1 link to other sites is dead, for example https://ahavacom.aftership.com/ (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

ahava.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 34 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 523 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

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

Loading the homepage contacts 55 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.