Website review, no card needed
empik.com website review
Visit site (opens in a new tab)Reviewed 18 November 202646 issues · 84 checks
This review found 46 issues worth fixing on empik.com, 15 of them high impact, across 84 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.5 s |
| Nov 14, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 312 ms |
| Jun 6, 2026 | 320 ms |
| Jun 13, 2026 | 327 ms |
| Jun 20, 2026 | 335 ms |
| Jun 27, 2026 | 346 ms |
| Jul 4, 2026 | 353 ms |
| Jul 11, 2026 | 355 ms |
| Jul 18, 2026 | 355 ms |
| Jul 25, 2026 | 347 ms |
| Aug 1, 2026 | 343 ms |
| Aug 8, 2026 | 347 ms |
| Aug 15, 2026 | 352 ms |
| Aug 22, 2026 | 358 ms |
| Aug 29, 2026 | 357 ms |
| Sep 5, 2026 | 351 ms |
| Sep 12, 2026 | 340 ms |
| Sep 19, 2026 | 328 ms |
| Sep 26, 2026 | 316 ms |
| Oct 3, 2026 | 308 ms |
| Oct 10, 2026 | 309 ms |
| Oct 17, 2026 | 313 ms |
| Oct 24, 2026 | 321 ms |
| Oct 31, 2026 | 326 ms |
| Nov 7, 2026 | 330 ms |
| Nov 14, 2026 | 333 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Render-blocking requests
1.7 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Reduce unused CSS
1.2 s · 236 KiBAbout 236 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.
12,478 HTML elements
The page has 12,478 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Reduce initial server response time
762 msReduce initial server response time. Google estimates savings of 762 ms on a phone.
Document request latency
750 msThe HTML itself could arrive about 750 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
262 KiB6 images could be 262 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Server response: 862 ms
862 msYour server takes 862 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 239 ms. During a long task the page ignores taps.
Legacy JavaScript
20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need.
2 third-party services on the page
2 third-party services load with your homepage (Cloudflare and Google Tag Manager), adding 11 KiB and 8 ms of main-thread time.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Use efficient cache lifetimes
4 KiB1 file is served with short cache lifetimes, so returning visitors download them again (4 KiB).
Core Web Vitals
Fails Core Web Vitals for real visitors
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-user INP: 557 ms
557 msReal visitors wait 557 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Time to Interactive: 24.0 s
24.0 sThe page becomes fully interactive after 24.0 s. Good is under 3.8 s.
Speed Index: 9.4 s
9.4 sVisually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.7 s
3.7 sReal visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.23
0.23For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 919 ms
919 msReal visitors wait 919 ms for your server to start answering (75th percentile). Good is under 800 ms.
59 images without width and height
59 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 588 ms
588 msScripts block taps and scrolling for 588 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 3.0 s
3.0 sYour largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Elektronika w Black Weeks do -70% oraz w świetnych cenach”. Most of its time is element render delay (2.2 s).
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 312 ms to 333 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.3 MB in 143 requests
5.3 MBYour homepage downloads 5.3 MB in 143 requests on a phone: images 2.4 MB (91), scripts 2.3 MB (17) and stylesheets 244 KiB (1). Under 2 MB keeps phones on slow connections fast.
14 images below the first screen load straight away
14 images further down the page (613 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (218 KiB) are 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.
About 1.5 g of CO₂ per visit
1.50 gBy 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.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
28 buttons without a name
28 buttons have no accessible name, so screen readers announce just “button”.
28 tap targets too small
28 tap targets are too small or too close together to hit reliably with a finger.
18 text elements with low contrast
18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
163 images without alt text
163 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Alternative text of images should not be repeated as text (25 elements)
Alternative text of images should not be repeated as text: 25 elements on the page fail this check, rated minor by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (88 characters)
Your title is 88 characters, so Google will cut it off around 60: “Empik.com | 10 000 000 produktów i pomysłów na prezent | Dostawa za 0 zł z Empik Premium”.
Meta description is long (161 characters)
Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.
1,314 internal links, 2 external
The homepage links to 1,314 pages on empik.com and 2 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.empik.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.empik.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (7,823 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.empik.com/llms.txt (9 KiB, 35 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.empik.com/okazje/elektronika is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without an H1
https://www.empik.com/okazje/elektronika has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 124 found) and read each the way a search engine does.
5 checks passed
Linked pages load
5 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 3 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 3 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://media.empik.com/content/cpl/2606/1782738593439.jpg.
189 small tap targets
189 of 448 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 9,406 words of copy
The homepage carries about 9,406 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Start”.
1 call to action
The homepage has 1 call to action, for example “Start”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
9 cookies set on arrival
9Opening the homepage sets 9 cookies (measured from a US location before any click).
No consent tool detected
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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at empik.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Company
- Founded
- 1991
- Headquarters
- Warsaw
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on empik.com, including 22 speed issues, 4 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.