fitmar.cz website review

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

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

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

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

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

Shopify costs a phone 114 ms of main-thread work and 350 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 load with your homepage (Google Tag Manager, Clarity and Shopify and others), adding 890 KiB and 497 ms of main-thread time.

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

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

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

Polyfills for old browsers add 37 KiB JavaScript that modern phones do not need.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying JavaScript.

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

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

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

Over the last 25 four-week periods to 2026-11-07, 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).

Your homepage downloads 3.4 MB in 200 requests on a phone: images 1.5 MB (50), other files 765 KiB (68) and scripts 712 KiB (60). Under 2 MB keeps phones on slow connections fast.

Obrazek.webp 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).

9 images (518 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.

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

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

Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.

ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

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

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

Your meta description is 187 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 141 pages on fitmar.cz and 21 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://fitmar.cz/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://fitmar.cz/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://fitmar.cz/customer_authentication/redirect and https://fitmar.cz/collections/fitmar%C2%AE have no meta description, so Google writes the search snippet from whatever text it finds.

https://fitmar.cz/pages/wishlist and https://fitmar.cz/pages/o-nas use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://fitmar.cz/collections/fitmar%C2%AE, whose canonical is https://fitmar.cz/collections/fitmar%c2%ae. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://fitmar.cz/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 956 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Klaviyo 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.

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

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.

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