teplarny.cz website review

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

2 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 2.8 s faster on a phone.

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

About 314 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 610 ms faster on a phone.

5 third-party services load with your homepage (Google Tag Manager, Facebook and Adobe TypeKit and others), adding 2.1 MB and 526 ms of main-thread time.

Google Tag Manager costs a phone 407 ms of main-thread work and 503 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.

Adobe TypeKit costs a phone 0 ms of main-thread work and 1.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.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

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

12 KiB could be saved by minifying JavaScript.

Desktop scores 76 but mobile only 42. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

Your largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Používáme cookies k personalizaci obsahu a reklam, k umožně…”.

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

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

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

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

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

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

th_franta_860_0_fixed_width.png weighs 561 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.4 MB in 38 requests on a phone: fonts 1.5 MB (5), images 1.1 MB (16) and scripts 708 KiB (8). Under 2 MB keeps phones on slow connections fast.

1 image (561 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.

1 image is downloaded at several times the size a phone draws it, for example th_franta_860_0_fixed_width.png at 860 px wide, shown at 180 px. Resized copies would save about 340 KiB.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

The homepage links to 54 pages on teplarny.cz and 14 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

There is no https://www.teplarny.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.

https://www.teplarny.cz/cs/vyjadreni-k-existenci-siti, https://www.teplarny.cz/cs/elektrina, https://www.teplarny.cz/cs/plyn, https://www.teplarny.cz/cs/teplo, https://www.teplarny.cz/cs/elektromobilita and https://www.teplarny.cz/cs/dodavka-chladu and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 963 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 3 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 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.