Website review, no card needed

molchcom.ru logo

molchcom.ru website review

Visit site (opens in a new tab)Reviewed 10 November 202639 issues · 75 checks

This review found 39 issues worth fixing on molchcom.ru, 15 of them high impact, across 75 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

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

How it loaded on a phone

  1. molchcom.ru at 1.5 s1.5 s
  2. molchcom.ru at 3.1 s3.1 s
  3. molchcom.ru at 4.6 s4.6 s
  4. molchcom.ru at 6.2 s6.2 s
  5. molchcom.ru at 7.7 s7.7 s
  6. molchcom.ru at 9.3 s9.3 s
  7. molchcom.ru at 10.8 s10.8 s
  8. molchcom.ru at 12.3 s12.3 s

Speed

7 to fix56
  • Improve image delivery

    8.0 s · 3.0 MB

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

  • Render-blocking requests

    2.6 s

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

  • Use efficient cache lifetimes

    1.3 s · 534 KiB

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

  • Mobile performance score: 56

    56/100

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

  • Reduce unused CSS

    450 ms · 248 KiB

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

  • Reduce unused JavaScript

    300 ms · 379 KiB

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

  • ppdu.ru adds 133 ms

    133 ms

    ppdu.ru costs a phone 133 ms of main-thread work and 493 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 (ppdu.ru, webvisor.org and Yandex Metrica and others), adding 739 KiB and 347 ms of main-thread time.

  • Minify CSS

    150 ms · 9 KiB

    9 KiB could be saved by minifying CSS.

  • Font display

    150 ms

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

  • 4 long tasks on the main thread

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

  • Minify JavaScript

    26 KiB

    26 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    23 KiB

    23 KiB JavaScript is shipped twice across bundles.

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

    A phone's processor spends 1.1 s on main-thread work while loading, 497 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

6 to fix55
  • Largest Contentful Paint: 13.1 s

    13.1 s

    Your largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MolchCom.ru Кнопка Открыть Почтовый Менеджер”.

  • Time to Interactive: 17.2 s

    17.2 s

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

  • Speed Index: 8.5 s

    8.5 s

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

  • Cumulative Layout Shift: 0.188

    0.188

    The layout shifts by 0.188 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 17 images without width and height

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

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

1 checks passed
  • Total Blocking Time: 69 ms

    69 ms

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

Images and page weight

4 to fix35
  • Page weight: 4.3 MB in 72 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 72 requests on a phone: images 3.3 MB (25), scripts 654 KiB (15) and stylesheets 261 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    molchcom.ru_Ground_Zag_Favi_Logo.jpg weighs 601 KiB. On a phone connection a single image that size takes seconds.

  • 3 images in older formats

    3 images (904 KiB) 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.

  • 2 images far larger than shown

    291 KiB

    2 images are downloaded at several times the size a phone draws them, for example qJ1OUBpOuLaszhaxW0PR7moTo76eUiaX3c2c-5ZIwta-7ikMgVjLAsRtNa0o at 1,440 px wide, shown at 46 px. Resized copies would save about 291 KiB.

  • About 1.2 g of CO₂ per visit

    1.22 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 8692
  • Certain ARIA roles must be contained by particular parents (1 element)

    Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • Frames without titles

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

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • Headings skip levels

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

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 8592
  • No XML sitemap

    No XML sitemap at https://molchcom.ru/molchcom-ru-trudam.txt, so Google discovers your pages only by following links.

  • Only 4 internal links

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

7 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “«Валютный Информатор» - понадобится начинающим и экспертам рынка ценных бумаг и финансовых вложения. Здесь свой человек…”.

  • One H1 headline

    Your main headline reads: “» Валютный Информатор »: Более Чем Просто”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “» Валютный Информатор »: Более Чем Просто”.

  • Canonical URL set

    The canonical URL is https://molchcom.ru/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • 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

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

3 to fix71
  • 1 page without a title

    https://molchcom.ru/Download-Free-Reyting-TOP-3-nabirayushchih-oboroty-razshireniya-Valyutniy-informator.txt.torrent has no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://molchcom.ru/Download-Free-Reyting-TOP-3-nabirayushchih-oboroty-razshireniya-Valyutniy-informator.txt.torrent has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://molchcom.ru/Download-Free-Reyting-TOP-3-nabirayushchih-oboroty-razshireniya-Valyutniy-informator.txt.torrent has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 internal page checked

    We fetched 1 page linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 1 page we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 7385
  • 16 small tap targets

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

  • 4 third-party cookies

    4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://fonts.googleapis.com/css?family=ABeeZee%3Aital%400%3B1%7CAbril%20Fatface%7CAcme%7C…”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

7 to fix50
  • 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 map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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 11 words

    The homepage has only about 11 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 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
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

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

  • 22 other companies contacted

    Loading the homepage contacts 22 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 molchcom.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 39 issues on molchcom.ru, including 13 speed issues, 3 SEO issues and 7 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