whatchefswant.com website review

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

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

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

About 282 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and jotfor.ms and others), adding 3.0 MB and 1.1 s of main-thread time.

Google CDN costs a phone 647 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.

49 KiB could be saved by minifying JavaScript.

Google Tag Manager costs a phone 225 ms of main-thread work and 428 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.

jotfor.ms costs a phone 94 ms of main-thread work and 395 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.

19 KiB could be saved by minifying CSS.

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

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

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.

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

Your largest element takes 90.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WHAT CHEFS WANT Your trusted partners for chef-curated ingr…”.

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

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

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

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

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

1 image 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' tap response (inp) went from 121 ms to 126 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 27.1 MB in 159 requests on a phone: images 22.6 MB (41), scripts 2.8 MB (53) and other files 724 KiB (12). Under 2 MB keeps phones on slow connections fast.

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

6 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

Elements must only use permitted ARIA attributes: 26 elements on the page fail this check, rated serious by axe-core.

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

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

All page content should be contained by landmarks: 55 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.

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

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

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

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

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

There are 6 <h1> headlines (“WHAT CHEFS WANT”, “WHAT CHEFS WANT” and “WHAT CHEFS WANT”). One clear main headline is easier for people and search engines.

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

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

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

The homepage links to 121 pages on whatchefswant.com and 5 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.whatchefswant.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.whatchefswant.com/seafood, https://www.whatchefswant.com/broadline-backup, https://www.whatchefswant.com/dairy and https://www.whatchefswant.com/to-go-and-kitchen-essentials use the same meta description. A description written for each page earns more clicks.

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

Large scripts ship without source maps.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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