mailstep.cz website review

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

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

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

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

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

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

16 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

Hubspot costs a phone 601 ms of main-thread work and 504 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.

Facebook costs a phone 476 ms of main-thread work and 307 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 block the main thread while loading, the longest for 469 ms. During a long task the page ignores taps.

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

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

About 17 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 CSS.

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

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

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

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

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

Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Profesionální fulfillment pro e-shopy od lídra na trhu”. Most of its time is element render delay (2.2 s).

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.

Your homepage downloads 5.3 MB in 148 requests on a phone: images 2.6 MB (97), scripts 1.8 MB (24) and media 669 KiB (1). Under 2 MB keeps phones on slow connections fast.

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

2 buttons have no accessible name, so screen readers announce just “button”.

35 elements hidden from screen readers can still receive keyboard focus.

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

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

All page content should be contained by landmarks: 24 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.

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

Your title is 67 characters, so Google will cut it off around 60: “Mailstep - Svěřte logistiku vašeho e-shopu profesionálům | Mailstep”.

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 26 pages on mailstep.cz and 29 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 https://mailstep.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://mailstep.cz/integrace, https://mailstep.cz/en, https://mailstep.cz/sk and https://mailstep.cz/de have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

10 images failed to load on a phone, for example https://mailstep.cz/frontend/build/img/icons/arrow_down.svg.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

There is no form on the homepage, so every lead has to click through to another page first.

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 2,131 words of visible text.

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