Website review, no card needed

kumikomatcha.fr logo

kumikomatcha.fr website review

Visit site (opens in a new tab)Reviewed 17 November 202635 issues · 85 checks

This review found 35 issues worth fixing on kumikomatcha.fr, 10 of them high impact, across 85 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
2.8 s2.2 sMay 30Nov 142.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.7 s
Jul 11, 20262.6 s
Jul 18, 20262.5 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.2 s
Sep 19, 20262.4 s
Sep 26, 20262.5 s
Oct 3, 20262.6 s
Oct 10, 20262.7 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Oct 31, 20262.6 s
Nov 7, 20262.5 s
Nov 14, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
192 ms139 msMay 30Nov 14156 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026160 ms
Jun 6, 2026158 ms
Jun 13, 2026163 ms
Jun 20, 2026167 ms
Jun 27, 2026171 ms
Jul 4, 2026182 ms
Jul 11, 2026186 ms
Jul 18, 2026186 ms
Jul 25, 2026178 ms
Aug 1, 2026178 ms
Aug 8, 2026172 ms
Aug 15, 2026170 ms
Aug 22, 2026162 ms
Aug 29, 2026155 ms
Sep 5, 2026151 ms
Sep 12, 2026148 ms
Sep 19, 2026151 ms
Sep 26, 2026155 ms
Oct 3, 2026152 ms
Oct 10, 2026152 ms
Oct 17, 2026152 ms
Oct 24, 2026145 ms
Oct 31, 2026147 ms
Nov 7, 2026148 ms
Nov 14, 2026156 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 kumikomatcha.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kumikomatcha.fr at 0.7 s0.7 s
  2. kumikomatcha.fr at 1.3 s1.3 s
  3. kumikomatcha.fr at 2.0 s2.0 s
  4. kumikomatcha.fr at 2.6 s2.6 s
  5. kumikomatcha.fr at 3.3 s3.3 s
  6. kumikomatcha.fr at 3.9 s3.9 s
  7. kumikomatcha.fr at 4.6 s4.6 s
  8. kumikomatcha.fr at 5.2 s5.2 s

Speed

8 to fix70
  • Mobile performance score: 70

    70/100

    Your mobile performance score is 70. 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 (Google Tag Manager, Klaviyo and gotolstoy.com and others), adding 2.0 MB and 567 ms of main-thread time.

  • Reduce unused JavaScript

    450 ms · 279 KiB

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

  • Render-blocking requests

    550 ms

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

  • Google Tag Manager adds 295 ms

    295 ms

    Google Tag Manager costs a phone 295 ms of main-thread work and 355 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.3 s

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

  • 1,973 HTML elements

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

  • Shopify adds 35 ms

    35 ms

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

  • Use efficient cache lifetimes

    200 ms · 204 KiB

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

  • Improve image delivery

    219 KiB

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

  • Reduce unused CSS

    140 ms · 66 KiB

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

  • 3 long tasks on the main thread

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

  • Legacy JavaScript

    31 KiB

    Polyfills for old browsers add 31 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.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 10 ms

    10 ms

    Your server sent the HTML in 10 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.

  • Time to Interactive: 14.8 s

    14.8 s

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

  • Largest Contentful Paint: 5.9 s

    5.9 s

    Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “thé matcha premium bio kumiko matcha”.

  • Speed Index: 7.1 s

    7.1 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • 23 images without width and height

    23 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -4%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 160 ms to 156 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-11-14, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user INP: 137 ms

    137 ms

    Real visitors wait 137 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 TTFB: 655 ms

    655 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Total Blocking Time: 114 ms

    114 ms

    Scripts block the page for only 114 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

2 to fix75
  • Page weight: 3.4 MB in 195 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 195 requests on a phone: scripts 1.1 MB (94), other files 786 KiB (54) and media 713 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    52 KiB

    1 image is downloaded at several times the size a phone draws it, for example IMG_4457_2048x2048.JPG at 1,861 px wide, shown at 356 px. Resized copies would save about 52 KiB.

  • About 1.0 g of CO₂ per visit

    0.97 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 116.3 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

8 to fixGoogle 7989
  • Unlabelled dropdowns

    6 dropdowns have no label.

  • 12 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 6 images without alt text

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

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

  • 6 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Headings skip levels

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

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

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

Google 92100
  • 157 internal links, 5 external

    The homepage links to 157 pages on kumikomatcha.fr and 5 external pages.

8 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Vous cherchez du thé matcha bio premium ? Val de Kumiko Matcha vous propose du thé matcha de qualité cultivé et produit…”.

  • One H1 headline

    Your main headline reads: “Kumiko Matcha”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Kumiko Matcha, boutique de thé matcha premium bio du Japon”.

  • Canonical URL set

    The canonical URL is https://kumikomatcha.fr/.

  • Structured data in place

    Structured data found: WebPage 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://kumikomatcha.fr/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.

3 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 (1,443 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://kumikomatcha.fr/collections/nouveaux-produits is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://kumikomatcha.fr/collections/nouveaux-produits and https://kumikomatcha.fr/pages/laventure have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 5 broken images

    5 images failed to load on a phone, for example https://kumikomatcha.fr/.

  • 8 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were 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 fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: 11 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “contact & service client”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 27 cookies set on arrival

    27

    Opening the homepage sets 27 cookies, 1 of them by other companies (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 kumikomatcha.fr, 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

Simprosys Google Shopping Feed · Addingwell · Cozy Country Redirect · Tolstoy · Klaviyo Email Marketing Sms · Judge Me Reviews · Aftersell · sympl.fr · sealsubscriptions.com · nfcube.com · revenuehunt.com

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
Analytics
Google Tag Manager
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 kumikomatcha.fr, including 15 speed 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