medik8.sk website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and Optanon and others), adding 2.0 MB and 1.4 s of main-thread time.

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

26 KiB could be saved by minifying JavaScript.

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

poweredbyhue.app costs a phone 150 ms of main-thread work and 536 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.

LoyaltyLion costs a phone 106 ms of main-thread work and 371 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.

About 123 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.

Polyfills for old browsers add 43 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.

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

3 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

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

Your homepage downloads 4.9 MB in 368 requests on a phone: scripts 2.5 MB (191), images 1.1 MB (34) and other files 822 KiB (116). Under 2 MB keeps phones on slow connections fast.

20260928_-_Global_Brand_Platform_-_Web_-_Shopify_Banner_2_-_ 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).

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

11 tap targets are too small or too close together to hit reliably with a finger.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

Your title is only 28 characters: “Medik8 Slovensko – Medik8-SK”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 133 pages on medik8.sk and 9 external pages.

Your homepage links to https://sk.medik8.com/collections/travel, which answers with an error. Visitors hit a dead end and search engines drop it.

https://sk.medik8.com/pages/my-medik8-rewards has no meta description, so Google writes the search snippet from whatever text it finds.

https://sk.medik8.com/collections/all has 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.

https://sk.medik8.com/collections/fine-lines-wrinkles, https://sk.medik8.com/collections/blemish-prone-skin and https://sk.medik8.com/collections/hyperpigmentation took over 3 s to send their HTML from our server.

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

11 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

5 errors were logged to the browser console while the page loaded, for example “ReferenceError: customerPrivacyApi is not defined”.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Your longest form asks for 13 fields (6 required). Every extra field lowers completion.

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

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

The page uses urgency cues (a countdown or limited-time wording).

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

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

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