Website review, no card needed
tiande.ru website review
Visit site (opens in a new tab)Reviewed 20 November 202635 issues · 64 checks
This review found 35 issues worth fixing on tiande.ru, 14 of them high impact, across 64 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 6.1 s |
| Jun 6, 2026 | 6.1 s |
| Jun 13, 2026 | 5.9 s |
| Jun 20, 2026 | 5.9 s |
| Jun 27, 2026 | 5.8 s |
| Jul 4, 2026 | 5.9 s |
| Jul 11, 2026 | 5.8 s |
| Jul 18, 2026 | 5.7 s |
| Jul 25, 2026 | 5.3 s |
| Aug 1, 2026 | 5.3 s |
| Aug 8, 2026 | 5.5 s |
| Aug 15, 2026 | 5.7 s |
| Aug 22, 2026 | 5.8 s |
| Aug 29, 2026 | 5.7 s |
| Sep 5, 2026 | 5.6 s |
| Sep 12, 2026 | 5.5 s |
| Sep 19, 2026 | 5.4 s |
| Sep 26, 2026 | 5.2 s |
| Oct 3, 2026 | 5.2 s |
| Oct 10, 2026 | 5.1 s |
| Oct 17, 2026 | 5.0 s |
| Oct 24, 2026 | 5.0 s |
| Oct 31, 2026 | 4.9 s |
| Nov 7, 2026 | 4.7 s |
| Nov 14, 2026 | 4.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 395 ms |
| Jun 6, 2026 | 399 ms |
| Jun 13, 2026 | 411 ms |
| Jun 20, 2026 | 420 ms |
| Jun 27, 2026 | 413 ms |
| Jul 4, 2026 | 416 ms |
| Jul 11, 2026 | 427 ms |
| Jul 18, 2026 | 455 ms |
| Jul 25, 2026 | 477 ms |
| Aug 1, 2026 | 517 ms |
| Aug 8, 2026 | 526 ms |
| Aug 15, 2026 | 533 ms |
| Aug 22, 2026 | 528 ms |
| Aug 29, 2026 | 534 ms |
| Sep 5, 2026 | 522 ms |
| Sep 12, 2026 | 524 ms |
| Sep 19, 2026 | 520 ms |
| Sep 26, 2026 | 520 ms |
| Oct 3, 2026 | 520 ms |
| Oct 10, 2026 | 499 ms |
| Oct 17, 2026 | 499 ms |
| Oct 24, 2026 | 475 ms |
| Oct 31, 2026 | 465 ms |
| Nov 7, 2026 | 460 ms |
| Nov 14, 2026 | 451 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
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 4.7 s
4.7 sReal visitors wait 4.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.26
0.26For real visitors the layout shifts by 0.26 (75th percentile). Good is under 0.1.
Real-user FCP: 4.0 s
4.0 sReal visitors see the first content after 4.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.7 s
2.7 sReal visitors wait 2.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Real-user INP: 454 ms
454 msReal visitors wait 454 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 395 ms to 451 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 6.1 s to 4.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 4.4 MB
4.4 MBYour homepage downloads 4.4 MB on a phone, 2.8 MB of it images (62%). Under 2 MB keeps phones on slow connections fast.
About 1.3 g of CO₂ per visit
1.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.26 g of CO₂e: 150.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
20 text elements with low contrast
20 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
<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.
192 images without alt text
192 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate 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.
17 links without text
17 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have 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.
1 checks passed
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 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
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.
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 (173 characters)
Your meta description is 173 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://tiande.ru/sitemap.xml, so Google discovers your pages only by following links.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
124 internal links, 22 external
The homepage links to 124 pages on tiande.ru and 22 external pages.
3 checks passed
Title: 54 characters
Your title is a healthy 54 characters: “Интернет-магазин натуральной косметики TianDe (ТианДе)”.
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.
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.
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
2 pages share a title
https://tiande.ru/catalog/reshenie_problem/morschiny_i_poterya_uprugosti_kozhi_35__80 and https://tiande.ru/catalog/reshenie_problem/obezvozhennaya_kozha_78 all use the title “- купить по выгодной цене в интернет-магазине TianDe (ТианДе)”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://tiande.ru/catalog/reshenie_problem/morschiny_i_poterya_uprugosti_kozhi_35__80 and https://tiande.ru/catalog/reshenie_problem/obezvozhennaya_kozha_78 use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
https://tiande.ru/about-company, https://tiande.ru/business-opportunities, https://tiande.ru/shoppers-new, https://tiande.ru/loyalty_programm, https://tiande.ru/favorites and https://tiande.ru/findSolution have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://tiande.ru/about-company, https://tiande.ru/business-opportunities, https://tiande.ru/shoppers-new, https://tiande.ru/loyalty_programm, https://tiande.ru/favorites and https://tiande.ru/findSolution 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.
2 pages slow to respond
https://tiande.ru/catalog/reshenie_problem/lishniy_ves and https://tiande.ru/catalog/reshenie_problem/morschiny_i_poterya_uprugosti_kozhi_35_ took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 77 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 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 14 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
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_TUNNEL_CONNECTION_FAILED”.
2 checks passed
Tap targets are thumb-sized
41 of 46 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.
Thin social proof
Social proof on the homepage: 2 customer or partner logos. 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.
Only about 96 words
The homepage has only about 96 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
1 checks passed
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
10 other companies contacted
Loading the homepage contacts 10 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 tiande.ru, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on tiande.ru, including 6 speed issues, 6 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.