trinnity.pl website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Cloudflare CDN and others), adding 719 KiB and 368 ms of main-thread time.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 2.5 MB in 252 requests on a phone: scripts 990 KiB (51), other files 947 KiB (139) and images 478 KiB (44). Under 2 MB keeps phones on slow connections fast.

4 images (232 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.

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

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

ARIA attributes must conform to valid values: 5 elements on the page fail this check, rated critical by axe-core.

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

10 elements hidden from screen readers can still receive keyboard focus.

Some list items are not inside a list.

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

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

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

There are 10 <h1> headlines (“<img src="//trinnity.pl/cdn/shop/files/TRINNITY_l…”, “ARTYKUŁY GRZEWCZE” and “ARTYKUŁY INSTALACYJNE”). One clear main headline is easier for people and search engines.

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

4 links have no real href, so search engines can't follow them.

The homepage links to 180 pages on trinnity.pl and 16 external pages.

https://trinnity.pl/pages/o-trinnity, https://trinnity.pl/pages/kalkulator-strat-ciepla and https://trinnity.pl/pages/kalkulator-mocy-grzewczych have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://trinnity.pl/collections/naczynia-wzbiorcze/products/naczynie-wzbiorcze-cwu-trinnity-fx-biale, whose canonical is https://trinnity.pl/products/naczynie-wzbiorcze-cwu-trinnity-fx-biale. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

2 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 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

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

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