kitchenhub.com website review

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

39 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and cloudflarestorage.com and others), adding 3.1 MB and 2.0 s of main-thread time.

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

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

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

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

Google CDN costs a phone 413 ms of main-thread work and 746 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.

cloudflarestorage.com costs a phone 321 ms of main-thread work and 642 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.

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

Facebook costs a phone 269 ms of main-thread work and 222 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.

Google Maps costs a phone 134 ms of main-thread work and 346 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.

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

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

Desktop scores 62 but mobile only 37. A gap that wide usually means heavy scripts and images that hit phones hardest.

6 KiB JavaScript is shipped twice across bundles.

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.

Your largest element takes 22.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A spread of dishes from the hall”.

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

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

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

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

50 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-10, real Chrome visitors' tap response (inp) went from 214 ms to 203 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.8 MB in 108 requests on a phone: scripts 2.9 MB (51), images 1.2 MB (34) and other files 382 KiB (11). Under 2 MB keeps phones on slow connections fast.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Your title is only 26 characters: “Kitchen Hub | Landing page”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 101 pages on kitchenhub.com and 9 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.

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.

Your homepage links to /home, /restaurants, /in-the-news, /newsletter, /faq and /privacy-policy and 5 others, which answer with an error. Visitors hit a dead end and search engines drop them.

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

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 503 ()”.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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

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.