Website review, no card needed

thechefstoreuk.com logo

thechefstoreuk.com website review

Visit site (opens in a new tab)Reviewed 9 November 202622 issues · 71 checks

This review found 22 issues worth fixing on thechefstoreuk.com, 6 of them high impact, across 71 checks. The most urgent: 6 text elements with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.1 s738 msMay 23Nov 7781 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026915 ms
May 30, 2026911 ms
Jun 6, 2026949 ms
Jun 13, 2026934 ms
Jun 20, 2026937 ms
Jun 27, 2026930 ms
Jul 4, 2026953 ms
Jul 11, 2026964 ms
Jul 18, 2026981 ms
Aug 1, 2026976 ms
Aug 15, 20261.0 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.0 s
Sep 26, 20261.0 s
Oct 3, 2026994 ms
Oct 10, 2026931 ms
Oct 17, 2026846 ms
Oct 24, 2026905 ms
Oct 31, 2026780 ms
Nov 7, 2026781 ms
Real-visitor tap response (INP)75th percentile, phones
99 ms76 msMay 23Nov 781 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202686 ms
May 30, 202686 ms
Jun 6, 202694 ms
Jun 13, 202695 ms
Jun 20, 202696 ms
Jun 27, 202688 ms
Jul 11, 202696 ms
Aug 15, 202687 ms
Aug 22, 202684 ms
Aug 29, 202684 ms
Sep 5, 202686 ms
Sep 12, 202685 ms
Sep 19, 202685 ms
Sep 26, 202684 ms
Oct 3, 202688 ms
Oct 10, 202687 ms
Oct 17, 202682 ms
Oct 24, 202682 ms
Oct 31, 202679 ms
Nov 7, 202681 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of thechefstoreuk.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thechefstoreuk.com at 0.4 s0.4 s
  2. thechefstoreuk.com at 0.8 s0.8 s
  3. thechefstoreuk.com at 1.1 s1.1 s
  4. thechefstoreuk.com at 1.5 s1.5 s
  5. thechefstoreuk.com at 1.9 s1.9 s
  6. thechefstoreuk.com at 2.3 s2.3 s
  7. thechefstoreuk.com at 2.6 s2.6 s
  8. thechefstoreuk.com at 3.0 s3.0 s

Speed

2 to fix70
  • Mobile performance score: 70

    70/100

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

  • Improve image delivery

    150 ms · 291 KiB

    8 images could be 291 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Shopify, av-northern-apps.com and shop.app), adding 269 KiB and 39 ms of main-thread time.

  • Use efficient cache lifetimes

    21 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 checks passed
  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 212 ms of it running JavaScript. That is comfortably low.

  • Server response: 6 ms

    6 ms

    Your server sent the HTML in 6 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 7.5 s

    7.5 s

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

  • Time to Interactive: 7.7 s

    7.7 s

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

  • Speed Index: 5.5 s

    5.5 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • Tap response (INP) held steady for real visitors

    -7%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 0.8 s

    0.8 s

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

  • Real-user INP: 81 ms

    81 ms

    Real visitors wait 81 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.5 s

    0.5 s

    Real visitors see the first content after 0.5 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 315 ms

    315 ms

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

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 203 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 203 requests on a phone: images 818 KiB (10), other files 781 KiB (100) and scripts 286 KiB (61). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.59 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 9797
  • 6 text elements with low contrast

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

  • All page content should be contained by landmarks (4 elements)

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

2 checks passed
  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10088
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Wholesale Food Suppliers UK | The Chef Store UK - Nationwide Delivery”.

  • One H1 headline

    Your <h1> is empty.

  • 79 internal links, 4 external

    The homepage links to 79 pages on thechefstoreuk.com and 4 external pages.

6 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Leading wholesale food suppliers UK. Premium ambient ingredients, pantry staples & bulk supplies for chefs, caterers & …”.

  • Canonical URL set

    The canonical URL is https://www.thechefstoreuk.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.thechefstoreuk.com/sitemap.xml.

AI search readiness

100
3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • llms.txt published

    The site publishes https://www.thechefstoreuk.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix67
  • 1 page without a title

    https://www.thechefstoreuk.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.thechefstoreuk.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.thechefstoreuk.com/collections/all and https://www.thechefstoreuk.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages share a meta description

    https://www.thechefstoreuk.com/collections/flour, https://www.thechefstoreuk.com/collections/tracklements, https://www.thechefstoreuk.com/collections/tinned-fruit, https://www.thechefstoreuk.com/collections/canned-tinned-packaged-foods, https://www.thechefstoreuk.com/collections/herbs and https://www.thechefstoreuk.com/collections/pasta and 2 others use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.thechefstoreuk.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.thechefstoreuk.com/customer_authentication/redirect took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

Best practices

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    10 of 10 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix56
  • No call to action on the first screen

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

  • No social proof

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

  • Local business without LocalBusiness data

    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.

  • No analytics detected

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

  • Only about 125 words

    The homepage has only about 125 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

  • Phone number is not tap-to-call

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

  • No map or directions link

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact information”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    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.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 8 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at thechefstoreuk.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

No apps were seen in the code your storefront loads.

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on thechefstoreuk.com, including 6 speed issues, 2 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25