ketoactivate.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, konsciousketo.com and truevaultcdn.com and others), adding 2.8 MB and 963 ms of main-thread time.

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

Google Tag Manager costs a phone 540 ms of main-thread work and 973 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.1 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 19 ms of main-thread work and 1.3 MB 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.

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

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

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

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

3 KiB could be saved by minifying JavaScript.

Your largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A breakthrough, delicious ketone blend that helps you feel …”.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.0 MB in 186 requests on a phone: images 2.2 MB (67), scripts 1.9 MB (55) and other files 528 KiB (45). Under 2 MB keeps phones on slow connections fast.

17 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

6 images are downloaded at several times the size a phone draws them, for example ka-updated-sfp-042624.png at 1,240 px wide, shown at 390 px. Resized copies would save about 205 KiB.

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

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

No meta description, so Google writes its own snippet from whatever text it finds.

Google's crawler is blocked from indexing this page.

Your title is only 29 characters: “Chocolate Discovery Burns Fat”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“A breakthrough, delicious ketone blend that helps…”, “Keto Activate Dark Chocolate Truffle” and “Keto Activate Dark Chocolate Truffle”). One clear main headline is easier for people and search engines.

The homepage links to 15 pages on ketoactivate.com and 14 external pages.

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.

https://ketoactivate.com/pages/dark-chocolate-truffle, https://ketoactivate.com/pages/shipping-refund-policy, https://ketoactivate.com/pages/terms-conditions and https://ketoactivate.com/pages/accessibility-statement are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://ketoactivate.com/pages/dark-chocolate-truffle, https://ketoactivate.com/pages/shipping-refund-policy, https://ketoactivate.com/pages/terms-conditions and https://ketoactivate.com/pages/accessibility-statement have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 4 pages linked from your homepage and read each the way a search engine does.

2 images failed to load on a phone, for example https://pixel.adblade.com/imps.php?sgms=17718.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 1,352 words of visible text.

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