Website review, no card needed

shopzetu.com logo

shopzetu.com website review

Visit site (opens in a new tab)Reviewed 7 November 202639 issues · 84 checks

This review found 39 issues worth fixing on shopzetu.com, 11 of them high impact, across 84 checks. The most urgent: fails Core Web Vitals for real visitors. 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
4.9 s3.4 sMay 16Oct 313.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.9 s
May 23, 20263.8 s
May 30, 20263.6 s
Jun 6, 20263.6 s
Jun 13, 20263.7 s
Jun 20, 20264.1 s
Jun 27, 20264.5 s
Jul 4, 20264.7 s
Jul 11, 20264.7 s
Jul 18, 20264.7 s
Jul 25, 20264.3 s
Aug 1, 20264.1 s
Aug 8, 20264.0 s
Aug 15, 20264.0 s
Aug 22, 20264.0 s
Aug 29, 20263.9 s
Sep 5, 20263.9 s
Sep 12, 20264.0 s
Sep 19, 20264.1 s
Sep 26, 20264.2 s
Oct 3, 20264.3 s
Oct 10, 20264.3 s
Oct 17, 20264.3 s
Oct 24, 20264.0 s
Oct 31, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
286 ms150 msMay 16Oct 31270 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026174 ms
May 23, 2026173 ms
May 30, 2026166 ms
Jun 6, 2026169 ms
Jun 13, 2026179 ms
Jun 20, 2026194 ms
Jun 27, 2026219 ms
Jul 4, 2026228 ms
Jul 11, 2026223 ms
Jul 18, 2026219 ms
Jul 25, 2026199 ms
Aug 1, 2026193 ms
Aug 8, 2026199 ms
Aug 15, 2026202 ms
Aug 22, 2026209 ms
Aug 29, 2026210 ms
Sep 5, 2026215 ms
Sep 12, 2026228 ms
Sep 19, 2026233 ms
Sep 26, 2026239 ms
Oct 3, 2026240 ms
Oct 10, 2026239 ms
Oct 17, 2026244 ms
Oct 24, 2026257 ms
Oct 31, 2026270 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 shopzetu.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. shopzetu.com at 0.9 s0.9 s
  2. shopzetu.com at 1.9 s1.9 s
  3. shopzetu.com at 2.8 s2.8 s
  4. shopzetu.com at 3.8 s3.8 s
  5. shopzetu.com at 4.7 s4.7 s
  6. shopzetu.com at 5.7 s5.7 s
  7. shopzetu.com at 6.6 s6.6 s
  8. shopzetu.com at 7.6 s7.6 s

Speed

10 to fix62
  • 3,410 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and Facebook and others), adding 2.6 MB and 1.3 s of main-thread time.

  • Mobile performance score: 62

    62/100

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

  • Render-blocking requests

    950 ms

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

  • Shopify adds 679 ms

    679 ms

    Shopify costs a phone 679 ms of main-thread work and 1.8 MB 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.

  • Improve image delivery

    150 ms · 315 KiB

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

  • Google Tag Manager adds 386 ms

    386 ms

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

  • Reduce unused JavaScript

    150 ms · 260 KiB

    About 260 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 14 long tasks on the main thread

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

  • Main-thread work: 3.0 s

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

  • Use efficient cache lifetimes

    233 KiB

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

  • Minify JavaScript

    20 KiB

    20 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    14 KiB

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

  • Legacy JavaScript

    13 KiB

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

  • 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 36 ms

    36 ms

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

Core Web Vitals

10 to fix33
  • 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: 12.9 s

    12.9 s

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

  • Largest Contentful Paint: 5.6 s

    5.6 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user INP: 288 ms

    288 ms

    Real visitors wait 288 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 52% slower for real visitors

    +52%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Total Blocking Time: 589 ms

    589 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Largest content (LCP) held steady for real visitors

    0%

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

3 checks passed
  • Real-user CLS: 0.04

    0.04

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

  • Speed Index: 2.8 s

    2.8 s

    Visually, the page fills in at 2.8 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.003

    0.003

    The layout barely moves while loading (CLS 0.003, good is under 0.1).

Images and page weight

2 to fix65
  • 6 images far larger than shown

    672 KiB

    6 images are downloaded at several times the size a phone draws them, for example Jacaranda_Blossoms_and_Joyful_Friends-2.png at 1,254 px wide, shown at 96 px. Resized copies would save about 672 KiB.

  • Page weight: 3.0 MB in 138 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 138 requests on a phone: images 1.6 MB (42), scripts 914 KiB (46) and other files 348 KiB (39). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (49 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.

  • About 0.9 g of CO₂ per visit

    0.86 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

7 to fixGoogle 8289
  • 1 button without a name

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

  • 4 tap targets too small

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

  • 1 text element with low contrast

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • 3 form fields without a label

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 106 images in the HTML carry an alt attribute.

  • 41 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: 41 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10092
  • Meta description is long (173 characters)

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

  • 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.

  • 599 internal links, 4 external

    The homepage links to 599 pages on shopzetu.com and 4 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Shopzetu – Online Fashion Shopping in Kenya”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Shopzetu | Online Fashion Shopping in Kenya”.

  • Canonical URL set

    The canonical URL is https://www.shopzetu.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.shopzetu.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.shopzetu.com/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 (2,005 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix75
  • 1 page without a title

    https://www.shopzetu.com/shop/vivo has no <title>, so Google invents the link text in results.

  • 5 pages without a meta description

    https://www.shopzetu.com/pages/all-our-brands, https://www.shopzetu.com/pages/featured-brands, https://www.shopzetu.com/shop/vivo, https://www.shopzetu.com/shop/safari-by-vivo and https://www.shopzetu.com/collections/zambarau-apparel have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.shopzetu.com/shop/vivo and https://www.shopzetu.com/shop/safari-by-vivo have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://www.shopzetu.com/collections/stylish-sisters, https://www.shopzetu.com/collections/african-yuva, https://www.shopzetu.com/collections/hats-and-more and https://www.shopzetu.com/collections/lizola took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 199 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.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 9293
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message …”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    70 of 74 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “UP TO 50% OFF Shop flash sale”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop the sale”, “SHOP BY BODY FIT” and “Shop the edit”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 9 cookies set on arrival

    9

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 shopzetu.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Hydrogen and Oxygen;Shopify Plus
Hosting
Shopify

Company

Headquarters
Nairobi

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on shopzetu.com, including 20 speed issues, 2 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