tsum.ru website review

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

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

About 688 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

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

Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, AdRiver and Yandex Metrica and others), adding 769 KiB and 727 ms of main-thread time.

Google Tag Manager costs a phone 340 ms of main-thread work and 333 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.

A phone's processor spends 3.5 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

Polyfills for old browsers add 69 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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.

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

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

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

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

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

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

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

Scripts block taps and scrolling for 469 ms in total while the page loads. Good is under 200 ms.

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

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

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

Your homepage downloads 42.8 MB in 350 requests on a phone: media 30.0 MB (8), images 10.5 MB (149) and scripts 1.6 MB (35). Under 2 MB keeps phones on slow connections fast.

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

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

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

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

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

Alternative text of images should not be repeated as text: 16 elements on the page fail this check, rated minor by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 90 characters, so Google will cut it off around 60: “Интернет-магазин ЦУМ: одежда, обувь и аксессуары премиум-класса от ведущих мировых брендов”.

The homepage links to 357 pages on tsum.ru and 18 external pages.

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.

https://www.tsum.ru/favorites is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.tsum.ru/favorites has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tsum.ru/brand/gucci.html took over 3 s to send its HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

Large scripts ship without source maps.

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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage carries about 466 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (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 4 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.