Website review, no card needed

krotoski.com logo

krotoski.com website review

Visit site (opens in a new tab)Reviewed 30 October 202631 issues · 87 checks

This review found 31 issues worth fixing on krotoski.com, 12 of them high impact, across 87 checks. The most urgent: google Tag Manager adds 1.2 s. 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 s1.6 sMay 9Oct 241.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.3 s
Jun 20, 20262.4 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.1 s
Jul 18, 20262.0 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.0 s
Oct 3, 20261.8 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
108 ms91 msMay 9Oct 24106 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202694 ms
May 16, 202693 ms
May 23, 202694 ms
May 30, 202694 ms
Jun 6, 202695 ms
Jun 13, 202696 ms
Jun 20, 202698 ms
Jun 27, 2026100 ms
Jul 4, 2026102 ms
Jul 11, 2026100 ms
Jul 18, 202698 ms
Jul 25, 202698 ms
Aug 1, 2026100 ms
Aug 8, 2026102 ms
Aug 15, 2026104 ms
Aug 22, 2026104 ms
Aug 29, 2026102 ms
Sep 5, 202697 ms
Sep 12, 202696 ms
Sep 19, 202697 ms
Sep 26, 202698 ms
Oct 3, 2026103 ms
Oct 10, 2026104 ms
Oct 17, 2026104 ms
Oct 24, 2026106 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 krotoski.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. krotoski.com at 1.3 s1.3 s
  2. krotoski.com at 2.7 s2.7 s
  3. krotoski.com at 4.0 s4.0 s
  4. krotoski.com at 5.4 s5.4 s
  5. krotoski.com at 6.7 s6.7 s
  6. krotoski.com at 8.0 s8.0 s
  7. krotoski.com at 9.4 s9.4 s
  8. krotoski.com at 10.7 s10.7 s

Speed

10 to fix57
  • Google Tag Manager adds 1.2 s

    1.2 s

    Google Tag Manager costs a phone 1.2 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 5.3 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and consentmanager.net and others), adding 2.4 MB and 2.3 s of main-thread time.

  • Reduce unused JavaScript

    1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page.

  • Mobile performance score: 57

    57/100

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

  • Google CDN adds 494 ms

    494 ms

    Google CDN costs a phone 494 ms of main-thread work and 736 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.

  • consentmanager.net adds 343 ms

    343 ms

    consentmanager.net costs a phone 343 ms of main-thread work and 136 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.

  • Legacy JavaScript

    300 ms · 11 KiB

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

  • 20 long tasks on the main thread

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

  • LiveChat adds 60 ms

    60 ms

    LiveChat costs a phone 60 ms of main-thread work and 365 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.

  • Use efficient cache lifetimes

    99 KiB

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

  • Improve image delivery

    84 KiB

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

  • Reduce unused CSS

    44 KiB

    About 44 KiB of CSS is downloaded but never applied on this page.

  • 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: 20 ms

    20 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 25.3 s

    25.3 s

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

  • Speed Index: 14.8 s

    14.8 s

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

  • Total Blocking Time: 1.5 s

    1.5 s

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

  • Largest Contentful Paint: 3.2 s

    3.2 s

    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 “Grupa Krotoski”. Most of its time is resource load delay (2.2 s).

  • Tap response (INP) got 12% slower for real visitors

    +12%

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

9 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: 1.0 s

    1.0 s

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

  • Real-user INP: 119 ms

    119 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 485 ms

    485 ms

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

  • Largest content (LCP) got 21% faster for real visitors

    -21%

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

  • Cumulative Layout Shift: 0

    0

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

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

Images and page weight

2 to fix81
  • Page weight: 3.9 MB in 135 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 135 requests on a phone: scripts 2.6 MB (62), images 607 KiB (30) and other files 400 KiB (30). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    image 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).

  • About 1.1 g of CO₂ per visit

    1.10 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

6 to fixGoogle 8590
  • 10 buttons without a name

    10 buttons have no accessible name, so screen readers announce just “button”.

  • 8 tap targets too small

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

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

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

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

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 41 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 10087
  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (170 characters)

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

  • Structured data has 1 problem

    Structured data found (AutoDealer) but with 1 problem, for example “AutoDealer: image is not an absolute URL ("https://www.krotoski.com/_next/static/media/logo.80869f7b.svg")”.

  • 108 internal links, 7 external

    The homepage links to 108 pages on krotoski.com and 7 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Autoryzowany dealer renomowanych marek samochodowych, w tym Audi, Porsche, Volkswagen, Skoda, Cupra, MG i BYD.”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Grupa KROTOSKI - dealer samochodów osobowych i dostawczych”.

  • 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.krotoski.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.krotoski.com/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.

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (539 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 2 pages share a title

    https://www.krotoski.com/samochody-nowe/volkswagen and https://www.krotoski.com/samochody-nowe/volkswagen-dostawcze all use the title “Nowe samochody VOLKSWAGEN | Grupa Krotoski”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.krotoski.com/samochody-nowe/volkswagen and https://www.krotoski.com/samochody-nowe/volkswagen-dostawcze use the same meta description. A description written for each page earns more clicks.

  • 4 pages slow to respond

    https://www.krotoski.com/samochody-nowe, https://www.krotoski.com/samochody-nowe/audi, https://www.krotoski.com/samochody-nowe/cupra and https://www.krotoski.com/samochody-nowe/volkswagen took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

1 to fixGoogle 9293
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    31 of 38 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No opening hours

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 337 words of visible text.

4 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 4 trackers load before any consent

    4

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

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies, 4 of them by other companies (measured from a US location before any click).

  • 20 other companies contacted

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

1 checks passed
  • Consent tool: consentmanager

    A consent management tool (consentmanager) loads with the page.

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

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager
Hosting
Eco Atman Pl Eco Atman

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on krotoski.com, including 14 speed issues, 3 SEO issues and 3 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