Website review, no card needed

albi.cz logo

albi.cz website review

Visit site (opens in a new tab)Reviewed 19 October 202638 issues · 86 checks

This review found 38 issues worth fixing on albi.cz, 18 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. 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.4 s1.3 sApr 25Oct 101.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.3 s
May 2, 20261.3 s
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
265 ms152 msApr 25Oct 10167 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026229 ms
May 2, 2026226 ms
May 9, 2026221 ms
May 16, 2026220 ms
May 23, 2026223 ms
May 30, 2026227 ms
Jun 6, 2026234 ms
Jun 13, 2026239 ms
Jun 20, 2026245 ms
Jun 27, 2026248 ms
Jul 4, 2026252 ms
Jul 11, 2026246 ms
Jul 18, 2026221 ms
Jul 25, 2026200 ms
Aug 1, 2026180 ms
Aug 8, 2026167 ms
Aug 15, 2026165 ms
Aug 22, 2026167 ms
Aug 29, 2026167 ms
Sep 5, 2026167 ms
Sep 12, 2026167 ms
Sep 19, 2026167 ms
Sep 26, 2026168 ms
Oct 3, 2026168 ms
Oct 10, 2026167 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 albi.cz (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. albi.cz at 0.8 s0.8 s
  2. albi.cz at 1.6 s1.6 s
  3. albi.cz at 2.4 s2.4 s
  4. albi.cz at 3.2 s3.2 s
  5. albi.cz at 4.0 s4.0 s
  6. albi.cz at 4.8 s4.8 s
  7. albi.cz at 5.5 s5.5 s
  8. albi.cz at 6.3 s6.3 s

Speed

12 to fix36
  • Use efficient cache lifetimes

    3.5 s · 1.7 MB

    85 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).

  • Reduce unused JavaScript

    1.4 s · 2.1 MB

    About 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 36

    36/100

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

  • Main-thread work: 5.9 s

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

  • 4,174 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, YouTube and Google CDN and others), adding 5.1 MB and 2.2 s of main-thread time.

  • Improve image delivery

    700 ms · 1.1 MB

    26 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

  • YouTube adds 470 ms

    470 ms

    YouTube costs a phone 470 ms of main-thread work and 2.5 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.

  • Reduce unused CSS

    450 ms · 235 KiB

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

  • Google CDN adds 293 ms

    293 ms

    Google CDN costs a phone 293 ms of main-thread work and 733 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.

  • Google Maps adds 144 ms

    144 ms

    Google Maps costs a phone 144 ms of main-thread work and 375 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.

  • 20 long tasks on the main thread

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

  • Render-blocking requests

    150 ms

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

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

    133 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 10.8 s

    10.8 s

    Your largest element takes 10.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Vláček, který se nezastaví!”.

  • Time to Interactive: 40.4 s

    40.4 s

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

  • Speed Index: 14.9 s

    14.9 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • 17 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.3 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.3 s

    1.3 s

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

  • Real-user INP: 167 ms

    167 ms

    Real visitors wait 167 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.2 s

    1.2 s

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

  • Real-user TTFB: 711 ms

    711 ms

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

  • Tap response (INP) got 26% faster for real visitors

    -26%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix50
  • Page weight: 7.6 MB in 165 requests

    7.6 MB

    Your homepage downloads 7.6 MB in 165 requests on a phone: scripts 4.5 MB (45), images 2.0 MB (67) and other files 402 KiB (31). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    karol-kvido-08-2026.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).

  • 6 images in older formats

    6 images (837 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.

  • 2 images far larger than shown

    47 KiB

    2 images are downloaded at several times the size a phone draws them, for example maxresdefault.jpg at 1,280 px wide, shown at 390 px. Resized copies would save about 47 KiB.

  • 4 images below the first screen load straight away

    4 images further down the page (247 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.2 g of CO₂ per visit

    2.16 g

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

Accessibility

4 to fixGoogle 9692
  • 5 text elements with low contrast

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

  • 12 images without alt text

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

  • 35 links without text

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

  • 4 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 33 automated accessibility rules passed

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

SEO

4 to fixGoogle 10076
  • No H1 headline

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

  • Title is short (23 characters)

    Your title is only 23 characters: “Albi.cz | Úvodní strana”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

  • 641 internal links, 35 external

    The homepage links to 641 pages on albi.cz and 35 external pages.

4 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Společenské hry, Kouzelné čtení, dětské hry Kvído, tipy na dárky, prémiové vonné svíčky Heart and Home a spoustu další …”.

  • Canonical URL set

    The canonical URL is https://albi.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://albi.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.

  • No llms.txt

    There is no https://albi.cz/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.

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.

  • Text is in the HTML

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

Other pages

1 to fix98
  • 6 pages share a meta description

    https://albi.cz/prodejny, https://albi.cz/inspirace, https://albi.cz/cteni-pro-radost, https://albi.cz/archiv, https://albi.cz/nahradni-dily-a-komponenty and https://albi.cz/kontakt use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

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

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

Best practices

3 to fixGoogle 9271
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.net/action/0?ti=295027752&tm=gtm002&Ver=2&mid=bc9f6fcc-5942-4d92-bb95-cb9ca310e81e&bo=2&gtm_tag_source=1&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Albi.cz%20%7C%20%C3%9Avodn%.

  • 13 small tap targets

    13 of 60 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 “Cannot read properties of null (reading 'addEventListener')”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

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

    The homepage carries about 632 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • 17 short forms

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

  • Social proof on the page

    Social proof on the homepage: 18 testimonial or review blocks, 1 customer or partner logo and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Microsoft Clarity (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.

  • 10 cookies set on arrival

    10

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

  • 36 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager

Company

Employees
300
Founded
1993
Headquarters
Prague

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on albi.cz, including 18 speed issues, 4 SEO issues and 2 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