Website review, no card needed

kapazi.com logo

kapazi.com website review

Visit site (opens in a new tab)Reviewed 28 October 202635 issues · 86 checks

This review found 35 issues worth fixing on kapazi.com, 12 of them high impact, across 86 checks. The most urgent: page weight: 34.7 MB in 232 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
2.2 s1.9 sAug 8Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
Aug 8, 20262.1 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.0 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
218 ms184 msAug 8Oct 24188 ms
Show as table
DateReal-visitor tap response (INP)
Aug 8, 2026214 ms
Aug 15, 2026208 ms
Aug 22, 2026211 ms
Aug 29, 2026211 ms
Sep 5, 2026203 ms
Sep 12, 2026204 ms
Sep 19, 2026204 ms
Sep 26, 2026197 ms
Oct 3, 2026204 ms
Oct 10, 2026204 ms
Oct 17, 2026194 ms
Oct 24, 2026188 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 kapazi.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix72
  • 3,537 HTML elements

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

  • Improve image delivery

    300 ms · 3.9 MB

    36 images could be 3.9 MB 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.

  • Mobile performance score: 72

    72/100

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

  • Render-blocking requests

    350 ms

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

  • Reduce unused JavaScript

    310 KiB

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

  • Main-thread work: 2.8 s

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

  • Shopify adds 39 ms

    39 ms

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 103 ms. During a long task the page ignores taps.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Shopify and shop.app), adding 416 KiB and 39 ms of main-thread time.

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

  • Use efficient cache lifetimes

    1 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

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

4 to fix100
  • Largest Contentful Paint: 5.4 s

    5.4 s

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

  • Time to Interactive: 8.6 s

    8.6 s

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

  • Speed Index: 6.0 s

    6.0 s

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

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

  • Tap response (INP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 214 ms to 188 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-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.1 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: 2.0 s

    2.0 s

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

  • Real-user INP: 185 ms

    185 ms

    Real visitors wait 185 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.5 s

    1.5 s

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

  • Real-user TTFB: 792 ms

    792 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 27 ms

    27 ms

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

Images and page weight

5 to fix26
  • Page weight: 34.7 MB in 232 requests

    34.7 MB

    Your homepage downloads 34.7 MB in 232 requests on a phone: media 27.5 MB (6), images 5.6 MB (51) and other files 722 KiB (77). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    2_-_Kapazi_-_CleanKap_-_concessionaria.jpg weighs 624 KiB. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    1.0 MB

    5 images are downloaded at several times the size a phone draws them, for example 2_-_Kapazi_-_CleanKap_-_concessionaria.jpg at 1,479 px wide, shown at 274 px. Resized copies would save about 1.0 MB.

  • An image on the first screen is lazy-loaded

    jundiai-5.jpg 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).

  • 4 images in older formats

    4 images (567 KiB) are 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.

  • 1 image below the first screen load straight away

    1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 9.8 g of CO₂ per visit

    9.83 g

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

Accessibility

8 to fixGoogle 8290
  • 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.

  • Hidden but focusable

    30 elements hidden from screen readers can still receive keyboard focus.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • 26 images without alt text

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

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

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

  • Alternative text of images should not be repeated as text (3 elements)

    Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 53 automated accessibility rules passed

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

SEO

3 to fixGoogle 8588
  • Meta description is long (249 characters)

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

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

  • One H1 headline

    Your <h1> is empty.

  • 183 internal links, 70 external

    The homepage links to 183 pages on kapazi.com and 70 external pages.

6 checks passed
  • Title: 49 characters

    Your title is a healthy 49 characters: “Kapazi - Rugs, Vinyl Flooring and Synthetic Grass”.

  • Canonical URL set

    The canonical URL is https://kapazi.com/en.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://kapazi.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 (2,090 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix93
  • 4 pages share a meta description

    https://kapazi.com/en/collections/all, https://kapazi.com/en/pages/about-us, https://kapazi.com/en/pages/stores and https://kapazi.com/en/pages/industrial-units use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://kapazi.com/en/pages/about-us, https://kapazi.com/en/pages/stores and https://kapazi.com/en/pages/industrial-units 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 53 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 9687
  • 13 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix78
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Local business without LocalBusiness data

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

  • No analytics detected

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • About 1,443 words of copy

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

6 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Learn more”, “Shop online for your Home” and “Shop Online for Your Business”.

  • 6 short forms

    6 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 2 customer or partner logos and 2 trust badges.

  • Direct contact links

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

  • Phone number on the homepage

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 8 cookies set on arrival

    8

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

  • 9 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on kapazi.com, including 11 speed issues, 3 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