Website review, no card needed

1mtkani.ru logo

1mtkani.ru website review

Visit site (opens in a new tab)Reviewed 10 November 202630 issues · 83 checks

This review found 30 issues worth fixing on 1mtkani.ru, 11 of them high impact, across 83 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
941 ms680 msMay 23Nov 7743 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026855 ms
May 30, 2026887 ms
Jun 6, 2026883 ms
Jun 13, 2026871 ms
Jun 20, 2026824 ms
Jun 27, 2026813 ms
Jul 4, 2026890 ms
Jul 11, 2026911 ms
Jul 18, 2026880 ms
Jul 25, 2026848 ms
Aug 1, 2026762 ms
Aug 8, 2026710 ms
Aug 15, 2026714 ms
Aug 22, 2026738 ms
Aug 29, 2026776 ms
Sep 5, 2026811 ms
Sep 12, 2026782 ms
Sep 19, 2026757 ms
Sep 26, 2026780 ms
Oct 3, 2026763 ms
Oct 10, 2026785 ms
Oct 17, 2026808 ms
Oct 24, 2026746 ms
Oct 31, 2026744 ms
Nov 7, 2026743 ms
Real-visitor tap response (INP)75th percentile, phones
174 ms132 msMay 23Nov 7144 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026141 ms
May 30, 2026141 ms
Jun 6, 2026137 ms
Jun 13, 2026145 ms
Jun 20, 2026143 ms
Jun 27, 2026146 ms
Jul 4, 2026165 ms
Jul 11, 2026163 ms
Jul 18, 2026167 ms
Jul 25, 2026169 ms
Aug 1, 2026159 ms
Aug 8, 2026150 ms
Aug 15, 2026149 ms
Aug 22, 2026154 ms
Aug 29, 2026157 ms
Sep 5, 2026164 ms
Sep 12, 2026161 ms
Sep 19, 2026155 ms
Sep 26, 2026157 ms
Oct 3, 2026147 ms
Oct 10, 2026154 ms
Oct 17, 2026156 ms
Oct 24, 2026149 ms
Oct 31, 2026148 ms
Nov 7, 2026144 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

Full-page screenshot of 1mtkani.ru (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 1mtkani.ru at 0.4 s0.4 s
  2. 1mtkani.ru at 0.8 s0.8 s
  3. 1mtkani.ru at 1.1 s1.1 s
  4. 1mtkani.ru at 1.5 s1.5 s
  5. 1mtkani.ru at 1.9 s1.9 s
  6. 1mtkani.ru at 2.3 s2.3 s
  7. 1mtkani.ru at 2.6 s2.6 s
  8. 1mtkani.ru at 3.0 s3.0 s

Speed

5 to fix79
  • Improve image delivery

    1.6 s · 1.2 MB

    30 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

  • Render-blocking requests

    2.0 s

    14 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.

  • Mobile performance score: 79

    79/100

    Your mobile performance score is 79. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    300 ms · 196 KiB

    About 196 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Font display

    450 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Yandex Metrica and top100.ru and others), adding 568 KiB and 281 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 20 KiB

    About 20 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify JavaScript

    150 ms · 5 KiB

    5 KiB could be saved by minifying JavaScript.

  • Minify CSS

    150 ms · 4 KiB

    4 KiB could be saved by minifying CSS.

  • Use efficient cache lifetimes

    147 KiB

    9 files are served with short cache lifetimes, so returning visitors download them again (147 KiB).

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 54 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    25 KiB

    Polyfills for old browsers add 25 KiB JavaScript that modern phones do not need.

  • 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.

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 344 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 4.7 s

    4.7 s

    Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • 41 images without width and height

    41 images have no width and height attributes, so the layout jumps as each one loads.

  • Speed Index: 4.3 s

    4.3 s

    Visually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 4.7 s

    4.7 s

    The page becomes fully interactive after 4.7 s. Good is under 3.8 s.

  • First Contentful Paint: 1.8 s

    1.8 s

    The 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

    +4%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 141 ms to 144 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 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.9 s

    1.9 s

    Real visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.7 s

    1.7 s

    Real visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 582 ms

    582 ms

    Real visitors wait 582 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 15% faster for real visitors

    -15%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.055

    0.055

    The layout barely moves while loading (CLS 0.055, good is under 0.1).

  • Total Blocking Time: 4 ms

    4 ms

    Scripts block the page for only 4 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix68
  • Page weight: 3.2 MB in 89 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 89 requests on a phone: images 2.5 MB (50), scripts 555 KiB (19) and fonts 147 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 30 images in older formats

    30 images (2.4 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.

  • 11 images below the first screen load straight away

    11 images further down the page (519 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.92 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 110.3 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

8 to fixGoogle 6382
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (11 elements)

    All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 29 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 8594
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 5 links crawlers can't follow

    5 links have no real href, so search engines can't follow them.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 188 internal links, 7 external

    The homepage links to 188 pages on 1mtkani.ru and 7 external pages.

6 checks passed
  • Meta description: 106 characters

    Your meta description is 106 characters: “Ткани в розницу и оптом от производителя 1 МЕТР ТКАНИ в Иваново и Москве. Доставка текстиля по всей России”.

  • One H1 headline

    Your main headline reads: “Интернет-магазин тканей”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Купить ткани в розницу и оптом в интернет-магазине 1mtkani.ru”.

  • Canonical URL set

    The canonical URL is https://1mtkani.ru/.

  • 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://1mtkani.ru/sitemap.xml.

AI search readiness

1 to fix88
  • 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://1mtkani.ru/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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (185 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 9 pages with very little text

    https://1mtkani.ru/o-nas, https://1mtkani.ru/dostavka-i-oplata, https://1mtkani.ru/kontakty, https://1mtkani.ru/napolniteli, https://1mtkani.ru/napolniteli/dlya-igrushek-i-podelok and https://1mtkani.ru/napolniteli/sintepon-na-otrez-641 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 69 found) and read each the way a search engine does.

7 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 14 pages that loaded have a meta description.

  • 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 27 small tap targets

    27 of 95 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

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

4 to fix42
  • 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 178 words

    The homepage has only about 178 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.

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and 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.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 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.

  • 12 other companies contacted

    Loading the homepage contacts 12 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 1mtkani.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
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Ooovps As Ooo Vps

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on 1mtkani.ru, including 10 speed issues, 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25