Website review, no card needed

eobuwie.com.pl logo

eobuwie.com.pl website review

Visit site (opens in a new tab)Reviewed 26 October 202640 issues · 84 checks

This review found 40 issues worth fixing on eobuwie.com.pl, 14 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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.0 s1.8 sMay 9Oct 242.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.9 s
May 16, 20261.9 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
158 ms133 msMay 9Oct 24136 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026155 ms
May 16, 2026153 ms
May 23, 2026154 ms
May 30, 2026153 ms
Jun 6, 2026152 ms
Jun 13, 2026152 ms
Jun 20, 2026151 ms
Jun 27, 2026151 ms
Jul 4, 2026151 ms
Jul 11, 2026150 ms
Jul 18, 2026150 ms
Jul 25, 2026149 ms
Aug 1, 2026148 ms
Aug 8, 2026149 ms
Aug 15, 2026148 ms
Aug 22, 2026147 ms
Aug 29, 2026147 ms
Sep 5, 2026146 ms
Sep 12, 2026146 ms
Sep 19, 2026147 ms
Sep 26, 2026147 ms
Oct 3, 2026146 ms
Oct 10, 2026144 ms
Oct 17, 2026139 ms
Oct 24, 2026136 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 eobuwie.com.pl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. eobuwie.com.pl at 0.8 s0.8 s
  2. eobuwie.com.pl at 1.6 s1.6 s
  3. eobuwie.com.pl at 2.4 s2.4 s
  4. eobuwie.com.pl at 3.2 s3.2 s
  5. eobuwie.com.pl at 4.1 s4.1 s
  6. eobuwie.com.pl at 4.9 s4.9 s
  7. eobuwie.com.pl at 5.7 s5.7 s
  8. eobuwie.com.pl at 6.5 s6.5 s

Speed

8 to fix63
  • Use efficient cache lifetimes

    1.3 s · 1.1 MB

    56 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • Improve image delivery

    750 ms · 494 KiB

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

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63 (desktop: 69). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    683 KiB

    About 683 KiB of JavaScript is downloaded but never used on this page.

  • 13 long tasks on the main thread

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

  • Main-thread work: 3.3 s

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

  • 2,810 HTML elements

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

  • eobuwie.cloud adds 0 ms

    0 ms

    eobuwie.cloud costs a phone 0 ms of main-thread work and 972 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

    150 ms · 65 KiB

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

  • Render-blocking requests

    200 ms

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Cloudflare, Google Tag Manager and eobuwie.cloud), adding 983 KiB and 11 ms of main-thread time.

  • Reduce unused CSS

    22 KiB

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

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

    249 ms

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

Core Web Vitals

9 to fix33
  • 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.

  • Time to Interactive: 14.7 s

    14.7 s

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

  • Total Blocking Time: 961 ms

    961 ms

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

  • Speed Index: 6.3 s

    6.3 s

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

  • Real-user INP: 213 ms

    213 ms

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

  • Real-user CLS: 0.12

    0.12

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

  • Real-user TTFB: 811 ms

    811 ms

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

  • Largest Contentful Paint: 3.3 s

    3.3 s

    Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Zwiększamy rabaty do -30%”.

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

4 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Tap response (INP) got 11% faster for real visitors

    -11%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 155 ms to 136 ms 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).

Images and page weight

2 to fix81
  • Page weight: 2.7 MB in 84 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 84 requests on a phone: scripts 1.5 MB (25), images 974 KiB (31) and HTML 103 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    marketing-hero-component.webp 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).

  • 9 images in older formats

    9 images (349 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.

  • About 0.8 g of CO₂ per visit

    0.76 g

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

1 checks passed
  • 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 7688
  • 5 buttons without a name

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

  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • Orphan list items

    Some list items are not inside a list.

  • 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 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 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 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 75 images in the HTML carry an alt attribute.

  • 47 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: 47 passed and 9 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 10086
  • No H1 headline

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

  • No XML sitemap

    No XML sitemap at https://eobuwie.com.pl/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 578 internal links, 20 external

    The homepage links to 578 pages on eobuwie.com.pl and 20 external pages.

6 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Wybierz modne buty, torebki lub akcesoria spośród 140 000 markowych modeli w atrakcyjnych cenach. Skorzystaj z szybkiej…”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “eobuwie.pl • Modne buty, akcesoria i torebki online”.

  • Canonical URL set

    The canonical URL is https://eobuwie.com.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.

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://eobuwie.com.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 (1,487 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix74
  • 4 linked pages hidden from search

    https://eobuwie.com.pl/c/eobuwie/akcja:fasttrackoctober_lp, https://eobuwie.com.pl/c/campaign-1/plec:damskie-unisex, https://eobuwie.com.pl/c/campaign-1/plec:meskie and https://eobuwie.com.pl/c/campaign-1/plec:dziewczynka-chlopiec are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages share a title

    https://eobuwie.com.pl/c/campaign-1, https://eobuwie.com.pl/c/campaign-1/plec:damskie-unisex, https://eobuwie.com.pl/c/campaign-1/plec:meskie and https://eobuwie.com.pl/c/campaign-1/plec:dziewczynka-chlopiec all use the title “Fall Winter 2026 • oferta eobuwie”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://eobuwie.com.pl/b/sklepy and https://eobuwie.com.pl/b/centrum-pomocy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://eobuwie.com.pl/c/campaign-1, https://eobuwie.com.pl/c/campaign-1/plec:damskie-unisex, https://eobuwie.com.pl/c/campaign-1/plec:meskie and https://eobuwie.com.pl/c/campaign-1/plec:dziewczynka-chlopiec use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://eobuwie.com.pl/b/sklepy and https://eobuwie.com.pl/wishlist have 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 194 found) and read each the way a search engine does.

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

    All 15 pages that loaded have a <title>.

Best practices

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    54 of 59 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 744 words of visible text.

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 eobuwie.com.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
Nuxt

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on eobuwie.com.pl, including 17 speed issues, 2 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