Website review, no card needed

zarela.co.uk logo

zarela.co.uk website review

Visit site (opens in a new tab)Reviewed 17 November 202636 issues · 84 checks

This review found 36 issues worth fixing on zarela.co.uk, 6 of them high impact, across 84 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
887 ms732 msMay 30Nov 14802 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026841 ms
Jun 6, 2026819 ms
Jun 13, 2026808 ms
Jun 20, 2026799 ms
Jun 27, 2026800 ms
Jul 4, 2026795 ms
Jul 11, 2026801 ms
Jul 18, 2026782 ms
Jul 25, 2026782 ms
Aug 1, 2026781 ms
Aug 8, 2026750 ms
Aug 15, 2026786 ms
Aug 22, 2026826 ms
Aug 29, 2026861 ms
Sep 5, 2026869 ms
Sep 12, 2026847 ms
Sep 19, 2026863 ms
Sep 26, 2026840 ms
Oct 3, 2026833 ms
Oct 10, 2026838 ms
Oct 17, 2026795 ms
Oct 24, 2026787 ms
Oct 31, 2026775 ms
Nov 7, 2026774 ms
Nov 14, 2026802 ms
Real-visitor tap response (INP)75th percentile, phones
90 ms75 msMay 30Nov 1481 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202687 ms
Jun 6, 202686 ms
Jun 13, 202686 ms
Jun 20, 202683 ms
Jun 27, 202681 ms
Jul 4, 202679 ms
Jul 11, 202678 ms
Jul 18, 202677 ms
Jul 25, 202679 ms
Aug 1, 202682 ms
Aug 8, 202680 ms
Aug 15, 202684 ms
Aug 22, 202683 ms
Aug 29, 202683 ms
Sep 5, 202683 ms
Sep 12, 202681 ms
Sep 19, 202686 ms
Sep 26, 202685 ms
Oct 3, 202688 ms
Oct 10, 202688 ms
Oct 17, 202685 ms
Oct 24, 202685 ms
Oct 31, 202681 ms
Nov 7, 202681 ms
Nov 14, 202681 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of zarela.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. zarela.co.uk at 0.4 s0.4 s
  2. zarela.co.uk at 0.8 s0.8 s
  3. zarela.co.uk at 1.1 s1.1 s
  4. zarela.co.uk at 1.5 s1.5 s
  5. zarela.co.uk at 1.9 s1.9 s
  6. zarela.co.uk at 2.3 s2.3 s
  7. zarela.co.uk at 2.6 s2.6 s
  8. zarela.co.uk at 3.0 s3.0 s

Speed

7 to fix70
  • Render-blocking requests

    1.7 s

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

  • Mobile performance score: 70

    70/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Google CDN and Other Google APIs/SDKs and others), adding 1.0 MB and 322 ms of main-thread time.

  • Reduce unused JavaScript

    371 KiB

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

  • Improve image delivery

    300 ms · 46 KiB

    1 image could be 46 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 114 ms

    114 ms

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

  • Google CDN adds 97 ms

    97 ms

    Google CDN costs a phone 97 ms of main-thread work and 296 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.

  • Use efficient cache lifetimes

    250 ms · 220 KiB

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

  • Reduce unused CSS

    130 ms · 27 KiB

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

  • 3 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Chained critical requests

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

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 374 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

    Your server sent the HTML in 1 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix50
  • Fails Core Web Vitals for real visitors

    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.

  • Time to Interactive: 8.8 s

    8.8 s

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

  • Cumulative Layout Shift: 0.299

    0.299

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

  • Real-user CLS: 0.22

    0.22

    For real visitors the layout shifts by 0.22 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 3.8 s

    3.8 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Speed Index: 3.8 s

    3.8 s

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

  • 15 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

4 checks passed
  • Real-user LCP: 0.7 s

    0.7 s

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

  • Real-user FCP: 0.6 s

    0.6 s

    Real visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 361 ms

    361 ms

    Real visitors wait 361 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 51 ms

    51 ms

    Scripts block the page for only 51 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix68
  • Page weight: 2.7 MB in 58 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 58 requests on a phone: images 1.6 MB (27), scripts 847 KiB (17) and fonts 173 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    90 KiB

    2 images are downloaded at several times the size a phone draws them, for example banner_mid-1300x460.webp at 1,300 px wide, shown at 390 px. Resized copies would save about 90 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (374 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.76 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 9895
  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

  • 5 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9276
  • Title is short (12 characters)

    Your title is only 12 characters: “Zarela.co.uk”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 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 short (12 characters)

    Your meta description is only 12 characters: “Zarela.co.uk”. 70 to 160 characters is enough to sell the click.

  • 4 H1 headlines

    There are 4 <h1> headlines (“Zarela Yarns”, “Wholesale and discounted rates on Zarela products” and “Zarela Luxurious Baby Alpaca”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

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

  • 138 internal links, 4 external

    The homepage links to 138 pages on zarela.co.uk and 4 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://zarela.co.uk/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://zarela.co.uk/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://zarela.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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (839 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix75
  • 2 pages without a title

    https://zarela.co.uk/pom-pom-pompon-pompom-knitting-yarn/rico-creative-pompon-pom-pom-yarn and https://zarela.co.uk/pom-pom-pompon-pompom-knitting-yarn/sirdar-snuggly-sweetie-200g-dk have no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://zarela.co.uk/contact has no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 links to non-canonical URLs

    Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://zarela.co.uk/pom-pom-pompon-pompom-knitting-yarn/rico-creative-pompon-pom-pom-yarn, whose canonical is https://zarela.co.uk/rico-creative-pompon-pom-pom-yarn. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9287
  • 6 small tap targets

    6 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://analytics.google.com/g/collect?v=2&tid=G-9S6VT7PY5P&gtm=45je6bd1h1v9121325540za20gxf1&_p=1794901…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 390 words of copy

    The homepage carries about 390 words of visible text.

  • Urgency cues

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “contact-us” and “CONTACT”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Register”, “Contact” and “Contact us”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies (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.

  • 10 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at zarela.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics
Hosting
Krystal Hosting Ltd

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on zarela.co.uk, including 15 speed issues, 5 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25