moex.com website review

48 files are served with short cache lifetimes, so returning visitors download them again (5.4 MB).

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 15.4 s.

The page has 3,033 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 2.9 MB of CSS is downloaded but never applied on this page.

About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

The HTML itself could arrive about 950 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 938 ms on a phone.

Your server takes 1.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

Yandex CDN costs a phone 60 ms of main-thread work and 297 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.

5 third-party services load with your homepage (Yandex CDN, Yandex Metrica and yandex.ru and others), adding 611 KiB and 223 ms of main-thread time.

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

3 images could be 24 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 visitors wait 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

Your largest element takes 4.1 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 (6.2 s).

Real visitors wait 371 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 8.5 MB in 72 requests on a phone: stylesheets 3.0 MB (1), media 2.5 MB (1) and scripts 2.4 MB (26). Under 2 MB keeps phones on slow connections fast.

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

[role] values are not valid (32 elements).

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

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

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

4 visible links have no text or label, so screen readers cannot say where they go.

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

1 link inside paragraphs relies on colour alone to stand out.

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

Headings skip levels (h3 → h6, h2 → h5 and h1 → h6), which makes the page harder to scan with a screen reader.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

There is no robots.txt at moex.com/robots.txt, the first file search crawlers ask for.

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

The homepage links to 172 pages on moex.com and 27 external pages.

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.

/ru/spfi/protsentnye-derivativy has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example /ru/obligatsii, whose canonical is /ru/bonds. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/kak-sohranit-dostup-k-servisam-birzhi, /fyuchersy-na-bitkoin-i-efir-vash-dostup-k-kripte-uzhe-sejchas, /ru/derivatives/perpetual-futures, /ru/gold-moex and /ru/spfi/protsentnye-derivativy have no <h1> headline, so visitors and search engines get no clear main topic.

/ru/spfi/protsentnye-derivativy, /ru/index/IMOEX, /ru/index/IMOEX2, /ru/index/RTSI and /ru/index/MOEXBMI 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.

/ru/obligatsii, /ru/funds, /fyuchersy-na-bitkoin-i-efir-vash-dostup-k-kripte-uzhe-sejchas and /ru/derivatives/perpetual-futures took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

Your certificate from ZeroSSL GmbH · ZeroSSL RSA DV SSL CA 2 expires in 8 days. If it doesn't renew automatically, visitors get a security warning.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

moex.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

moex.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads 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.

Opening the homepage sets 5 cookies (measured from a US location before any click).

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.

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