chiveuk.com website review

The page goes through 2 redirects before it starts loading, costing about 16.1 s. Link and advertise the final URL directly.

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

Your mobile performance score is 46. 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, Facebook and Shopify and others), adding 1.1 MB and 789 ms of main-thread time.

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

The HTML itself could arrive about 400 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

12 images could be 312 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

18 KiB JavaScript is shipped twice across bundles.

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

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

5 KiB could be saved by minifying JavaScript.

Your largest element takes 20.0 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 25.3 s. Good is under 3.8 s.

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

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

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

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 23.3 MB in 408 requests on a phone: media 17.3 MB (3), scripts 2.4 MB (105) and images 1.6 MB (44). Under 2 MB keeps phones on slow connections fast.

691728f92d314314a7cf0271c48cf557.thumbnail.0000000000.jpg 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).

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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.

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

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

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

The homepage links to 81 pages on chiveuk.com and 11 external pages.

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.

/collections/ceramic-flowers-english-garden-collection/products/ceramic-flower-wall-art-teal-flower and /collections/ceramic-flowers-english-garden-collection/products/ceramic-flower-wall-art-teal-lotus use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example /collections/ceramic-flowers-english-garden-collection/products/ceramic-flower-wall-art-teal-flower, whose canonical is /products/ceramic-flower-wall-art-teal-flower. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/collections/ceramic-flowers, /collections/ceramic-flowers-english-garden-collection, /collections/ceramic-flowers-france-collection, /collections/ceramic-flowers-japan-collection, /collections/ceramic-flowers-coastal-collection and /collections/ceramic-flower-curated-sets have no <h1> headline, so visitors and search engines get no clear main topic.

/products/pooley-modern-bud-vase-for-flowers has 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 15 pages linked from your homepage (of 41 found) and read each the way a search engine does.

3 errors were logged to the browser console while the page loaded, for example “AbortError: The play() request was interrupted by a call to pause(). https://goo.gl/LdLk22”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

chiveuk.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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

DMARC is set to p=none, so mail pretending to be chiveuk.com is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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