pakolorente.com website review

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

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

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

About 701 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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

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

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.

Your largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “3 sztuki 249 zł”.

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

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

The layout shifts by 0.267 while loading, so content jumps under the reader's thumb. Good is under 0.1.

For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

Your homepage downloads 3.4 MB in 142 requests on a phone: images 1.5 MB (36), scripts 1.5 MB (49) and fonts 199 KiB (5). Under 2 MB keeps phones on slow connections fast.

1789628168_rwd_mobile.webp 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).

3 images further down the page (389 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.96 g of CO₂e: 114.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 elements use ARIA attributes their role does not allow, which confuses screen readers.

1 button has no accessible name, so screen readers announce just “button”.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

Your title is 220 characters, so Google will cut it off around 60: “Marka dla współczesnych mężczyzn, stylowa odzież męska, koszule, garnitury, swetry, spodn…”.

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

Structured data found (OnlineBusiness, Organization and WebSite) but with 2 problems, for example “Organization: missing name”.

Your <h1> is empty.

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

The homepage links to 156 pages on pakolorente.com and 6 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.pakolorente.com/pl/shoppinglist and https://www.pakolorente.com/basketedit.php are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.pakolorente.com/stocks.php, https://www.pakolorente.com/pl/shoppinglist and https://www.pakolorente.com/basketedit.php all use the title “Marka dla współczesnych mężczyzn, stylowa odzież męska, koszule, garn…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.pakolorente.com/stocks.php, https://www.pakolorente.com/pl/shoppinglist and https://www.pakolorente.com/basketedit.php use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.pakolorente.com/pol_m_KOLEKCJA_TRAVELER-tailored-5142.html, whose canonical is https://www.pakolorente.com/pol_m_KOLEKCJA_Kolekcje_Traveler-tailored-5142.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.pakolorente.com/pol_m_KOLEKCJA_TRAVELER-tailored-5142.html, https://www.pakolorente.com/pol_m_KOLEKCJA_SWIMWEAR-4415.html, https://www.pakolorente.com/pol_m_KOLEKCJA_UNDERWEAR-4249.html, https://www.pakolorente.com/pol_m_ONLINE-ONLY-4392.html and https://www.pakolorente.com/pol_m_KOLEKCJA_TRAVELER-4250.html took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://client592.idosell.com/checkup.php?c=8127b39b573891506825eff0137f0e1f.

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “$ is not defined <anonymous>:2:5 https://www.pakolorente.com/gfx/pol/main_shop.js.gzip?r=1792071206:5:274851 Array.forE…”.

Chrome logged issues while loading the page (“Cookie”).

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: a star rating. 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 423 words of visible text.

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