solitea.cz website review

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

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

Your mobile performance score is 50 (desktop: 80). Pages that score under 90 lose visitors before the first paint.

Google Tag Manager costs a phone 807 ms of main-thread work and 723 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 CDN costs a phone 468 ms of main-thread work and 741 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.

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

consentmanager.net costs a phone 274 ms of main-thread work and 135 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.

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.

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

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

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

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, 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 2.4 MB in 53 requests on a phone: scripts 1.6 MB (16), other files 355 KiB (8) and HTML 135 KiB (3). Under 2 MB keeps phones on slow connections fast.

1 image (36 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 further down the page (36 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

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

Your page has no <title>, so Google has to invent the blue link in search results.

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

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token '/', " /*<![CDATA"... is not valid JSON)”.

No XML sitemap at https://www.seyfor.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at seyfor.com/robots.txt, the first file search crawlers ask for.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

The homepage links to 22 pages on solitea.cz and 7 external pages.

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.

There is no /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.

/en-hu/products, /en-hu/about-us, /en-hu/company-history, /en-hu/contact-us and /en-hu have no <title>, so Google invents the link text in results.

/cs-cz, /en-cz, /sk-sk, /hu-hu and /en-hu declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/en-hu/products, /en-hu/about-us, /en-hu/seyfor-group, /en-hu/seyfor-in-hungary, /en-hu/company-history and /en-hu/contact-us and 3 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 19 found) and read each the way a search engine does.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 176 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.

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

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