Website review, no card needed

kenzzi.com logo

kenzzi.com website review

Visit site (opens in a new tab)Reviewed 5 November 202620 issues · 64 checks

This review found 20 issues worth fixing on kenzzi.com, 4 of them high impact, across 64 checks. The most urgent: no social proof. 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
1.6 s1.1 sMay 16Oct 311.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.3 s
May 30, 20261.2 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.2 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.2 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
101 ms78 msMay 16Oct 3190 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202683 ms
May 23, 202682 ms
May 30, 202681 ms
Jun 6, 202683 ms
Jun 13, 202685 ms
Jun 20, 202686 ms
Jun 27, 202686 ms
Jul 4, 202686 ms
Jul 11, 202686 ms
Jul 18, 202686 ms
Jul 25, 202687 ms
Aug 1, 202693 ms
Aug 8, 202692 ms
Aug 15, 202689 ms
Aug 22, 202689 ms
Aug 29, 202687 ms
Sep 5, 202688 ms
Sep 12, 202694 ms
Sep 19, 202697 ms
Sep 26, 202698 ms
Oct 3, 202697 ms
Oct 10, 202692 ms
Oct 17, 202687 ms
Oct 24, 202688 ms
Oct 31, 202690 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 kenzzi.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kenzzi.com at 0.6 s0.6 s
  2. kenzzi.com at 1.2 s1.2 s
  3. kenzzi.com at 1.8 s1.8 s
  4. kenzzi.com at 2.3 s2.3 s
  5. kenzzi.com at 2.9 s2.9 s
  6. kenzzi.com at 3.5 s3.5 s
  7. kenzzi.com at 4.1 s4.1 s
  8. kenzzi.com at 4.7 s4.7 s

Speed

6 to fix66
  • Mobile performance score: 66

    66/100

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

  • Render-blocking requests

    900 ms

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

  • Reduce unused JavaScript

    580 ms · 106 KiB

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

  • Improve image delivery

    500 ms · 81 KiB

    2 images could be 81 KiB 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.

  • Klaviyo adds 236 ms

    236 ms

    Klaviyo costs a phone 236 ms of main-thread work and 309 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, 910 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Klaviyo, Google CDN and Shopify and others), adding 493 KiB and 342 ms of main-thread time.

  • Reduce unused CSS

    280 ms · 42 KiB

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

  • Use efficient cache lifetimes

    150 ms · 22 KiB

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

  • Legacy JavaScript

    150 ms · 19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 124 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.

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

    4 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 10.7 s

    10.7 s

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

  • Time to Interactive: 10.8 s

    10.8 s

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

  • Speed Index: 5.8 s

    5.8 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Tap response (INP) held steady for real visitors

    +8%

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

  • 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 1.2 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user INP: 95 ms

    95 ms

    Real visitors wait 95 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.

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 592 ms

    592 ms

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

  • Total Blocking Time: 123 ms

    123 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix50
  • Page weight: 2.4 MB in 167 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 167 requests on a phone: images 1.0 MB (21), other files 636 KiB (72) and scripts 589 KiB (62). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.68 g

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

Accessibility

1 to fix97
  • 5 tap targets too small

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

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

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

1 checks passed
  • Every image has alt text

    All 39 images in the HTML carry an alt attribute.

SEO

2 to fixGoogle 9295
  • No social preview image

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

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 44 internal links, 15 external

    The homepage links to 44 pages on kenzzi.com and 15 external pages.

7 checks passed
  • Meta description: 133 characters

    Your meta description is 133 characters: “Do your own laser hair removal at home with the Kenzzi IPL Laser Hair Removal Handset. Hairless, smooth skin in just a …”.

  • One H1 headline

    Your main headline reads: “Kenzzi”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “Laser Hair Removal at Home | Kenzzi”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, 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://kenzzi.com/sitemap.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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.

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.

  • llms.txt published

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

Other pages

2 to fix90
  • 4 pages without a meta description

    https://kenzzi.com/collections/all, https://kenzzi.com/policies/privacy-policy, https://kenzzi.com/policies/terms-of-service and https://kenzzi.com/pages/faqs have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://kenzzi.com/pages/faqs has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://kenzzi.com/pages/mens-electric-shave-warranty, https://kenzzi.com/pages/ipliceusawarranty, https://kenzzi.com/pages/ipliceguarantee and https://kenzzi.com/pages/salon-pro-hair-dryer-warranty took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 100100
1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

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

  • About 624 words of copy

    The homepage carries about 624 words of visible text.

3 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Subscribe”, “learn more” and “shop now at walmart”.

  • 6 short forms

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on 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 kenzzi.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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

goaffpro.com · klaviyo.com · stamped.io

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

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Auckland

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on kenzzi.com, including 10 speed issues, 2 SEO issues and 3 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