Programmable

Website review, no card needed

kitukali.com logo

kitukali.com website review

Visit site (opens in a new tab)Reviewed 6 November 202628 issues · 78 checks

This review found 28 issues worth fixing on kitukali.com, 7 of them high impact, across 78 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

Site score

86B

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.3 s1.8 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.1 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20261.9 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
179 ms140 msMay 16Oct 31144 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026172 ms
May 23, 2026165 ms
May 30, 2026163 ms
Jun 6, 2026167 ms
Jun 13, 2026170 ms
Jun 20, 2026160 ms
Jun 27, 2026153 ms
Jul 4, 2026154 ms
Jul 11, 2026155 ms
Jul 18, 2026166 ms
Jul 25, 2026169 ms
Aug 1, 2026173 ms
Aug 8, 2026174 ms
Aug 15, 2026163 ms
Aug 22, 2026165 ms
Aug 29, 2026153 ms
Sep 5, 2026148 ms
Sep 12, 2026147 ms
Sep 19, 2026145 ms
Sep 26, 2026153 ms
Oct 3, 2026162 ms
Oct 10, 2026174 ms
Oct 17, 2026165 ms
Oct 24, 2026168 ms
Oct 31, 2026144 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

www.kitukali.com (opens in a new tab)
Full-page screenshot of kitukali.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kitukali.com at 1.0 s1.0 s
  2. kitukali.com at 1.9 s1.9 s
  3. kitukali.com at 2.9 s2.9 s
  4. kitukali.com at 3.8 s3.8 s
  5. kitukali.com at 4.8 s4.8 s
  6. kitukali.com at 5.7 s5.7 s
  7. kitukali.com at 6.7 s6.7 s
  8. kitukali.com at 7.7 s7.7 s

Speed

9 to fix72

  • Render-blocking requests

    1.2 s

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

  • Improve image delivery

    500 ms · 1.0 MB

    23 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Mobile performance score: 72

    72/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and ContentSquare and others), adding 1.4 MB and 635 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 507 KiB

    About 507 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.

  • Use efficient cache lifetimes

    360 KiB

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

  • Shopify adds 214 ms

    214 ms

    Shopify costs a phone 214 ms of main-thread work and 569 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.

  • Main-thread work: 2.6 s

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

  • Google Tag Manager adds 140 ms

    140 ms

    Google Tag Manager costs a phone 140 ms of main-thread work and 301 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 CSS

    100 ms · 39 KiB

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

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    42 KiB

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

  • Minify JavaScript

    18 KiB

    18 KiB could be saved by minifying JavaScript.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

  • 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: 8 ms

    8 ms

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

Core Web Vitals

7 to fix67

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

  • Largest Contentful Paint: 8.6 s

    8.6 s

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

  • Time to Interactive: 14.2 s

    14.2 s

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user FCP: 1.9 s

    1.9 s

    Real visitors see the first content after 1.9 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.

  • Speed Index: 4.4 s

    4.4 s

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

  • Tap response (INP) held steady for real visitors

    -7%

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

5 checks passed

  • Real-user INP: 151 ms

    151 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Total Blocking Time: 75 ms

    75 ms

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

  • Cumulative Layout Shift: 0.007

    0.007

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

Images and page weight

2 to fix64

  • Page weight: 4.5 MB in 331 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 331 requests on a phone: images 1.4 MB (26), scripts 1.4 MB (98) and other files 1.4 MB (188). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Urban_Polo_Collection_Collage-banner.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).

  • 1 image in older formats

    1 image (72 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 1.3 g of CO₂ per visit

    1.27 g

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

1 checks passed

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 8995

  • 27 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • Headings skip levels

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

1 checks passed

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

SEO

1 to fixGoogle 9297

  • No social preview image

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

  • 62 internal links, 0 external

    The homepage links to 62 pages on kitukali.com and 0 external pages.

7 checks passed

  • Meta description: 157 characters

    Your meta description is 157 characters: “Explore handmade, colourful shoes and premium Kenyan apparel at Kitu Kali Africa. Elevate your style with our exclusive…”.

  • One H1 headline

    Your main headline reads: “KITU KALI. BEI POA.”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Vibrant African Fashion Brand, Made in Kenya – Kitu Kali Africa”.

  • Canonical URL set

    The canonical URL is https://www.kitukali.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.kitukali.com/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

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

  • llms.txt published

    The site publishes https://www.kitukali.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix83

  • 5 pages without a meta description

    https://www.kitukali.com/collections/black-friday-ts-collection, https://www.kitukali.com/collections/black-friday-hoodies-collection, https://www.kitukali.com/collections/black-friday-sale-collection, https://www.kitukali.com/pages/our-stores and https://www.kitukali.com/pages/corporate have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://www.kitukali.com/collections/black-friday-ts-collection/products/ladies-graphic-ts-baby-pink-with-nairobi-vibes-chui and https://www.kitukali.com/collections/black-friday-ts-collection/products/ladies-graphic-ts-baby-pink-with-kenya-shield use the same meta description. A description written for each page earns more clicks.

  • 8 links to non-canonical URLs

    Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.kitukali.com/collections/black-friday-ts-collection/products/ladies-graphic-ts-baby-pink-with-nairobi-vibes-chui, whose canonical is https://www.kitukali.com/products/ladies-graphic-ts-baby-pink-with-nairobi-vibes-chui. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages without an H1

    https://www.kitukali.com/collections/black-friday-ts-collection, https://www.kitukali.com/collections/black-friday-hoodies-collection, https://www.kitukali.com/collections/black-friday-sale-collection, https://www.kitukali.com/pages/our-stores and https://www.kitukali.com/pages/corporate 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 24 found) and read each the way a search engine does.

4 checks passed

  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    43 of 45 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92

  • No direct contact details

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

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

    The homepage carries about 610 words of visible text.

5 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP THE SALE →” and “START SHOPPING”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “SHOP THE SALE →”, “Shop before it's too late” and “Shop tees”.

  • 12 short forms

    12 short forms (1 field at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager, Hotjar and LinkedIn Insight.

Privacy and tracking

1 to fix

  • 5 trackers load before any consent

    5

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

  • 21 cookies set on arrival

    21

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

  • 33 other companies contacted

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

Apps on your store

Your storefront loads 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Drip Email Marketing Popup · Hulk Form Builder · Judge Me Reviews · Frequently Bought · Parkour Tiktok Pixel · Swym Wishlist Plus · Whatsapp Chat Button · chimpstatic.com · amazonaws.com · azureedge.net

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Hotjar
Hosting
Shopify

Company

Headquarters
London

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on kitukali.com, including 16 speed issues, 1 SEO issue and 1 conversion gap. 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