Website review, no card needed
51015kids.pl website review
Visit site (opens in a new tab)Reviewed 20 October 202647 issues · 84 checks
This review found 47 issues worth fixing on 51015kids.pl, 23 of them high impact, across 84 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
62DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.5 s |
| May 9, 2026 | 1.5 s |
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 155 ms |
| May 9, 2026 | 158 ms |
| May 16, 2026 | 163 ms |
| May 23, 2026 | 169 ms |
| May 30, 2026 | 173 ms |
| Jun 6, 2026 | 178 ms |
| Jun 13, 2026 | 178 ms |
| Jun 20, 2026 | 178 ms |
| Jun 27, 2026 | 179 ms |
| Jul 4, 2026 | 181 ms |
| Jul 11, 2026 | 187 ms |
| Jul 18, 2026 | 191 ms |
| Jul 25, 2026 | 196 ms |
| Aug 1, 2026 | 199 ms |
| Aug 8, 2026 | 202 ms |
| Aug 15, 2026 | 205 ms |
| Aug 22, 2026 | 203 ms |
| Aug 29, 2026 | 202 ms |
| Sep 5, 2026 | 198 ms |
| Sep 12, 2026 | 197 ms |
| Sep 19, 2026 | 197 ms |
| Sep 26, 2026 | 196 ms |
| Oct 3, 2026 | 196 ms |
| Oct 10, 2026 | 198 ms |
| Oct 17, 2026 | 201 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
How it loaded on a phone
2.1 s
4.1 s
6.2 s
8.3 s
10.3 s
12.4 s
14.5 s
16.5 s
Speed
Improve image delivery
1.8 s · 1.8 MB7 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.
Reduce unused JavaScript
2.7 s · 849 KiBAbout 849 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Use efficient cache lifetimes
2.3 s · 826 KiB46 files are served with short cache lifetimes, so returning visitors download them again (826 KiB).
Render-blocking requests
1.2 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 21
21/100Your mobile performance score is 21 (desktop: 40). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google Maps and fwcdn3.com and others), adding 1.7 MB and 1.3 s of main-thread time.
Google Tag Manager adds 805 ms
805 msGoogle Tag Manager costs a phone 805 ms of main-thread work and 714 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
620 ms · 69 KiBAbout 69 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 620 ms faster on a phone.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Maps adds 194 ms
194 msGoogle Maps costs a phone 194 ms of main-thread work and 386 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 243 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
29 KiB29 KiB could be saved by minifying JavaScript.
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: 136 ms
136 msYour server sent the HTML in 136 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.9 s
13.9 sYour largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 13.6 s
13.6 sVisually, the page fills in at 13.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 17.7 s
17.7 sThe page becomes fully interactive after 17.7 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.556
0.556The layout shifts by 0.556 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Total Blocking Time: 641 ms
641 msScripts block taps and scrolling for 641 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 155 ms to 201 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
40 images without width and height
40 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 171 ms
171 msReal visitors wait 171 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 517 ms
517 msReal visitors wait 517 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 9.1 MB in 94 requests
9.1 MBYour homepage downloads 9.1 MB in 94 requests on a phone: images 7.1 MB (20), scripts 1.8 MB (48) and stylesheets 76 KiB (3). Under 2 MB keeps phones on slow connections fast.
About 2.6 g of CO₂ per visit
2.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.59 g of CO₂e: 310.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
[role]s are not contained by their required parent element
[role]s are not contained by their required parent element (3 elements).
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (2 elements).
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
Headings skip levels
Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
3 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 7 WCAG 2.2 A/AA and best-practice rules on the phone render: 3 passed and 4 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
Meta description is short (40 characters)
Your meta description is only 40 characters: “Oficjalny sklep internetowy marki 51015.”. 70 to 160 characters is enough to sell the click.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://www.51015kids.pl/sitemap.xml, so Google discovers your pages only by following links.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
212 internal links, 10 external
The homepage links to 212 pages on 51015kids.pl and 10 external pages.
3 checks passed
Title: 54 characters
Your title is a healthy 54 characters: “Ubrania i Akcesoria dla Dzieci | Moda dla Najmłodszych”.
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
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://www.51015kids.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.
1 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.
Other pages
11 linked pages are broken
Your homepage links to https://www.51015kids.pl/niemowlak/dziewczynki, https://www.51015kids.pl/niemowlak/dziewczynki/kombinezony-i-kurtki, https://www.51015kids.pl/niemowlak/dziewczynki/body-spiochy, https://www.51015kids.pl/niemowlak/dziewczynki/bluzy, https://www.51015kids.pl/niemowlak/dziewczynki/spodnie-spodnie-dresowe-legginsy and https://www.51015kids.pl/niemowlak/dziewczynki/sukienki-i-spodniczki and 5 others, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages without a meta description
https://www.51015kids.pl/schowek.html and https://www.51015kids.pl/koszyk.html have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.51015kids.pl/nowosci, whose canonical is https://www.51015kids.pl/nowosci,1. 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 181 found) and read each the way a search engine does.
4 checks passed
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 4 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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 418 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Only about 8 words
The homepage has only about 8 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 51015kids.pl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on 51015kids.pl, including 18 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.