zapaka.co.uk website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

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

• Real-user LCP: 2.6 s

  2.6 s

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

• Largest content (LCP) held steady for real visitors

  +5%

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

• Page weight: 7.4 MB

  7.4 MB

  Your homepage downloads 7.4 MB on a phone, 4.7 MB of it images (64%). Under 2 MB keeps phones on slow connections fast.

• 15 images far larger than shown

  1.9 MB

  15 images are downloaded at several times the size a phone draws them, for example guest_banner.jpg at 1,500 px wide, shown at 370 px. Resized copies would save about 1.9 MB.

  Elements (5)

• 14 images below the first screen load straight away

  14 images further down the page (2.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (5)

• About 2.1 g of CO₂ per visit

  2.09 g

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

• Invalid ARIA attributes

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

  Elements (2)

• Certain ARIA roles must contain particular children (2 elements)

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

  Elements (2)

• ARIA attributes must conform to valid values (1 element)

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

  Elements (1)

• 1 button without a name

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

  Elements (1)

• Unlabelled dropdowns

  1 dropdown has no label.

  Elements (1)

• Hidden but focusable

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

  Elements (3)

• 4 text elements with low contrast

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

  Elements (3)

• Interactive controls must not be nested (3 elements)

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

  Elements (3)

• ARIA input fields must have an accessible name (2 elements)

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

  Elements (2)

• 2 tap targets too small

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

  Elements (2)

• <html> element must have a lang attribute (1 element)

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

  Elements (1)

• 97 images without alt text

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

  View sourceElements (3)

• All page content should be contained by landmarks (22 elements)

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

  Elements (3)

• Page should contain a level-one heading (1 element)

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

  Elements (1)

• 20 links without text

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

  Elements (3)

• 4 form fields without a label

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

  View source

• No page language

  The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  View source

• Elements marked as presentational should be consistently ignored (2 elements)

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

  Elements (2)

• Headings skip levels

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

  View sourceElements (1)

• Title is long (73 characters)

  Your title is 73 characters, so Google will cut it off around 60: “Women's Dresses Online - Prom & Bridesmaid & 1920s Dresses UK – ZAPAKA UK”.

  View source

• No structured data

  No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

• Meta description is long (223 characters)

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

  View source

• No social preview image

  No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  View source

• No X (Twitter) card tag

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

• 431 internal links, 28 external

  The homepage links to 431 pages on zapaka.co.uk and 28 external pages.

• No Organization structured data

  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.

• 8 pages without a meta description

  https://zapaka.co.uk/collections/new-arrivals, https://zapaka.co.uk/collections/bridal-dresses, https://zapaka.co.uk/collections/2020-mother-of-bride-dresses, https://zapaka.co.uk/collections/maxi-dresses, https://zapaka.co.uk/collections/midi-dresses and https://zapaka.co.uk/collections/mini-dresses and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (8)

• 11 pages without an H1

  https://zapaka.co.uk/collections/new-arrivals, https://zapaka.co.uk/collections/prom-dress, https://zapaka.co.uk/collections/bridesmaid-dresses, https://zapaka.co.uk/collections/bridal-dresses, https://zapaka.co.uk/collections/2020-mother-of-bride-dresses and https://zapaka.co.uk/collections/maxi-dresses and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

• 15 internal pages checked

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

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

• No risk reducer

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

• About 1,289 words of copy

  The homepage carries about 1,289 words of visible text.

• 6 trackers load before any consent

  6

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag and 1 more (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.

• 18 cookies set on arrival

  18

  Opening the homepage sets 18 cookies, 2 of them by other companies (measured from a US location before any click).

• No consent tool detected

  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.

• 43 other companies contacted

  Loading the homepage contacts 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.