Website review, no card needed
prostor.ua website review
Visit site (opens in a new tab)Reviewed 25 October 202642 issues · 90 checks
This review found 42 issues worth fixing on prostor.ua, 24 of them high impact, across 90 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
72C- #93,749 of 120,865 reviewed websitesbeats 19%
- #58,136 of 68,427 online storesbeats 12%
- #383 of 716 Magento storesbeats 41%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.7 s |
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 261 ms |
| May 9, 2026 | 264 ms |
| May 16, 2026 | 261 ms |
| May 23, 2026 | 261 ms |
| May 30, 2026 | 258 ms |
| Jun 6, 2026 | 250 ms |
| Jun 13, 2026 | 250 ms |
| Jun 20, 2026 | 232 ms |
| Jun 27, 2026 | 223 ms |
| Jul 4, 2026 | 224 ms |
| Jul 11, 2026 | 223 ms |
| Jul 18, 2026 | 227 ms |
| Jul 25, 2026 | 246 ms |
| Aug 1, 2026 | 244 ms |
| Aug 8, 2026 | 247 ms |
| Aug 15, 2026 | 248 ms |
| Aug 22, 2026 | 248 ms |
| Aug 29, 2026 | 246 ms |
| Sep 5, 2026 | 244 ms |
| Sep 12, 2026 | 242 ms |
| Sep 19, 2026 | 240 ms |
| Sep 26, 2026 | 240 ms |
| Oct 3, 2026 | 238 ms |
| Oct 10, 2026 | 238 ms |
| Oct 17, 2026 | 236 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
Improve image delivery
10.6 s · 5.6 MB29 images could be 5.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 10.6 s faster on a phone.
Render-blocking requests
3.4 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.
Reduce unused JavaScript
1.4 s · 555 KiBAbout 555 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Reduce unused CSS
1.4 s · 241 KiBAbout 241 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 30
30/100Your mobile performance score is 30 (desktop: 54). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.9 s
A phone's processor spends 7.9 s on main-thread work while loading, 4.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,330 HTML elements
The page has 3,330 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 (TikTok, esputnik.com and Facebook and others), adding 510 KiB and 723 ms of main-thread time.
Use efficient cache lifetimes
600 ms · 116 KiB3 files are served with short cache lifetimes, so returning visitors download them again (116 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 607 ms. During a long task the page ignores taps.
Legacy JavaScript
300 ms · 43 KiBPolyfills for old browsers add 43 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
TikTok adds 300 ms
300 msTikTok costs a phone 300 ms of main-thread work and 160 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 7 ms
7 msYour server sent the HTML in 7 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: 24.5 s
24.5 sYour largest element takes 24.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 26.6 s
26.6 sThe page becomes fully interactive after 26.6 s. Good is under 3.8 s.
Speed Index: 11.7 s
11.7 sVisually, the page fills in at 11.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 4.7 s
4.7 sThe first text or image appears after 4.7 s on a phone. Good is under 1.8 s.
Real-user INP: 265 ms
265 msReal visitors wait 265 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
7 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 490 ms
490 msReal visitors wait 490 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 261 ms to 236 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.036
0.036The layout barely moves while loading (CLS 0.036, good is under 0.1).
Images and page weight
Page weight: 9.4 MB in 421 requests
9.4 MBYour homepage downloads 9.4 MB in 421 requests on a phone: images 6.8 MB (66), scripts 1.8 MB (273) and fonts 437 KiB (15). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 3.9 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
2.9 MB5 images are downloaded at several times the size a phone draws them, for example Pink_rabbit_rgb_700_560_1.png at 2,917 px wide, shown at 358 px. Resized copies would save about 2.9 MB.
11 images in older formats
11 images (5.2 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.
An image on the first screen is lazy-loaded
Pink_rabbit_rgb_700_560_1.png 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).
About 2.7 g of CO₂ per visit
2.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.68 g of CO₂e: 321.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
8 buttons without a name
8 buttons have no accessible name, so screen readers announce just “button”.
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.
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 77 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 8 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
460 internal links, 18 external
The homepage links to 460 pages on prostor.ua and 18 external pages.
7 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “【Офіційний інтернет магазин Prostor】Великий асортимент косметики, парфумерії та побутової хімії ✅ Акції, знижки, розпро…”.
One H1 headline
Your main headline reads: “Prostor.ua - Будь собою”.
Title: 47 characters
Your title is a healthy 47 characters: “PROSTOR ❤️ інтернет магазин косметики в Україні”.
Canonical URL set
The canonical URL is https://prostor.ua/.
Structured data in place
Structured data found: OnlineStore.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://prostor.ua/sitemap.xml.
AI search readiness
No llms.txt
There is no https://prostor.ua/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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Other pages
3 linked pages hidden from search
https://prostor.ua/ua/track/order, https://prostor.ua/ua/aktsii/supertseny and https://prostor.ua/ua/podarki/dlya-zhenshchin/dlya-zhinok are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
4 pages without a meta description
https://prostor.ua/ua/pickup-points, https://prostor.ua/ua/track/order, https://prostor.ua/ua/vakansii and https://prostor.ua/ua/aktsii have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://prostor.ua/ua/polzovatelskoe-soglashenie, whose canonical is https://prostor.ua/ua/polzovatelskoe-soglashenie-privacy-policy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
7 pages with very little text
https://prostor.ua/ua/oplata-i-dostavka, https://prostor.ua/ua/prostor-club, https://prostor.ua/ua/vakansii, https://prostor.ua/ua/kontakty, https://prostor.ua/ua/ofitsialnye-pravila-po-priobreteniu-i-ispolzovaniu-podarochnykh-sertifikatov and https://prostor.ua/ua/aktsii and 1 other 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 199 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
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
65 of 77 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.
Only about 149 words
The homepage has only about 149 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
18 short forms
18 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 48 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links 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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.
23 cookies set on arrival
23Opening the homepage sets 23 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.
18 other companies contacted
Loading the homepage contacts 18 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 prostor.ua, 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
- Magento
- 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 42 issues on prostor.ua, including 19 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.