chicsew.co.uk website review

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

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

48 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

Shopify costs a phone 223 ms of main-thread work and 770 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.7 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

5 third-party services load with your homepage (Shopify, Google CDN and MailMunch and others), adding 863 KiB and 262 ms of main-thread time.

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

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

13 KiB could be saved by minifying CSS.

11 KiB could be saved by minifying JavaScript.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

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

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.

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

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

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

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

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

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

Your homepage downloads 5.2 MB in 178 requests on a phone: images 4.2 MB (101), scripts 524 KiB (51) and HTML 158 KiB (2). Under 2 MB keeps phones on slow connections fast.

17 images are downloaded at several times the size a phone draws them, for example sequin-fabric.jpg at 600 px wide, shown at 70 px. Resized copies would save about 1.5 MB.

97A1F7B9527F1F90032F8BED9E28140E.png 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).

4 images (447 KiB) are 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 1.48 g of CO₂e: 177.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 buttons have no accessible name, so screen readers announce just “button”.

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

1 dropdown has no label.

Interactive controls must not be nested: 10 elements on the page fail this check, rated serious by axe-core.

ARIA input fields must have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.

5 elements hidden from screen readers can still receive keyboard focus.

2 tap targets are too small or too close together to hit reliably with a finger.

ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

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

There are 2 <h1> headlines (“Shop Chic, Silky Satin Bridesmaid Dresses Online” and “Social Media”). One clear main headline is easier for people and search engines.

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

16 links have no real href, so search engines can't follow them.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 569 pages on chicsew.co.uk and 11 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://chicsew.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://chicsew.co.uk/pages/wishlists, which answers with an error. Visitors hit a dead end and search engines drop it.

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

3 images failed to load on a phone, for example https://chicsew.co.uk/cdn/shop/files/floral%20velvet-fabric.jpg?v=31227.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“`<source src>` with a `<picture>` parent is invalid and therefore ignored. Please use `<source srcs…”).

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

13 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

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 1,626 words of visible text.

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