Website review, no card needed

kabooki.com logo

kabooki.com website review

Visit site (opens in a new tab)Reviewed 5 November 202634 issues · 74 checks

This review found 34 issues worth fixing on kabooki.com, 12 of them high impact, across 74 checks. The most urgent: mobile performance score: 47. 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
3.0 s737 msMay 16Oct 312.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.6 s
Jun 6, 20262.4 s
Jun 13, 20262.5 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.6 s
Jul 11, 20262.5 s
Jul 18, 20261.7 s
Jul 25, 20261.2 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 2026999 ms
Aug 22, 20261.0 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.2 s
Oct 10, 20261.5 s
Oct 17, 20261.8 s
Oct 24, 20262.1 s
Oct 31, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
159 ms78 msMay 16Oct 31150 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202697 ms
May 23, 202693 ms
May 30, 202697 ms
Jun 6, 2026112 ms
Jun 13, 2026120 ms
Jun 20, 2026132 ms
Jun 27, 2026129 ms
Jul 4, 2026124 ms
Jul 11, 2026116 ms
Jul 18, 202698 ms
Jul 25, 202697 ms
Aug 1, 202695 ms
Aug 8, 2026103 ms
Aug 15, 2026113 ms
Aug 22, 2026114 ms
Aug 29, 2026109 ms
Sep 5, 2026102 ms
Sep 12, 202690 ms
Sep 19, 202687 ms
Sep 26, 202691 ms
Oct 3, 202690 ms
Oct 10, 202696 ms
Oct 17, 2026109 ms
Oct 24, 2026120 ms
Oct 31, 2026150 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 kabooki.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kabooki.com at 0.9 s0.9 s
  2. kabooki.com at 1.8 s1.8 s
  3. kabooki.com at 2.7 s2.7 s
  4. kabooki.com at 3.6 s3.6 s
  5. kabooki.com at 4.5 s4.5 s
  6. kabooki.com at 5.4 s5.4 s
  7. kabooki.com at 6.3 s6.3 s
  8. kabooki.com at 7.2 s7.2 s

Speed

9 to fix47
  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.0 s

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

  • 4,336 HTML elements

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

  • Use efficient cache lifetimes

    750 ms · 658 KiB

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

  • Render-blocking requests

    900 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 900 ms.

  • Reduce unused JavaScript

    600 ms · 289 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Cookiebot, Facebook and Google Tag Manager and others), adding 553 KiB and 576 ms of main-thread time.

  • Improve image delivery

    475 KiB

    8 images could be 475 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    300 ms · 38 KiB

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

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    67 KiB

    Polyfills for old browsers add 67 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: 237 ms

    237 ms

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

Core Web Vitals

13 to fix0
  • 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: 6.6 s

    6.6 s

    Your largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Child in a beige winter jacket and black LEGO® NINJAGO® hat…”.

  • Cumulative Layout Shift: 0.42

    0.42

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

  • Time to Interactive: 10.6 s

    10.6 s

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

  • Speed Index: 5.9 s

    5.9 s

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

  • Real-user LCP: 3.4 s

    3.4 s

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

  • Real-user INP: 302 ms

    302 ms

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

  • Real-user CLS: 0.12

    0.12

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

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

    +42%

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

  • Largest content (LCP) got 65% slower for real visitors

    +65%

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • Total Blocking Time: 275 ms

    275 ms

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

1 checks passed
  • 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 fix75
  • Page weight: 2.7 MB in 151 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 151 requests on a phone: images 1.3 MB (61), scripts 1.0 MB (54) and fonts 152 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    323 KiB

    4 images are downloaded at several times the size a phone draws them, for example fit-1000x1400x75.webp at 973 px wide, shown at 195 px. Resized copies would save about 323 KiB.

  • 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.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

Accessibility

7 to fixGoogle 9089
  • 59 text elements with low contrast

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

  • Scrollable region must have keyboard access (3 elements)

    Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

  • 3 images without alt text

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

  • [aria-*] attributes do not have valid values

    [aria-*] attributes do not have valid values (1 element).

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9294
  • No structured data

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 580 internal links, 14 external

    The homepage links to 580 pages on kabooki.com and 14 external pages.

7 checks passed
  • Meta description: 125 characters

    Your meta description is 125 characters: “Shop LEGO® kids clothing at KABOOKI. Discover durable, playful styles designed for comfort, quality, and everyday adven…”.

  • One H1 headline

    Your main headline reads: “New styles. Fresh adventures.”.

  • Title: 38 characters

    Your title is a healthy 38 characters: “LEGO® kidswear | KABOOKI Official Shop”.

  • Canonical URL set

    The canonical URL is https://kabooki.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://kabooki.com/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://kabooki.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,706 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    198 of 200 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop news” and “SHOP NEWS”.

  • 25 calls to action

    The homepage has 25 calls to action, for example “Cancel your order”, “Continue to the other shop” and “Shop news”.

  • 7 short forms

    7 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 43 testimonial or review blocks, 11 customer or partner logos, a star rating and 26 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 cookies (measured from a US location before any click).

  • 16 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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

Upkeep, stack and company

Stack

CMS
Shoporama
Analytics
Google Tag Manager
Hosting
Dlx As Dlx A/S

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on kabooki.com, including 22 speed issues and 2 SEO issues. 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