boulkitchen.co.uk website review

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

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

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

7 third-party services load with your homepage (Squarespace, Google CDN and Facebook and others), adding 3.4 MB and 1.4 s of main-thread time.

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

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

Squarespace costs a phone 690 ms of main-thread work and 1.1 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.

Google CDN costs a phone 422 ms of main-thread work and 743 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 2.9 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

squarespace-cdn.com costs a phone 0 ms of main-thread work and 1.2 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.

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

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

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 13.1 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 19.9 s. Good is under 3.8 s.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.9 MB in 64 requests on a phone: scripts 1.9 MB (33), images 1.2 MB (8) and other files 487 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Your title is only 4 characters: “Boul”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/625ed1d4dda74648b8e…”.

The homepage links to 37 pages on boulkitchen.co.uk and 12 external pages.

Your Organization JSON-LD is missing name, url, logo, 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 https://www.boulkitchen.co.uk/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 https://www.boulkitchen.co.uk/shop, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.boulkitchen.co.uk/shop-tTVF0, https://www.boulkitchen.co.uk/contact, https://www.boulkitchen.co.uk/weddings, https://www.boulkitchen.co.uk/gallery, https://www.boulkitchen.co.uk/faq and https://www.boulkitchen.co.uk/terms-of-service-1 and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.boulkitchen.co.uk/shop-tTVF0/babka-treats-platters, whose canonical is https://www.boulkitchen.co.uk/shop-tTVF0. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.boulkitchen.co.uk/shop-tTVF0, https://www.boulkitchen.co.uk/about, https://www.boulkitchen.co.uk/contact, https://www.boulkitchen.co.uk/weddings, https://www.boulkitchen.co.uk/gallery and https://www.boulkitchen.co.uk/faq and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.boulkitchen.co.uk/contact, https://www.boulkitchen.co.uk/weddings, https://www.boulkitchen.co.uk/gallery and https://www.boulkitchen.co.uk/sustainability have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

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

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 100 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.

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.

Before a visitor clicks anything, the page loads Meta Pixel (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 4 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.