sakara.com website review

33 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 12.2 s faster on a phone.

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

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

8 third-party services load with your homepage (kustomerapp.com, Impact Radius and ketchcdn.com and others), adding 4.0 MB and 136 ms of main-thread time.

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

sanity.io costs a phone 0 ms of main-thread work and 2.0 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.

Cloudinary costs a phone 0 ms of main-thread work and 1.8 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.

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

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

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

1 file is served with short cache lifetimes, so returning visitors download them again (24 KiB).

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

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

Your largest element takes 22.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Silver stacked bowls with popcorn on a green background”.

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

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

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

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

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

Your homepage downloads 6.7 MB in 252 requests on a phone: images 3.7 MB (42), media 1.8 MB (11) and scripts 703 KiB (132). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example 180a7e4f-11a4-4601-9f6c-7d6bea85e2ff.avif at 640 px wide, shown at 160 px. Resized copies would save about 71 KiB.

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

4 buttons have no accessible name, so screen readers announce just “button”.

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

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.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 86 pages on sakara.com and 6 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.

There is no https://www.sakara.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.sakara.com/mag and https://www.sakara.com/pages/nutrition-program-compare use the same meta description. A description written for each page earns more clicks.

https://www.sakara.com/nutrition/detox, https://www.sakara.com/collections/shop-by-collection, https://www.sakara.com/next-week-menu, https://www.sakara.com/pages/about, https://www.sakara.com/pages/sakara-podcast and https://www.sakara.com/pages/the-sakara-promise and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.sakara.com/nutrition/detox, https://www.sakara.com/collections/shop-by-collection, https://www.sakara.com/pages/about, https://www.sakara.com/pages/sakara-podcast, https://www.sakara.com/pages/the-sakara-promise and https://www.sakara.com/pages/nutrition-program-compare and 7 others have 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 49 found) and read each the way a search engine does.

47 of 105 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”.

Social proof on the homepage: 3 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 540 words of visible text.

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

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