Website review, no card needed

yourkaya.pl logo

yourkaya.pl website review

Visit site (opens in a new tab)Reviewed 19 November 202650 issues · 93 checks

This review found 50 issues worth fixing on yourkaya.pl, 21 of them high impact, across 93 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
3.3 s2.7 sMay 30Nov 142.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.9 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20263.0 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.0 s
Aug 29, 20263.0 s
Sep 5, 20263.1 s
Sep 12, 20263.2 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.2 s
Oct 10, 20263.1 s
Oct 17, 20263.1 s
Oct 24, 20263.1 s
Oct 31, 20263.1 s
Nov 7, 20263.1 s
Nov 14, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
207 ms171 msMay 30Nov 14203 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026189 ms
Jun 6, 2026187 ms
Jun 13, 2026180 ms
Jun 20, 2026175 ms
Jun 27, 2026175 ms
Jul 4, 2026179 ms
Jul 11, 2026181 ms
Jul 18, 2026186 ms
Jul 25, 2026188 ms
Aug 1, 2026188 ms
Aug 8, 2026189 ms
Aug 15, 2026189 ms
Aug 22, 2026188 ms
Aug 29, 2026187 ms
Sep 5, 2026184 ms
Sep 12, 2026182 ms
Sep 19, 2026184 ms
Sep 26, 2026184 ms
Oct 3, 2026184 ms
Oct 10, 2026183 ms
Oct 17, 2026188 ms
Oct 24, 2026193 ms
Oct 31, 2026196 ms
Nov 7, 2026198 ms
Nov 14, 2026203 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 yourkaya.pl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. yourkaya.pl at 1.2 s1.2 s
  2. yourkaya.pl at 2.3 s2.3 s
  3. yourkaya.pl at 3.5 s3.5 s
  4. yourkaya.pl at 4.6 s4.6 s
  5. yourkaya.pl at 5.8 s5.8 s
  6. yourkaya.pl at 6.9 s6.9 s
  7. yourkaya.pl at 8.1 s8.1 s
  8. yourkaya.pl at 9.2 s9.2 s

Speed

12 to fix31
  • Render-blocking requests

    1.4 s

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

  • Main-thread work: 11.0 s

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

  • Mobile performance score: 31

    31/100

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

  • 9,164 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, rebuyengine.com and Shopify and others), adding 2.4 MB and 1.3 s of main-thread time.

  • Reduce unused JavaScript

    881 KiB

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

  • Improve image delivery

    500 ms · 236 KiB

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

  • Google Tag Manager adds 579 ms

    579 ms

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

  • 20 long tasks on the main thread

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

  • Use efficient cache lifetimes

    336 KiB

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

  • rebuyengine.com adds 230 ms

    230 ms

    rebuyengine.com costs a phone 230 ms of main-thread work and 731 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.

  • tidio.co adds 79 ms

    79 ms

    tidio.co costs a phone 79 ms of main-thread work and 518 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 CSS

    150 ms · 31 KiB

    About 31 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    50 ms

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

  • Legacy JavaScript

    40 KiB

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

  • Duplicated JavaScript

    26 KiB

    26 KiB JavaScript is shipped twice across bundles.

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

    105 ms

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

Core Web Vitals

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

  • Time to Interactive: 27.9 s

    27.9 s

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

  • Largest Contentful Paint: 7.4 s

    7.4 s

    Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BW”.

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • Speed Index: 7.9 s

    7.9 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user INP: 224 ms

    224 ms

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

  • Real-user CLS: 0.14

    0.14

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

  • Real-user FCP: 2.8 s

    2.8 s

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

  • Cumulative Layout Shift: 0.139

    0.139

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

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

1 checks passed
  • Real-user TTFB: 370 ms

    370 ms

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

Images and page weight

2 to fix69
  • Page weight: 6.4 MB in 323 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 323 requests on a phone: scripts 2.3 MB (115), images 1.0 MB (80) and media 1.0 MB (3). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

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

  • 1 image below the first screen load straight away

    1 image further down the page (26 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.80 g

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

11 to fixGoogle 7687
  • Invalid ARIA attributes

    16 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (4 elements)

    Certain ARIA roles must contain particular children: 4 elements on the page fail this check, rated critical by axe-core.

  • 6 text elements with low contrast

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

  • Unlabelled dropdowns

    4 dropdowns have no label.

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

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

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

    ARIA role should be appropriate for the element: 126 elements on the page fail this check, rated minor 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.

  • Zoom is disabled

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

  • 28 links without text

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

  • 1 form field without a label

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

2 checks passed
  • Every image has alt text

    All 144 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 9 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 9284
  • 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.

  • 6 links crawlers can't follow

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

  • 286 internal links, 0 external

    The homepage links to 286 pages on yourkaya.pl and 0 external pages.

6 checks passed
  • Meta description: 126 characters

    Your meta description is 126 characters: “Cokolwiek potrzebuje Twoja skóra – mamy to. Pielęgnacja dopasowana do każdej potrzeby. Darmowa dostawa od 69 zł w subsk…”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “Your KAYA – odkryj pełną rutynę pielęgnacji ciała”.

  • Canonical URL set

    The canonical URL is https://yourkaya.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://yourkaya.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://yourkaya.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,774 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 5 pages without an H1

    https://yourkaya.pl/pages/o-nas, https://yourkaya.pl/blogs/you-know, https://yourkaya.pl/pages/faq, https://yourkaya.pl/pages/subskrypcja and https://yourkaya.pl/collections/wszystkie-produkty have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://yourkaya.pl/pages/o-nas, https://yourkaya.pl/blogs/you-know, https://yourkaya.pl/pages/faq, https://yourkaya.pl/pages/subskrypcja and https://yourkaya.pl/collections/wszystkie-produkty have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 5 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=27025877&tm=gtm002&Ver=2&mid=c346a21d-1821-41dd-8da7-c95bb798e3be&bo=1&sid=ce4c3a40e44211f18f669b3c62dd5c19&vid=ce4c56b0e44211f1ab11cfdc968f3213&vids=1&msclkid=N&gtm_t.

  • 101 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • 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 2,907 words of copy

    The homepage carries about 2,907 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, Microsoft Clarity, Hotjar and TikTok Pixel.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 34 cookies set on arrival

    34

    Opening the homepage sets 34 cookies, 2 of them by other companies (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.

  • 41 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Shopify

Company

Headquarters
Warszawa

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on yourkaya.pl, including 24 speed issues, 3 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