Website review, no card needed

100dia.ru logo

100dia.ru website review

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

This review found 30 issues worth fixing on 100dia.ru, 8 of them high impact, across 56 checks. The most urgent: render-blocking requests. 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

Full-page screenshot of 100dia.ru (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 100dia.ru at 0.7 s0.7 s
  2. 100dia.ru at 1.4 s1.4 s
  3. 100dia.ru at 2.1 s2.1 s
  4. 100dia.ru at 2.8 s2.8 s
  5. 100dia.ru at 3.5 s3.5 s
  6. 100dia.ru at 4.2 s4.2 s
  7. 100dia.ru at 4.9 s4.9 s
  8. 100dia.ru at 5.6 s5.6 s

Speed

5 to fix88
  • Render-blocking requests

    2.8 s

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

  • Mobile performance score: 88

    88/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (YouTube, Yandex Metrica and Other Google APIs/SDKs and others), adding 1.2 MB and 570 ms of main-thread time.

  • YouTube adds 503 ms

    503 ms

    YouTube costs a phone 503 ms of main-thread work and 1,016 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.

  • Reduce unused JavaScript

    499 KiB

    About 499 KiB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    150 ms · 145 KiB

    About 145 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.

  • Font display

    250 ms

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

  • 4 long tasks on the main thread

    4 long tasks block the main thread while loading, the longest for 121 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    92 KiB

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

  • 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: 1.7 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

4 to fix94
  • Time to Interactive: 9.5 s

    9.5 s

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

  • Speed Index: 6.0 s

    6.0 s

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

  • Largest Contentful Paint: 2.8 s

    2.8 s

    Your largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “САЙТЫ ДЛЯ БИЗНЕСА. СОЗДАНИЕ РАЗВИТИЕ ПРОДВИЖЕНИЕ ПОДДЕРЖКА”. Most of its time is element render delay (1.9 s).

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 92 ms

    92 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.44 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.44 g of CO₂e: 52.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Page weight: 1.5 MB in 70 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 70 requests on a phone: scripts 1.1 MB (26), fonts 248 KiB (5) and stylesheets 137 KiB (16). That is a lean page.

Accessibility

5 to fixGoogle 6867
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • No main landmark

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 4 automated accessibility rules passed

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

SEO

9 to fixGoogle 9259
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (29 characters)

    Your title is only 29 characters: “Создание и продвижение сайтов”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is short (21 characters)

    Your meta description is only 21 characters: “100dia.ru - Студия.ру”. 70 to 160 characters is enough to sell the click.

  • 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 XML sitemap

    No XML sitemap at https://100dia.ru/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at 100dia.ru/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

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

1 checks passed
  • Canonical URL set

    The canonical URL is https://100dia.ru/.

AI search readiness

1 to fix69
  • 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://100dia.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.

Best practices

Google 92100
  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

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

6 to fix36
  • 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.

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

  • Only about 18 words

    The homepage has only about 18 words of visible text; thin pages give Google and first-time buyers little to go on.

  • 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
  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 1 other company contacted

    Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 100dia.ru, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Hosting
Sprinthost Sprinthost.Ru Llc

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 100dia.ru, including 9 speed issues, 9 SEO issues and 6 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