essentialfoods.com website review

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

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

Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (dixa.io, rebuyengine.com and Klaviyo and others), adding 2.1 MB and 1.2 s of main-thread time.

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

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

rebuyengine.com costs a phone 293 ms of main-thread work and 712 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.

dixa.io costs a phone 295 ms of main-thread work and 514 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.

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

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

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

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

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

Polyfills for old browsers add 48 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.

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

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

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

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

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

Your homepage downloads 7.3 MB in 318 requests on a phone: images 3.9 MB (90), scripts 1.9 MB (101) and other files 767 KiB (89). Under 2 MB keeps phones on slow connections fast.

ESSENCE_Marrow_bone_mobile.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images further down the page (123 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 2.06 g of CO₂e: 247.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

18 tap targets are too small or too close together to hit reliably with a finger.

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

Interactive controls must not be nested: 7 elements on the page fail this check, rated serious by axe-core.

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

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

There are 5 <h1> headlines (“Ready to bring joy from its spot beneath the Chri…”, “A new member. Long-lasting enjoyment” and “Natural ingredients to match the natural instinct”). One clear main headline is easier for people and search engines.

Structured data found ((untyped), Organization and WebSite) but with 3 problems, for example “Organization: url points at a different host (https://essentialfoods.dk)”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 253 pages on essentialfoods.com and 12 external pages.

Your homepage links to https://essentialfoods.com/collections, which answers with an error. Visitors hit a dead end and search engines drop it.

https://essentialfoods.com/collections/dog and https://essentialfoods.com/blogs/dog all use the title “Dog – Essential Foods”. Search engines can't tell which page to show for a search, so each competes with the others.

https://essentialfoods.com/pages/wishlist, https://essentialfoods.com/pages/contact-1, https://essentialfoods.com/pages/member-get-member, https://essentialfoods.com/blogs/dog and https://essentialfoods.com/pages/what-is-bof have no meta description, so Google writes the search snippet from whatever text it finds.

https://essentialfoods.com/collections/all and https://essentialfoods.com/collections/dog use the same meta description. A description written for each page earns more clicks.

https://essentialfoods.com/pages/member-get-member has no <h1> headline, so visitors and search engines get no clear main topic.

https://essentialfoods.com/collections/all-meals, https://essentialfoods.com/collections/dog-meals, https://essentialfoods.com/pages/wishlist, https://essentialfoods.com/collections/dog and https://essentialfoods.com/collections/british-heritage-kitchens took over 3 s to send their HTML from our server.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_EMPTY_RESPONSE”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

6 images are served at too low a resolution for sharp phone screens.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 1,156 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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