Website review, no card needed

bonnemaman.cz logo

bonnemaman.cz website review

Visit site (opens in a new tab)Reviewed 8 November 202629 issues · 74 checks

This review found 29 issues worth fixing on bonnemaman.cz, 7 of them high impact, across 74 checks. The most urgent: 3,260 HTML elements. 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.0 s1.3 sMay 16Oct 31.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.9 s
May 23, 20261.7 s
May 30, 20261.6 s
Jun 6, 20261.4 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Aug 22, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
115 ms71 msMay 23Sep 2696 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202695 ms
May 30, 202695 ms
Jun 6, 2026110 ms
Jul 4, 202689 ms
Sep 12, 202676 ms
Sep 19, 202689 ms
Sep 26, 202696 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 bonnemaman.cz (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bonnemaman.cz at 0.4 s0.4 s
  2. bonnemaman.cz at 0.8 s0.8 s
  3. bonnemaman.cz at 1.2 s1.2 s
  4. bonnemaman.cz at 1.6 s1.6 s
  5. bonnemaman.cz at 2.0 s2.0 s
  6. bonnemaman.cz at 2.4 s2.4 s
  7. bonnemaman.cz at 2.8 s2.8 s
  8. bonnemaman.cz at 3.2 s3.2 s

Speed

7 to fix71
  • 3,260 HTML elements

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

  • Mobile performance score: 71

    71/100

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

  • Improve image delivery

    500 ms · 376 KiB

    11 images could be 376 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.

  • Render-blocking requests

    600 ms

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

  • Reduce unused JavaScript

    309 KiB

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

  • Main-thread work: 2.2 s

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

  • Shopify adds 41 ms

    41 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Optanon, Shopify and nfcube.com and others), adding 764 KiB and 289 ms of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 84 KiB

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

  • 4 long tasks on the main thread

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

  • Reduce unused CSS

    44 KiB

    About 44 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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: 8 ms

    8 ms

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

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 6.0 s

    6.0 s

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

  • Time to Interactive: 9.0 s

    9.0 s

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

  • Speed Index: 4.8 s

    4.8 s

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

  • Cumulative Layout Shift: 0.117

    0.117

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • Largest content (LCP) got 20% faster for real visitors

    -20%

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

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

  • Total Blocking Time: 79 ms

    79 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.9 MB in 199 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 199 requests on a phone: images 1.2 MB (34), other files 758 KiB (90) and scripts 695 KiB (63). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

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

    0.82 g

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

2 checks passed
  • Images load when needed

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

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 9794
  • 1 tap target too small

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

  • 97 images without alt text

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

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

    All page content should be contained by landmarks: 62 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 (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.

  • 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
  • 47 automated accessibility rules passed

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

SEO

3 to fixGoogle 9291
  • Structured data has 8 problems

    Structured data found ((untyped) and Organization) but with 8 problems, for example “untyped block: missing @context (expected "https://schema.org")”.

  • No social preview image

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 267 internal links, 14 external

    The homepage links to 267 pages on bonnemaman.cz and 14 external pages.

6 checks passed
  • Meta description: 128 characters

    Your meta description is 128 characters: “Bonne Maman nabízí ve svém internetovém obchodě džemy, sušenky, sladkosti, dárkové sady a dárky vyrobené s maximální pe…”.

  • One H1 headline

    Your main headline reads: “Bonne Maman nabízí ve svém e-shopu džemy, sušenky a pečivo, ale také krabičky a plechovky plněné džemy a dárky. Všechny…”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Bonne Maman Česko : Džemy a sušenky Bonne Maman CZ”.

  • Canonical URL set

    The canonical URL is https://bonnemaman.cz/.

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

  • llms.txt published

    The site publishes https://bonnemaman.cz/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://bonnemaman.cz/collections/eshop-novinky, https://bonnemaman.cz/collections/eshop-oblibene-produkty, https://bonnemaman.cz/collections/zele and https://bonnemaman.cz/collections/marmelady have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://bonnemaman.cz/products/adventkalender-2026, whose canonical is https://bonnemaman.cz/products/adventni-kalendar. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8591
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “debounce is not defined”.

  • Pasting is blocked

    A form field blocks pasting, which frustrates password managers and people on phones.

2 checks passed
  • Tap targets are thumb-sized

    145 of 151 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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 789 words of copy

    The homepage carries about 789 words of visible text.

2 checks passed
  • 6 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 5 cookies set on arrival

    5

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

  • 17 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 bonnemaman.cz, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on bonnemaman.cz, including 12 speed issues, 3 SEO issues and 4 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