eatdeux.com website review

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

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

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

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

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

8 third-party services load with your homepage (Hotjar, Yotpo and Shopify and others), adding 372 KiB and 215 ms of main-thread time.

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

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

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

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

2 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Your homepage downloads 3.2 MB in 164 requests on a phone: images 1.5 MB (43), other files 679 KiB (71) and scripts 672 KiB (40). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example IMG_3014_2.png at 358 px wide, shown at 89 px. Resized copies would save about 51 KiB.

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 26 characters: “DEUX | Good-For-You Snacks”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 36 pages on eatdeux.com and 2 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.eatdeux.com/pages/become-a-member, https://www.eatdeux.com/collections/bundle-sale, https://www.eatdeux.com/collections/cookie-dough, https://www.eatdeux.com/collections/dessert-spreads, https://www.eatdeux.com/collections/donuts and https://www.eatdeux.com/collections/all-products and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.eatdeux.com/collections/all-products has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.eatdeux.com/pages/become-a-member, https://www.eatdeux.com/pages/contact and https://www.eatdeux.com/pages/invite-friends 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 14 pages linked from your homepage and read each the way a search engine does.

3 images failed to load on a phone, for example https://www.eatdeux.com/Liquid%20error%20(snippets/responsive-image%20line%2042):%20invalid%20url%20input.

4 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'document'”.

Large scripts ship without source maps.

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

Social proof on the homepage: 5 testimonial or review blocks. 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.

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

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 607 words of visible text.

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