Website review, no card needed
cosibella.pl website review
Visit site (opens in a new tab)Reviewed 23 October 202639 issues · 88 checks
This review found 39 issues worth fixing on cosibella.pl, 19 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.4 s |
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 219 ms |
| May 9, 2026 | 218 ms |
| May 16, 2026 | 216 ms |
| May 23, 2026 | 213 ms |
| May 30, 2026 | 212 ms |
| Jun 6, 2026 | 212 ms |
| Jun 13, 2026 | 210 ms |
| Jun 20, 2026 | 208 ms |
| Jun 27, 2026 | 210 ms |
| Jul 4, 2026 | 213 ms |
| Jul 11, 2026 | 218 ms |
| Jul 18, 2026 | 219 ms |
| Jul 25, 2026 | 220 ms |
| Aug 1, 2026 | 219 ms |
| Aug 8, 2026 | 221 ms |
| Aug 15, 2026 | 223 ms |
| Aug 22, 2026 | 227 ms |
| Aug 29, 2026 | 228 ms |
| Sep 5, 2026 | 226 ms |
| Sep 12, 2026 | 224 ms |
| Sep 19, 2026 | 222 ms |
| Sep 26, 2026 | 221 ms |
| Oct 3, 2026 | 221 ms |
| Oct 10, 2026 | 223 ms |
| Oct 17, 2026 | 226 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
Speed
Reduce unused JavaScript
2.1 s · 451 KiBAbout 451 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Render-blocking requests
1.6 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 48
48/100Your mobile performance score is 48 (desktop: 65). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,685 HTML elements
The page has 3,685 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
600 ms · 2.1 MB9 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused CSS
300 ms · 42 KiBAbout 42 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 307 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
126 KiB9 files are served with short cache lifetimes, so returning visitors download them again (126 KiB).
5 third-party services on the page
5 third-party services load with your homepage (getzowie.com, ceneo.pl and Google Tag Manager and others), adding 202 KiB and 36 ms of main-thread time.
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: 311 ms
311 msYour server sent the HTML in 311 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 22.2 s
22.2 sYour largest element takes 22.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “10.2026_TrickOrTreat”.
Time to Interactive: 22.8 s
22.8 sThe page becomes fully interactive after 22.8 s. Good is under 3.8 s.
Speed Index: 11.3 s
11.3 sVisually, the page fills in at 11.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 618 ms
618 msScripts block taps and scrolling for 618 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
37 images without width and height
37 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 219 ms to 226 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 180 ms
180 msReal visitors wait 180 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.04
0.04The layout barely moves while loading (CLS 0.04, good is under 0.1).
Images and page weight
Page weight: 4.5 MB in 112 requests
4.5 MBYour homepage downloads 4.5 MB in 112 requests on a phone: images 2.6 MB (50), scripts 1.2 MB (23) and fonts 656 KiB (11). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.
8 images far larger than shown
1.5 MB8 images are downloaded at several times the size a phone draws them, for example Nasze_marki_wlasne.jpg at 3,795 px wide, shown at 272 px. Resized copies would save about 1.5 MB.
7 images below the first screen load straight away
7 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images in older formats
3 images (1.0 MB) 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 1.3 g of CO₂ per visit
1.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.29 g of CO₂e: 154.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
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.
Orphan list items
Some list items are not inside a list.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
2 checks passed
Every image has alt text
All 62 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 6 failed. 3 mores need a person to judge. 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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
852 internal links, 20 external
The homepage links to 852 pages on cosibella.pl and 20 external pages.
7 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Skorzystaj z bezpłatnej porady kosmetologa i dobierz idealną, profesjonalną pielęgnację! W Cosibella czeka 500+ marek i…”.
Title: 56 characters
Your title is a healthy 56 characters: “Drogeria internetowa - pielęgnacja i makijaż | Cosibella”.
Canonical URL set
The canonical URL is https://cosibella.pl/.
Structured data in place
Structured data found: OnlineStore, WebPage and 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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://cosibella.pl/sitemap.xml.gz.
AI search readiness
Parts of the site are closed to 6 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
3 checks passed
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,436 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://cosibella.pl/llms.txt (22 KiB, 44 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://cosibella.pl/pl/newsletter.html has no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://cosibella.pl/pl/menu/makijaz-375, https://cosibella.pl/pl/menu/makijaz/twarz-166, https://cosibella.pl/pl/menu/makijaz/twarz/podklady-175 and https://cosibella.pl/pl/menu/makijaz/twarz/podklady-koreanskie-52657 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 200 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 13 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 13 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://client4460.idosell.com/checkup.php?c=7efc6b2de116a1cea4ee947914cfbac2.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
98 of 111 tappable elements near the top are at least 24 px.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 674 words of copy
The homepage carries about 674 words of visible text.
4 checks passed
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before 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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
6 other companies contacted
Loading the homepage contacts 6 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 cosibella.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 © 2021.
Stack
- Framework
- Tailwind CSS
- 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 39 issues on cosibella.pl, including 17 speed issues, 1 SEO issue 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.