goodeggs.com website review

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

About 571 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

Your mobile performance score is 57 (desktop: 67). Pages that score under 90 lose visitors before the first paint.

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

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

About 118 KiB of CSS is downloaded but never applied 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 (Unpkg, transcend-cdn.com and Klaviyo and others), adding 2.6 MB and 415 ms of main-thread time.

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

Unpkg costs a phone 228 ms of main-thread work and 592 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.

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

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

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

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

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.

Real visitors wait 940 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

The layout shifts by 0.101 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.1 MB in 99 requests on a phone: images 7.1 MB (60), scripts 1.3 MB (19) and fonts 338 KiB (7). Under 2 MB keeps phones on slow connections fast.

survey_popin_header.731c967eb3be359ff168.png weighs 4.5 MB. On a phone connection a single image that size takes seconds.

10 images are downloaded at several times the size a phone draws them, for example survey_popin_header.731c967eb3be359ff168.png at 2,000 px wide, shown at 318 px. Resized copies would save about 4.3 MB.

4 images (5.0 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

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

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

9 elements hidden from screen readers can still receive keyboard focus.

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

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

Heading levels should only increase by one: 3 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 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.

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

Your title is 100 characters, so Google will cut it off around 60: “Organic Grocery Delivery - Meal solutions and grocery items from the Deli, Bakery, Pantry…”.

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

Your meta description is only 58 characters: “Absurdly fresh groceries and meal-kits delivered same day.”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title), so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links have no real href, so search engines can't follow them.

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

The homepage links to 767 pages on goodeggs.com and 23 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 /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.

/join-membership, /refer-a-friend, /giftcards, /for-you, /fall and /new and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

/join-membership, /for-you, /fall, /thanksgiving, /new and /good-deals and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=137010767&Ver=2&mid=dc65ff72-8473-42de-9b46-85f794e8c65c&bo=2&sid=6b38ec30d05611f19c180d562e9b5d52&vid=6b3922e0d05611f1a3cf89f867d76f84&vids=1&msclkid=N&pi=918639831&l.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

24 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Opening https://goodeggs.com goes through 2 redirects before the homepage loads.

3 links go through two or more redirects, for example https://help.goodeggs.com/.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

goodeggs.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

goodeggs.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 4 mores (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 42 cookies (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 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.