Website review, no card needed

kopalnia.pl logo

kopalnia.pl website review

Visit site (opens in a new tab)Reviewed 18 November 202638 issues · 81 checks

This review found 38 issues worth fixing on kopalnia.pl, 15 of them high impact, across 81 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.7 s2.3 sMay 30Nov 142.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.6 s
Oct 31, 20262.6 s
Nov 7, 20262.6 s
Nov 14, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
315 ms253 msMay 30Nov 14281 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026260 ms
Jun 6, 2026266 ms
Jun 13, 2026270 ms
Jun 20, 2026270 ms
Jun 27, 2026272 ms
Jul 4, 2026275 ms
Jul 11, 2026277 ms
Jul 18, 2026280 ms
Jul 25, 2026283 ms
Aug 1, 2026285 ms
Aug 8, 2026294 ms
Aug 15, 2026301 ms
Aug 22, 2026306 ms
Aug 29, 2026308 ms
Sep 5, 2026302 ms
Sep 12, 2026295 ms
Sep 19, 2026286 ms
Sep 26, 2026280 ms
Oct 3, 2026281 ms
Oct 10, 2026281 ms
Oct 17, 2026283 ms
Oct 24, 2026280 ms
Oct 31, 2026273 ms
Nov 7, 2026278 ms
Nov 14, 2026281 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 kopalnia.pl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kopalnia.pl at 1.0 s1.0 s
  2. kopalnia.pl at 2.0 s2.0 s
  3. kopalnia.pl at 3.0 s3.0 s
  4. kopalnia.pl at 3.9 s3.9 s
  5. kopalnia.pl at 4.9 s4.9 s
  6. kopalnia.pl at 5.9 s5.9 s
  7. kopalnia.pl at 6.9 s6.9 s
  8. kopalnia.pl at 7.9 s7.9 s

Speed

8 to fix32
  • Reduce unused JavaScript

    2.4 s · 812 KiB

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

  • Mobile performance score: 32

    32/100

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

  • Reduce unused CSS

    40 ms · 2.7 MB

    About 2.7 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 40 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, cookiebot.eu and Facebook and others), adding 1.7 MB and 809 ms of main-thread time.

  • Use efficient cache lifetimes

    450 ms · 198 KiB

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

  • Google Tag Manager adds 363 ms

    363 ms

    Google Tag Manager costs a phone 363 ms of main-thread work and 852 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: 3.3 s

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

  • chatlab.com adds 126 ms

    126 ms

    chatlab.com costs a phone 126 ms of main-thread work and 426 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.

  • Render-blocking requests

    250 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.

  • 13 long tasks on the main thread

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

  • Improve image delivery

    57 KiB

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

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need.

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

1 checks passed
  • Server response: 260 ms

    260 ms

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

Core Web Vitals

10 to fix0
  • Fails Core Web Vitals for real visitors

    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-user CLS: 0.36

    0.36

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

  • Largest Contentful Paint: 13.8 s

    13.8 s

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

  • Time to Interactive: 17.3 s

    17.3 s

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

  • Speed Index: 8.7 s

    8.7 s

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

  • Cumulative Layout Shift: 0.436

    0.436

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user INP: 300 ms

    300 ms

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

  • Total Blocking Time: 599 ms

    599 ms

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +6%

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

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

    +11%

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

3 checks passed
  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 681 ms

    681 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

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

Images and page weight

1 to fix85
  • Page weight: 3.0 MB in 108 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 108 requests on a phone: scripts 2.0 MB (39), images 700 KiB (17) and fonts 148 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.85 g

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

7 to fixGoogle 8290
  • Links must have discernible text (12 elements)

    Links must have discernible text: 12 elements on the page fail this check, rated serious by axe-core.

  • 9 text elements with low contrast

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

  • Hidden but focusable

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 1 button without a name

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

  • ARIA role should be appropriate for the element (17 elements)

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Skip links are not focusable.

    Skip links are not focusable. (1 element).

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 10089
  • Title is long (94 characters)

    Your title is 94 characters, so Google will cut it off around 60: “Kopalnia Soli „Wieliczka” – poznaj ciekawe miejsca w Polsce, atrakcje turystyczne w Małop…”.

  • No structured data

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

  • No X (Twitter) card tag

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

  • 118 internal links, 38 external

    The homepage links to 118 pages on kopalnia.pl and 38 external pages.

6 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Masz ochotę na spacer wśród solnych dzieł sztuki? Wybierz Trasę Turystyczną!<br />Wolisz wędrówkę po zakamarkach podzie…”.

  • One H1 headline

    Your main headline reads: “ZabytkowaKopalnia Soli „Wieliczka””.

  • Canonical URL set

    The canonical URL is https://www.kopalnia.pl/.

  • 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://www.kopalnia.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://www.kopalnia.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 (2,060 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 2 pages share a title

    / and https://www.kopalnia.pl/turysta-indywidualny all use the title “Kopalnia Soli „Wieliczka” – poznaj ciekawe miejsca w Polsce, atrakcje…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without an H1

    https://www.kopalnia.pl/kopalnia-sklep-online has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 10 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of undefined (reading 'addEventListener')”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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.

  • Thin social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

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

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

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

1 checks passed
  • 2 short forms

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

Privacy and tracking

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

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Framework
Angular
Hosting
OVHcloud

Company

Founded
1300

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on kopalnia.pl, including 18 speed issues, 2 SEO issues and 5 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