flowerstation.co.uk website review

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

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

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

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

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

Shopify costs a phone 58 ms of main-thread work and 364 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.

8 third-party services load with your homepage (Klaviyo, Shopify and lipscore.com and others), adding 827 KiB and 187 ms of main-thread time.

About 195 KiB of JavaScript is downloaded but never used on this page.

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

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

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

6 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

Your homepage downloads 3.3 MB in 397 requests on a phone: images 984 KiB (53), other files 945 KiB (166) and scripts 927 KiB (108). Under 2 MB keeps phones on slow connections fast.

pure-bliss-shadow__73344.1691515158.800.800__82494.169151520 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).

1 image (35 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is 78 characters, so Google will cut it off around 60: “Flower Delivery London | Flower Shop Near Me | Florist London – Flower Station”.

Structured data found (Organization, Store and WebSite) but with 3 problems, for example “WebSite: url is not an absolute URL ("www.flowerstation.co.uk")”.

The homepage links to 396 pages on flowerstation.co.uk and 47 external pages.

https://www.flowerstation.co.uk/policies/shipping-policy, https://www.flowerstation.co.uk/pages/earn-rewards-at-flower-station and https://www.flowerstation.co.uk/pages/our-shops have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.flowerstation.co.uk/collections/all-flowers, https://www.flowerstation.co.uk/pages/earn-rewards-at-flower-station, https://www.flowerstation.co.uk/collections/autumn-flowers, https://www.flowerstation.co.uk/collections/birthday, https://www.flowerstation.co.uk/collections/delivery-thank-you-floral-gifts and https://www.flowerstation.co.uk/collections/delivery-anniversary-day-floral-gifts and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=17fce222-1d5f-4aba-a94e-d38634697ba7&referrer=&landingpage=https%3A%2F%2Fwww.flowerstation.co.uk%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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.

The homepage carries about 878 words of visible text.

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

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