pss.sk website review

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

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

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

7 images could be 279 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.

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

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

3 third-party services load with your homepage (Google Tag Manager, Cookiebot and daktela.com), adding 514 KiB and 290 ms of main-thread time.

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

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

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.

Real visitors wait 3.0 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Real visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 204 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 2.8 MB in 60 requests on a phone: images 1.3 MB (38), scripts 591 KiB (7) and HTML 434 KiB (2). Under 2 MB keeps phones on slow connections fast.

banner-m-uver-na-dokoncenie-655x1024.png 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).

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

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

Headings skip levels (h2 → h5, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

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

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

The homepage links to 189 pages on pss.sk and 14 external pages.

There is no https://www.pss.sk/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.pss.sk/interaktivny-sprievodca is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.pss.sk/novinky, https://www.pss.sk/kontakty and https://www.pss.sk/interaktivny-sprievodca have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.pss.sk/informacie/aktivujte-si-sluzbu-moja-pss and https://www.pss.sk/interaktivny-sprievodca have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.pss.sk/vsetky-produkty, https://www.pss.sk/interaktivny-sprievodca, https://www.pss.sk/sporenie/sporenie-so-statnou-premiou, https://www.pss.sk/sporenie/sporenie-deti and https://www.pss.sk/sporenie/online-sporenie-lisiak took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

1 image is served at too low a resolution for sharp phone screens.

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.

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.

Social proof on the homepage: 7 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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