Website review, no card needed

espiro.pl logo

espiro.pl website review

Visit site (opens in a new tab)Reviewed 11 November 202636 issues · 87 checks

This review found 36 issues worth fixing on espiro.pl, 9 of them high impact, across 87 checks. The most urgent: render-blocking requests. 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 s986 msMay 23Nov 71.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.6 s
Sep 19, 20261.5 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.1 s
Nov 7, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
165 ms128 msMay 23Nov 7156 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026132 ms
May 30, 2026132 ms
Jun 6, 2026136 ms
Jun 13, 2026138 ms
Jun 20, 2026138 ms
Jun 27, 2026142 ms
Jul 4, 2026143 ms
Jul 11, 2026139 ms
Jul 18, 2026139 ms
Jul 25, 2026138 ms
Aug 1, 2026138 ms
Aug 8, 2026144 ms
Aug 15, 2026148 ms
Aug 22, 2026152 ms
Aug 29, 2026154 ms
Sep 5, 2026152 ms
Sep 12, 2026151 ms
Sep 19, 2026151 ms
Sep 26, 2026153 ms
Oct 3, 2026155 ms
Oct 10, 2026159 ms
Oct 17, 2026161 ms
Oct 24, 2026159 ms
Oct 31, 2026160 ms
Nov 7, 2026156 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 espiro.pl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. espiro.pl at 0.4 s0.4 s
  2. espiro.pl at 0.8 s0.8 s
  3. espiro.pl at 1.2 s1.2 s
  4. espiro.pl at 1.6 s1.6 s
  5. espiro.pl at 2.0 s2.0 s
  6. espiro.pl at 2.4 s2.4 s
  7. espiro.pl at 2.8 s2.8 s
  8. espiro.pl at 3.2 s3.2 s

Speed

7 to fix76
  • Render-blocking requests

    1.6 s

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

  • Improve image delivery

    1.3 MB

    10 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Facebook and Google/Doubleclick Ads and others), adding 998 KiB and 944 ms of main-thread time.

  • Mobile performance score: 76

    76/100

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

  • Google Tag Manager adds 683 ms

    683 ms

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

  • Reduce unused JavaScript

    298 KiB

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

  • Main-thread work: 2.3 s

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

  • 10 long tasks on the main thread

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

  • Use efficient cache lifetimes

    215 KiB

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

  • Reduce unused CSS

    28 KiB

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

  • Legacy JavaScript

    23 KiB

    Polyfills for old browsers add 23 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 126 ms

    126 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 14.2 s

    14.2 s

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

  • Speed Index: 6.4 s

    6.4 s

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

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

    +20%

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

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

  • Total Blocking Time: 386 ms

    386 ms

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

  • 1 image without width and height

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

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: 156 ms

    156 ms

    Real visitors wait 156 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.0 s

    1.0 s

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

  • Real-user TTFB: 462 ms

    462 ms

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

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

    -27%

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

  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

5 to fix43
  • 1 image over 500 KB

    Flame_2000x1080.webp weighs 500 KiB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    640 KiB

    2 images are downloaded at several times the size a phone draws them, for example Flame_2000x1080.webp at 2,000 px wide, shown at 358 px. Resized copies would save about 640 KiB.

  • Page weight: 3.3 MB in 140 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 140 requests on a phone: images 2.2 MB (100), scripts 927 KiB (19) and fonts 177 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    baner_2_(002).jpg 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).

  • 3 images below the first screen load straight away

    3 images further down the page (402 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (208 KiB) is 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.9 g of CO₂ per visit

    0.94 g

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

Accessibility

9 to fixGoogle 8589
  • 24 text elements with low contrast

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

  • Malformed lists

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 4 form fields without a label

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

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

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

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

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

2 checks passed
  • Every image has alt text

    All 134 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 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

4 to fixGoogle 9281
  • No H1 headline

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

  • No structured data

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 122 internal links, 13 external

    The homepage links to 122 pages on espiro.pl and 13 external pages.

5 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Espiro producent ✔️ wózków dziecięcych ✔️ spacerówek ✔️ fotelików samochodowych, ✔️ Łóżeczek, ✔️ Krzesełek. Najwyższa j…”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Espiro - Wózki, Spacerówki, Foteliki, Krzesełka, Łóżeczka”.

  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://espiro.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://espiro.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,495 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://espiro.pl/katalog-espiro-2025,p22.html, whose canonical is https://espiro.pl/katalog-espiro-2026,p22.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

  • Thin social proof

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

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

    The homepage carries about 851 words of visible text.

4 checks passed
  • 1 call to action

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

  • 3 short forms

    3 short forms (3 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 2 cookies set on arrival

    2

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

  • 9 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2024.

Stack

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Atman Sp. z o.o.

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 espiro.pl, including 13 speed issues, 4 SEO issues and 2 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