Website review, no card needed

facederma.cz logo

facederma.cz website review

Visit site (opens in a new tab)Reviewed 5 November 202634 issues · 74 checks

This review found 34 issues worth fixing on facederma.cz, 10 of them high impact, across 74 checks. The most urgent: page weight: 15.0 MB in 276 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.7 s2.0 sMay 16Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.3 s
May 23, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.2 s
Jun 20, 20262.1 s
Jul 11, 20262.1 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.6 s
Sep 12, 20262.5 s
Sep 26, 20262.3 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
191 ms157 msMay 16Oct 17180 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026181 ms
Jun 6, 2026174 ms
Jun 20, 2026161 ms
Jul 25, 2026168 ms
Aug 1, 2026165 ms
Aug 8, 2026167 ms
Aug 15, 2026182 ms
Aug 22, 2026187 ms
Aug 29, 2026187 ms
Sep 5, 2026187 ms
Sep 12, 2026171 ms
Oct 10, 2026178 ms
Oct 17, 2026180 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 facederma.cz (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. facederma.cz at 0.7 s0.7 s
  2. facederma.cz at 1.4 s1.4 s
  3. facederma.cz at 2.1 s2.1 s
  4. facederma.cz at 2.8 s2.8 s
  5. facederma.cz at 3.5 s3.5 s
  6. facederma.cz at 4.2 s4.2 s
  7. facederma.cz at 4.9 s4.9 s
  8. facederma.cz at 5.6 s5.6 s

Speed

8 to fix71
  • 3,785 HTML elements

    The page has 3,785 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.

  • Render-blocking requests

    750 ms

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

  • Use efficient cache lifetimes

    300 ms · 441 KiB

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

  • Improve image delivery

    701 KiB

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

  • Main-thread work: 3.8 s

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

  • Reduce unused CSS

    300 ms · 41 KiB

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

  • YouTube adds 0 ms

    0 ms

    YouTube costs a phone 0 ms of main-thread work and 539 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 (Clarity, Shopify and chatty.net and others), adding 908 KiB and 213 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Duplicated JavaScript

    35 KiB

    35 KiB JavaScript is shipped twice across bundles.

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

    9 ms

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

Core Web Vitals

3 to fix66
  • Largest Contentful Paint: 20.6 s

    20.6 s

    Your largest element takes 20.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “K ukládání informací o zařízení a/nebo přístupu k nim použí…”.

  • Time to Interactive: 21.3 s

    21.3 s

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

  • Speed Index: 4.7 s

    4.7 s

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

  • Tap response (INP) held steady for real visitors

    +1%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 181 ms to 180 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.

4 checks passed
  • Largest content (LCP) got 11% faster for real visitors

    -11%

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

  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Total Blocking Time: 82 ms

    82 ms

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

  • Cumulative Layout Shift: 0.007

    0.007

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

Images and page weight

4 to fix43
  • Page weight: 15.0 MB in 276 requests

    15.0 MB

    Your homepage downloads 15.0 MB in 276 requests on a phone: media 10.0 MB (1), images 3.1 MB (60) and other files 790 KiB (110). Under 2 MB keeps phones on slow connections fast.

  • 15 images below the first screen load straight away

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

  • 8 images in older formats

    8 images (535 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.

  • 5 images far larger than shown

    43 KiB

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

  • About 4.3 g of CO₂ per visit

    4.25 g

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

Accessibility

9 to fixGoogle 8689
  • 21 text elements with low contrast

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

  • Frames without titles

    12 frames have no title, so screen-reader users cannot tell what they contain.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 55 images without alt text

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

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

    All page content should be contained by landmarks: 9 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 (3 elements)

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

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 form fields without a label

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 9291
  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://facederma.cz/search?q={search_term_string}")”.

  • One H1 headline

    Your <h1> is empty.

  • 134 internal links, 7 external

    The homepage links to 134 pages on facederma.cz and 7 external pages.

6 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Slovenská kosmetika, která maximálně využívá sílu přírodních látek. Výrobky byly navrženy tak, aby respektovaly citlivo…”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Facederma®: Kosmetika vytvořená s ohledem na vědu a přírodu”.

  • Canonical URL set

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

  • 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://facederma.cz/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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 13 pages without a meta description

    https://facederma.cz/collections/produkty, https://facederma.cz/collections/zvyhodnena-cena, https://facederma.cz/collections/bila-rada, https://facederma.cz/collections/vrasky, https://facederma.cz/collections/cisteni-pleti and https://facederma.cz/collections/akne and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages without an H1

    https://facederma.cz/collections/produkty, https://facederma.cz/collections/zvyhodnena-cena, https://facederma.cz/collections/bila-rada, https://facederma.cz/collections/vrasky, https://facederma.cz/collections/cisteni-pleti and https://facederma.cz/collections/akne and 5 others 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 38 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.

  • 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

1 to fixGoogle 9693
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    45 of 46 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: 7 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 912 words of copy

    The homepage carries about 912 words of visible text.

2 checks passed
  • 21 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

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, Meta Pixel 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.

  • 12 cookies set on arrival

    12

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

  • 21 other companies contacted

    Loading the homepage contacts 21 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 facederma.cz, 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 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Microsoft Clarity · Judge Me Reviews · Gdpr Cookie Consent · Avada Faqs · Stape Remix

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

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on facederma.cz, including 11 speed issues, 2 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