tagomago.pl website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Onet and luigisbox.tech and others), adding 1.3 MB and 1.2 s of main-thread time.

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

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

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

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

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

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

About 52 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 51 KiB JavaScript that modern phones do not need.

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

13 KiB JavaScript is shipped twice across bundles.

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.

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

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

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

Real visitors wait 405 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' tap response (inp) went from 255 ms to 431 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “JESIENNA PROMOCJA Z INPOST PAY! 🍂”.

Your homepage downloads 3.4 MB in 296 requests on a phone: scripts 1.6 MB (78), other files 1,022 KiB (125) and images 532 KiB (65). Under 2 MB keeps phones on slow connections fast.

hf_20261103_121909_2ac80769-7838-489b-beda-29c60f016072.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).

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

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

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

Elements with visible text labels do not have matching accessible names. (3 elements).

Your title is 74 characters, so Google will cut it off around 60: “Kosmetyki i perfumy - Drogeria internetowa Tagomago.pl – Sklep Tagomago.pl”.

The homepage links to 490 pages on tagomago.pl and 4 external pages.

There is no https://tagomago.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://tagomago.pl/collections/promocja-perfumy is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://tagomago.pl/pages/inpost-pay has no meta description, so Google writes the search snippet from whatever text it finds.

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

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.

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 2,211 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and 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.

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

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