alchemynaturals.com website review

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

About 539 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

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

8 third-party services load with your homepage (cloudfront.net, Klaviyo and joinground.com and others), adding 1.7 MB and 612 ms of main-thread time.

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

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

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

cloudfront.net costs a phone 159 ms of main-thread work and 1,003 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.

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

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

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

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

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

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

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

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

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

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

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' tap response (inp) went from 106 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 3.7 MB in 198 requests on a phone: images 1.4 MB (21), scripts 1.2 MB (69) and other files 749 KiB (86). Under 2 MB keeps phones on slow connections fast.

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

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Elements with visible text labels do not have matching accessible names. (1 element).

There are 2 <h1> headlines (“Alchemy Naturals” and “New CBD Topical”). One clear main headline is easier for people and search engines.

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

The homepage links to 88 pages on alchemynaturals.com and 5 external pages.

Your homepage links to https://alchemynaturals.com/products/cbd-gummies-for-sex-old, which answers with an error. Visitors hit a dead end and search engines drop it.

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

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

4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://apps3.omegatheme.com/cookies-notification/client/save-cookies.php' from origin 'ht…”.

1 image is served at too low a resolution for sharp phone screens.

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

The homepage carries about 823 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (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 14 cookies (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 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.