keithscacao.com website review

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

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

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

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

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

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

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

Shopify costs a phone 93 ms of main-thread work and 595 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 long tasks block the main thread while loading, the longest for 82 ms. During a long task the page ignores taps.

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

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

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

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

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

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

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

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

The first text or image appears after 1.8 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' largest content (lcp) went from 1.5 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.4 MB in 236 requests on a phone: media 3.7 MB (1), scripts 1.1 MB (90) and other files 875 KiB (95). Under 2 MB keeps phones on slow connections fast.

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

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

1 link has no text or label, so screen readers cannot say where it goes.

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

Your title is 85 characters, so Google will cut it off around 60: “Keith’s Cacao | Ceremonial Cacao made in Guatemala enjoyed everywhere – Keith's Cacao”.

There are 2 <h1> headlines (“” and “the originalritual”). One clear main headline is easier for people and search engines.

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

The homepage links to 58 pages on keithscacao.com and 10 external pages.

https://www.keithscacao.com/collections/ceremonialcacaoexperiences and https://www.keithscacao.com/pages/events-experiences all use the title “Events & Experiences – Keith's Cacao”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.keithscacao.com/collections/all, https://www.keithscacao.com/pages/events-experiences, https://www.keithscacao.com/pages/become-a-practitioner, https://www.keithscacao.com/pages/what-is-cacao, https://www.keithscacao.com/pages/why-drink-cacao and https://www.keithscacao.com/pages/how-to-drink-it and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.keithscacao.com/collections/all, https://www.keithscacao.com/pages/homecoming-2027, https://www.keithscacao.com/collections/ceremonialcacao, https://www.keithscacao.com/collections/cacaopractitionertraining, https://www.keithscacao.com/collections/ceremonialcacaoexperiences and https://www.keithscacao.com/collections/virtual-cacao-ceremonies and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.keithscacao.com/collections/cacaopractitionertraining took over 3 s to send its HTML from our server.

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

3 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 403 (Forbidden)”).

Social proof on the homepage: 2 trust badges. 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 1,611 words of visible text.