Website review, no card needed
fix-price.com website review
Visit site (opens in a new tab)Reviewed 31 October 202649 issues · 87 checks
This review found 49 issues worth fixing on fix-price.com, 23 of them high impact, across 87 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
55FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 7.1 s |
| May 16, 2026 | 7.0 s |
| May 23, 2026 | 6.9 s |
| May 30, 2026 | 6.6 s |
| Jun 6, 2026 | 6.5 s |
| Jun 13, 2026 | 6.5 s |
| Jun 20, 2026 | 6.4 s |
| Jun 27, 2026 | 6.4 s |
| Jul 4, 2026 | 6.5 s |
| Jul 11, 2026 | 6.3 s |
| Jul 18, 2026 | 6.3 s |
| Jul 25, 2026 | 6.2 s |
| Aug 1, 2026 | 6.0 s |
| Aug 8, 2026 | 6.0 s |
| Aug 15, 2026 | 5.9 s |
| Aug 22, 2026 | 5.9 s |
| Aug 29, 2026 | 6.0 s |
| Sep 5, 2026 | 6.2 s |
| Sep 12, 2026 | 6.4 s |
| Sep 19, 2026 | 6.6 s |
| Sep 26, 2026 | 6.7 s |
| Oct 3, 2026 | 7.1 s |
| Oct 10, 2026 | 7.8 s |
| Oct 17, 2026 | 7.6 s |
| Oct 24, 2026 | 7.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 293 ms |
| May 16, 2026 | 291 ms |
| May 23, 2026 | 293 ms |
| May 30, 2026 | 305 ms |
| Jun 6, 2026 | 317 ms |
| Jun 13, 2026 | 330 ms |
| Jun 20, 2026 | 341 ms |
| Jun 27, 2026 | 341 ms |
| Jul 4, 2026 | 342 ms |
| Jul 11, 2026 | 338 ms |
| Jul 18, 2026 | 337 ms |
| Jul 25, 2026 | 339 ms |
| Aug 1, 2026 | 345 ms |
| Aug 8, 2026 | 353 ms |
| Aug 15, 2026 | 357 ms |
| Aug 22, 2026 | 355 ms |
| Aug 29, 2026 | 343 ms |
| Sep 5, 2026 | 330 ms |
| Sep 12, 2026 | 318 ms |
| Sep 19, 2026 | 306 ms |
| Sep 26, 2026 | 296 ms |
| Oct 3, 2026 | 284 ms |
| Oct 10, 2026 | 278 ms |
| Oct 17, 2026 | 270 ms |
| Oct 24, 2026 | 265 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
1.5 s
3.0 s
4.5 s
5.9 s
7.4 s
8.9 s
10.4 s
11.9 s
Speed
Reduce unused JavaScript
4.8 s · 1,022 KiBAbout 1,022 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.8 s faster on a phone.
Improve image delivery
1.8 s · 2.8 MB87 images could be 2.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.
Use efficient cache lifetimes
1.6 s · 1.0 MB198 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.0 s
A phone's processor spends 7.0 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,387 HTML elements
The page has 3,387 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 522 ms. During a long task the page ignores taps.
Yandex CDN adds 172 ms
172 msYandex CDN costs a phone 172 ms of main-thread work and 697 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.
8 third-party services on the page
8 third-party services load with your homepage (Yandex CDN, Yandex Metrica and mail.ru and others), adding 972 KiB and 446 ms of main-thread time.
Legacy JavaScript
150 ms · 54 KiBPolyfills for old browsers add 54 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page.
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: 414 ms
414 msYour server sent the HTML in 414 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.
Real-user LCP: 8.2 s
8.2 sReal visitors wait 8.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.95
0.95For real visitors the layout shifts by 0.95 (75th percentile). Good is under 0.1.
Real-user TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 24.9 s
24.9 sYour largest element takes 24.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Будьте в плюсе по-настоящему!”.
Time to Interactive: 25.8 s
25.8 sThe page becomes fully interactive after 25.8 s. Good is under 3.8 s.
Speed Index: 13.7 s
13.7 sVisually, the page fills in at 13.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.5 s
1.5 sScripts block taps and scrolling for 1.5 s in total while the page loads. Good is under 200 ms.
Real-user INP: 328 ms
328 msReal visitors wait 328 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
65 images without width and height
65 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 293 ms to 265 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 7.1 s to 7.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.2 MB in 287 requests
6.2 MBYour homepage downloads 6.2 MB in 287 requests on a phone: images 4.0 MB (169), scripts 1.9 MB (52) and HTML 133 KiB (1). Under 2 MB keeps phones on slow connections fast.
21 images in older formats
21 images (1.8 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.
25 images below the first screen load straight away
25 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.8 g of CO₂ per visit
1.76 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.76 g of CO₂e: 211.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
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.
89 buttons without a name
89 buttons have no accessible name, so screen readers announce just “button”.
81 images without alt text
81 images have no alt text, which hurts accessibility and image search.
[role]s do not have all required [aria-*] attributes
[role]s do not have all required [aria-*] attributes (1 element).
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.
15 tap targets too small
15 tap targets are too small or too close together to hit reliably with a finger.
ARIA toggle fields do not have accessible names
ARIA toggle fields do not have accessible names (1 element).
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Elements with role="none" or role="presentation" have conflicts
Elements with role="none" or role="presentation" have conflicts (18 elements).
1 checks passed
8 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 12 WCAG 2.2 A/AA and best-practice rules on the phone render: 8 passed and 4 failed. 2 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.
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Интернет-магазин Fix Price - магазин низких цен, всё по одной цене”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (195 characters)
Your meta description is 195 characters; Google truncates after about 160, so the end of your pitch is cut.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
220 internal links, 22 external
The homepage links to 220 pages on fix-price.com and 22 external pages.
3 checks passed
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://fix-price.com/sitemap_index.xml.
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.
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.
llms.txt published
The site publishes https://fix-price.com/llms.txt (8 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a title
https://fix-price.com/bonus and https://fix-price.com/fix-plus have no <title>, so Google invents the link text in results.
4 pages without a meta description
https://fix-price.com/bonus, https://fix-price.com/specials, https://fix-price.com/fix-plus and https://fix-price.com/specials/1213 have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://fix-price.com/bonus, https://fix-price.com/fix-plus and https://fix-price.com/specials/1213 have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages with very little text
https://fix-price.com/catalog, https://fix-price.com/bonus, https://fix-price.com/specials, https://fix-price.com/fix-plus, https://fix-price.com/catalog/magiya-halloween and https://fix-price.com/catalog/uyutnaya-osen and 3 others 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.
4 pages slow to respond
https://fix-price.com/fix-plus, https://fix-price.com/catalog/produkty-i-napitki/p-1704134-kofe-rastvorimyy-sublimirovannyy-offee-150-g, https://fix-price.com/specials/1213 and https://fix-price.com/catalog/kollektsiya-aksessuarov-dlya-volos took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 110 found) and read each the way a search engine does.
4 checks passed
Linked pages load
9 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.
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.
Best practices
6 distorted images
6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Requests the notification permission on page load
Requests the notification permission on page load.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Thin social proof
Social proof on the homepage: 60 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 315 words of copy
The homepage carries about 315 words of visible text.
1 checks passed
1 short form
A short form (2 fields at most) is right on the homepage.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Yandex Metrica (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.
11 other companies contacted
Loading the homepage contacts 11 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 fix-price.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- Hosting
- VK
Company
- Founded
- 2007
- Headquarters
- Kazakhstan
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on fix-price.com, including 19 speed issues, 5 SEO issues and 5 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.