Website review, no card needed

vanking.pl logo

vanking.pl website review

Visit site (opens in a new tab)Reviewed 31 October 202636 issues · 86 checks

This review found 36 issues worth fixing on vanking.pl, 18 of them high impact, across 86 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
3.4 s2.2 sMay 9Oct 243.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.0 s
May 16, 20263.0 s
May 23, 20263.0 s
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20263.2 s
Jun 20, 20263.1 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20262.9 s
Jul 25, 20263.2 s
Aug 1, 20263.1 s
Aug 8, 20262.9 s
Aug 15, 20262.8 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.7 s
Sep 19, 20263.2 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Oct 17, 20263.0 s
Oct 24, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
115 ms92 msMay 9Oct 24103 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026110 ms
May 16, 2026110 ms
May 23, 2026106 ms
May 30, 2026108 ms
Jun 6, 2026104 ms
Jun 13, 2026107 ms
Jun 20, 2026110 ms
Jun 27, 2026105 ms
Jul 4, 2026104 ms
Jul 11, 2026105 ms
Jul 18, 2026104 ms
Jul 25, 2026110 ms
Aug 1, 2026112 ms
Aug 8, 2026106 ms
Aug 15, 2026103 ms
Aug 22, 202695 ms
Aug 29, 202696 ms
Sep 5, 202696 ms
Sep 12, 2026104 ms
Sep 19, 2026103 ms
Sep 26, 2026101 ms
Oct 3, 2026101 ms
Oct 10, 202698 ms
Oct 17, 2026102 ms
Oct 24, 2026103 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 vanking.pl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. vanking.pl at 1.3 s1.3 s
  2. vanking.pl at 2.7 s2.7 s
  3. vanking.pl at 4.0 s4.0 s
  4. vanking.pl at 5.4 s5.4 s
  5. vanking.pl at 6.7 s6.7 s
  6. vanking.pl at 8.1 s8.1 s
  7. vanking.pl at 9.4 s9.4 s
  8. vanking.pl at 10.8 s10.8 s

Speed

11 to fix43
  • Reduce unused JavaScript

    5.9 s · 894 KiB

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

  • Font display

    3.0 s

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

  • Render-blocking requests

    2.9 s

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

  • Use efficient cache lifetimes

    1.9 s · 367 KiB

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

  • Mobile performance score: 43

    43/100

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

  • Main-thread work: 5.0 s

    A phone's processor spends 5.0 s on main-thread work while loading, 2.6 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 Google Maps and others), adding 2.2 MB and 1.5 s of main-thread time.

  • Google Tag Manager adds 585 ms

    585 ms

    Google Tag Manager costs a phone 585 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.

  • Google CDN adds 452 ms

    452 ms

    Google CDN costs a phone 452 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.

  • Google Maps adds 332 ms

    332 ms

    Google Maps costs a phone 332 ms of main-thread work and 707 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.

  • 2,182 HTML elements

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

  • 18 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 20 KiB

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

  • Reduce unused CSS

    47 KiB

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

  • Minify JavaScript

    15 KiB

    15 KiB could be saved by minifying JavaScript.

  • Improve image delivery

    7 KiB

    1 image could be 7 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

    143 ms

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

Core Web Vitals

9 to fix67
  • 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 FCP: 3.1 s

    3.1 s

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

  • Largest Contentful Paint: 18.1 s

    18.1 s

    Your largest element takes 18.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CZĘŚCI DO BUSÓW W JEDNYM MIEJSCU! Zakup części do samochodó…”.

  • Time to Interactive: 19.3 s

    19.3 s

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

  • Speed Index: 11.6 s

    11.6 s

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

  • Total Blocking Time: 872 ms

    872 ms

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

  • Real-user LCP: 3.8 s

    3.8 s

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

  • 20 images without width and height

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    -7%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

4 checks passed
  • Real-user INP: 111 ms

    111 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user TTFB: 591 ms

    591 ms

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

  • Cumulative Layout Shift: 0.062

    0.062

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

Images and page weight

1 to fix70
  • Page weight: 4.0 MB in 208 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 208 requests on a phone: scripts 2.1 MB (46), images 1.1 MB (96) and other files 369 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.14 g

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

8 to fixGoogle 9191
  • 8 text elements with low contrast

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

  • 3 tap targets too small

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (8 elements)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 11 links without text

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

  • Alternative text of images should not be repeated as text (17 elements)

    Alternative text of images should not be repeated as text: 17 elements on the page fail this check, rated minor by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

3 to fixGoogle 9278
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Hurtownia motoryzacyjna - dystrybutor części samochodowych - VanKing”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Części do busów” and “w jednym miejscu!”). One clear main headline is easier for people and search engines.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 99 internal links, 15 external

    The homepage links to 99 pages on vanking.pl and 15 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • 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://vanking.pl/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

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, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

2 to fix88
  • 2 linked pages hidden from search

    https://vanking.pl/warunki-handlowe and https://vanking.pl/konkursy-i-promocje are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 14 pages without a meta description

    https://vanking.pl/category/aktualnosci, https://vanking.pl/category/nowosci, https://vanking.pl/warunki-handlowe, https://vanking.pl/kariera, https://vanking.pl/o-firmie and https://vanking.pl/konkursy-i-promocje and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages slow to respond

    https://vanking.pl/kontakt, https://vanking.pl/oddzialy, https://vanking.pl/category/blog, https://vanking.pl/en, https://vanking.pl/it and https://vanking.pl/fr and 3 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 61 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.

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    43 of 52 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 961 words of copy

    The homepage carries about 961 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “shop”.

  • 1 call to action

    The homepage has 1 call to action, for example “shop”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

Privacy and tracking

  • 3 trackers load before any consent

    3

    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.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 12 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 vanking.pl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager | Hotjar
Hosting
Cf Krk

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on vanking.pl, including 20 speed issues, 3 SEO issues and 1 conversion gap. 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