ahyes.org website review

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

Your mobile performance score is 80. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Clarity, Klaviyo and Bazaarvoice and others), adding 1.6 MB and 832 ms of main-thread time.

8 images could be 760 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

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

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

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

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

Shopify costs a phone 98 ms of main-thread work and 613 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.

azurefd.net costs a phone 46 ms of main-thread work and 329 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.

About 30 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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.

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

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

Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Image”.

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

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

Your homepage downloads 5.7 MB in 474 requests on a phone: other files 1.9 MB (287), images 1.9 MB (51) and scripts 1.2 MB (109). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (176 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

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. (1 element).

There are 5 <h1> headlines (“CLEANSE Intimate Wash”, “COCO Oil-Based Lubricant Applicators” and “CLEANSE Intimate Wash”). One clear main headline is easier for people and search engines.

Your meta description is 286 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 85 pages on ahyes.org and 7 external pages.

Your homepage links to https://www.ahyes.org/pages/values and https://www.ahyes.org/pages/ingredients, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.ahyes.org/collections/bundles has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.ahyes.org/collections/ah-yes%C2%AE-moisturizers, whose canonical is https://www.ahyes.org/collections/ah-yes%c2%ae-moisturizers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.ahyes.org/pages/contact-help has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.ahyes.org/pages/contact-help has 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.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

The homepage carries about 427 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Ads and 2 mores (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.

Opening the homepage sets 25 cookies, 1 of them by other companies (measured from a US location before any click).

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.

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