7kd.pl website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, TikTok and Facebook and others), adding 1.1 MB and 670 ms of main-thread time.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).

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

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

54 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

10 KiB could be saved by minifying CSS.

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

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.

Your largest element takes 14.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Informujemy, iż w celu realizacji usług dostępnych w naszym…”.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 2.1 MB in 114 requests on a phone: scripts 1.4 MB (44), fonts 346 KiB (8) and images 219 KiB (16). Under 2 MB keeps phones on slow connections fast.

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

3 images further down the page (99 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 0.59 g of CO₂e: 70.3 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”.

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

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

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

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

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

Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

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

Your title is 76 characters, so Google will cut it off around 60: “Sklep z dywanami - Dywany online - Sklep internetowy - Dywany sklep - 7kd.pl”.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 387 pages on 7kd.pl and 41 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://7kd.pl/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://7kd.pl/content/29-propozycja is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://7kd.pl/content/29-propozycja, https://7kd.pl/31-kolekcje, https://7kd.pl/320-lara, https://7kd.pl/291-vintage and https://7kd.pl/353-sienna have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

3 images are 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.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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 1,722 words of visible text.

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