18chestnuts.com website review

20 files are served with short cache lifetimes, so returning visitors download them again (1,002 KiB).

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

12 images could be 523 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

8 third-party services load with your homepage (alia-prod.com, route.com and loox.io and others), adding 1.5 MB and 1.2 s of main-thread time.

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

alia-prod.com costs a phone 475 ms of main-thread work and 555 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.

route.com costs a phone 224 ms of main-thread work and 596 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.

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

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

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

About 77 KiB of CSS is downloaded but never applied on this page.

10 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 32.0 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 32.3 s. Good is under 3.8 s.

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

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

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

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

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

Your homepage downloads 6.4 MB in 316 requests on a phone: images 1.8 MB (50), fonts 1.7 MB (25) and scripts 1.5 MB (77). Under 2 MB keeps phones on slow connections fast.

FallBundleLayflat1x1.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).

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

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

Some list items are not inside a list.

Summary elements must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

Your title is 79 characters, so Google will cut it off around 60: “18 Chestnuts | Gourmet Plant-Based Soup Delivery for Your Health – 18 CHESTNUTS”.

Your meta description is 201 characters; Google truncates after about 160, so the end of your pitch is cut.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 112 pages on 18chestnuts.com and 9 external pages.

/pages/build-your-own-bundle, /pages/benefits, /blogs/recipes, /blogs/toppings, /blogs/ingredients and /blogs/care-and-comfort and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/nutrition and /pages/our-story have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://www.18chestnuts.com/.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

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.

18chestnuts.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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

The page uses urgency cues (a countdown or limited-time wording).

DMARC is set to p=none, so mail pretending to be 18chestnuts.com is still delivered. Reports are on, so moving to quarantine is the next step.

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 Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 6 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 28 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 52 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.