Website review, no card needed

berner.cz logo

berner.cz website review

Visit site (opens in a new tab)Reviewed 21 October 202642 issues · 85 checks

This review found 42 issues worth fixing on berner.cz, 21 of them high impact, across 85 checks. The most urgent: render-blocking 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
3.0 s2.7 sMay 2Oct 172.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.8 s
May 9, 20262.8 s
May 16, 20262.8 s
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.8 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.8 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Oct 17, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
245 ms227 msMay 2Oct 17240 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026240 ms
May 9, 2026240 ms
May 16, 2026240 ms
May 23, 2026239 ms
May 30, 2026237 ms
Jun 6, 2026236 ms
Jun 13, 2026235 ms
Jun 20, 2026234 ms
Jun 27, 2026234 ms
Jul 4, 2026235 ms
Jul 11, 2026236 ms
Jul 18, 2026234 ms
Jul 25, 2026234 ms
Aug 1, 2026231 ms
Aug 8, 2026229 ms
Aug 15, 2026230 ms
Aug 22, 2026229 ms
Aug 29, 2026231 ms
Sep 5, 2026235 ms
Sep 12, 2026237 ms
Sep 19, 2026240 ms
Sep 26, 2026243 ms
Oct 3, 2026241 ms
Oct 10, 2026241 ms
Oct 17, 2026240 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 berner.cz (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. berner.cz at 0.6 s0.6 s
  2. berner.cz at 1.2 s1.2 s
  3. berner.cz at 1.8 s1.8 s
  4. berner.cz at 2.5 s2.5 s
  5. berner.cz at 3.1 s3.1 s
  6. berner.cz at 3.7 s3.7 s
  7. berner.cz at 4.3 s4.3 s
  8. berner.cz at 4.9 s4.9 s

Speed

12 to fix32
  • Render-blocking requests

    4.8 s

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.8 s.

  • Improve image delivery

    2.1 s · 1.5 MB

    33 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

  • Reduce unused JavaScript

    2.7 s · 547 KiB

    About 547 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

  • Use efficient cache lifetimes

    2.6 s · 419 KiB

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

  • Document request latency

    1.5 s

    The HTML itself could arrive about 1.5 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    1.5 s

    Reduce initial server response time. Google estimates savings of 1.5 s on a phone.

  • Mobile performance score: 32

    32/100

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

  • 3,699 HTML elements

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

  • Reduce unused CSS

    750 ms · 172 KiB

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

  • Usercentrics CMP adds 329 ms

    329 ms

    Usercentrics CMP costs a phone 329 ms of main-thread work and 195 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.2 s

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

  • Server response: 1.6 s

    1.6 s

    Your server takes 1.6 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Usercentrics CMP, Kameleoon and Google Tag Manager), adding 227 KiB and 357 ms of main-thread time.

  • 8 long tasks on the main thread

    8 long tasks block the main thread while loading, the longest for 231 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

    7 KiB

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

Core Web Vitals

12 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: 18.0 s

    18.0 s

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

  • First Contentful Paint: 7.3 s

    7.3 s

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

  • Time to Interactive: 19.9 s

    19.9 s

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

  • Speed Index: 11.6 s

    11.6 s

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

  • Cumulative Layout Shift: 0.352

    0.352

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user INP: 245 ms

    245 ms

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

  • Real-user CLS: 0.17

    0.17

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

  • Real-user TTFB: 998 ms

    998 ms

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

  • Total Blocking Time: 283 ms

    283 ms

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

  • 8 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

1 checks passed
  • Real-user FCP: 1.8 s

    1.8 s

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

Images and page weight

4 to fix28
  • Page weight: 4.1 MB in 146 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 146 requests on a phone: images 2.6 MB (108), scripts 1.1 MB (17) and fonts 192 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 23 images far larger than shown

    3.1 MB

    23 images are downloaded at several times the size a phone draws them, for example 150631567261726.jpg at 2,048 px wide, shown at 347 px. Resized copies would save about 3.1 MB.

  • 1 image over 500 KB

    150631567261726.jpg weighs 697 KiB. On a phone connection a single image that size takes seconds.

  • 21 images below the first screen load straight away

    21 images further down the page (2.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 3 images in older formats

    3 images (369 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.

  • About 1.2 g of CO₂ per visit

    1.15 g

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

Accessibility

6 to fixGoogle 8292
  • 43 buttons without a name

    43 buttons have no accessible name, so screen readers announce just “button”.

  • 7 tap targets too small

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

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 5 form fields without a label

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

  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 160 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

6 to fixGoogle 8565
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (21 characters)

    Your title is only 21 characters: “Startpage | Berner CZ”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 2 problems

    Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("https://shop.berner.eu/cz-cs/_ui/theme/berner/img/berner-logo.svg")”.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 688 internal links, 11 external

    The homepage links to 688 pages on berner.cz and 11 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://shop.berner.eu/cz-cs/.

  • 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://shop.berner.eu/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://shop.berner.eu/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.

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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,457 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 3 pages without a meta description

    https://shop.berner.eu/cz-cs/company/berner, https://shop.berner.eu/cr/index_cs_CZ.html and https://shop.berner.eu/cz-cs/career/welcome have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://shop.berner.eu/cz-cs/company/berner and https://shop.berner.eu/cz-cs/career/welcome 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 196 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

  • 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 3 pages that loaded have a <title>.

Best practices

Google 96100
  • 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

    109 of 115 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

5 checks passed
  • Clear next step on the first screen

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

  • 2 calls to action

    The homepage has 2 calls to action, for example “Shop”.

  • 5 short forms

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

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks, 3 customer or partner logos and 2 trust badges.

  • 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 Google Tag Manager (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

  • 4 cookies set on arrival

    4

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

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

1 checks passed
  • Consent tool: Usercentrics

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on berner.cz, including 24 speed issues and 6 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