Website review, no card needed

protym.pl logo

protym.pl website review

Visit site (opens in a new tab)Reviewed 6 November 202637 issues · 89 checks

This review found 37 issues worth fixing on protym.pl, 15 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.5 s2.1 sMay 16Oct 312.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.2 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.2 s
Sep 19, 20262.3 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.3 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Oct 31, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
117 ms99 msMay 16Oct 31111 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026104 ms
May 23, 2026103 ms
May 30, 2026105 ms
Jun 6, 2026105 ms
Jun 13, 2026107 ms
Jun 20, 2026111 ms
Jun 27, 2026109 ms
Jul 4, 2026109 ms
Jul 11, 2026103 ms
Jul 18, 2026101 ms
Jul 25, 2026103 ms
Aug 1, 2026103 ms
Aug 8, 2026102 ms
Aug 15, 2026104 ms
Aug 22, 2026107 ms
Aug 29, 2026110 ms
Sep 5, 2026115 ms
Sep 12, 2026114 ms
Sep 19, 2026110 ms
Sep 26, 2026109 ms
Oct 3, 2026105 ms
Oct 10, 2026101 ms
Oct 17, 2026108 ms
Oct 24, 2026110 ms
Oct 31, 2026111 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

Full-page screenshot of protym.pl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. protym.pl at 0.5 s0.5 s
  2. protym.pl at 0.9 s0.9 s
  3. protym.pl at 1.4 s1.4 s
  4. protym.pl at 1.9 s1.9 s
  5. protym.pl at 2.4 s2.4 s
  6. protym.pl at 2.8 s2.8 s
  7. protym.pl at 3.3 s3.3 s
  8. protym.pl at 3.8 s3.8 s

Speed

8 to fix56
  • Reduce unused JavaScript

    2.1 s · 423 KiB

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

  • 3,338 HTML elements

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

  • Mobile performance score: 56

    56/100

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

  • Render-blocking requests

    600 ms

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

  • Reduce unused CSS

    300 ms · 48 KiB

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

  • 5 long tasks on the main thread

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

  • Google Tag Manager adds 207 ms

    207 ms

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

  • Main-thread work: 2.5 s

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Hotjar, Google Tag Manager and Shopify and others), adding 673 KiB and 443 ms of main-thread time.

  • Improve image delivery

    250 ms · 79 KiB

    3 images could be 79 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    11 KiB

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

  • 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.

1 checks passed
  • Server response: 30 ms

    30 ms

    Your server sent the HTML in 30 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 9.9 s

    9.9 s

    Your largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “hufgard pt zaprawy techniczne p&t hufgard polska dystrybuto…”.

  • Time to Interactive: 9.9 s

    9.9 s

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

  • Total Blocking Time: 619 ms

    619 ms

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

  • Speed Index: 4.6 s

    4.6 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) got 10% slower for real visitors

    +10%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 112 ms

    112 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 501 ms

    501 ms

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 2.0 MB in 121 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 121 requests on a phone: scripts 937 KiB (35), other files 668 KiB (72) and images 185 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.57 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 7486
  • 51 text elements with low contrast

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

  • Links look like plain text

    18 links inside paragraphs rely on colour alone to stand out.

  • Hidden but focusable

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

  • 7 tap targets too small

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Malformed lists

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

  • Orphan list items

    Some list items are not inside a list.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

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

  • 6 links without text

    6 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.

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

2 checks passed
  • Every image has alt text

    All 56 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9276
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “PROTYM - Sklep online: Chemia budowlana, przemysłowa, maszyny — Protym”.

  • Meta description is long (301 characters)

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

  • 5 links crawlers can't follow

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

  • 258 internal links, 11 external

    The homepage links to 258 pages on protym.pl and 11 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://protym.pl/.

  • Structured data in place

    Structured data found: WebSite.

  • 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://protym.pl/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://protym.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.

2 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 (3,046 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 11 linked pages hidden from search

    https://protym.pl/collections/budownictwo-1/kleje-i-uszczelniacze_wszystkie, https://protym.pl/collections/budownictwo-1/do-hydroizolacji_wszystkie, https://protym.pl/collections/budownictwo-1/do-posadzek_naprawy-betonu, https://protym.pl/collections/budownictwo-1/do-posadzek_posadzki-betonowe, https://protym.pl/collections/budownictwo-1/do-posadzek_posadzki-zywiczne and https://protym.pl/collections/budownictwo-1/kleje-i-uszczelniacze_narzedzia-i-akcesoria and 5 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 1 page without a meta description

    https://protym.pl/policies/shipping-policy has no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages share a meta description

    https://protym.pl/collections/budownictwo-1, https://protym.pl/collections/budownictwo-1/kleje-i-uszczelniacze_wszystkie, https://protym.pl/collections/budownictwo-1/do-hydroizolacji_wszystkie, https://protym.pl/collections/budownictwo-1/do-posadzek_naprawy-betonu, https://protym.pl/collections/budownictwo-1/do-posadzek_posadzki-betonowe and https://protym.pl/collections/budownictwo-1/do-posadzek_posadzki-zywiczne and 1 other use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    14 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    67 of 74 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 1,216 words of copy

    The homepage carries about 1,216 words of visible text.

3 checks passed
  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Hotjar.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 15 other companies contacted

    Loading the homepage contacts 15 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 protym.pl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Local Pickup;Shopify Plus;Shopify POS
Hosting
Shopify

Company

Headquarters
Tarnowo Podgórne

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on protym.pl, including 13 speed issues, 4 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25