minjapan.ru website review

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

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

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

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

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

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

6 third-party services load with your homepage (vk.ru, onicon.ru and Google CDN and others), adding 652 KiB and 229 ms of main-thread time.

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

3 KiB JavaScript is shipped twice across bundles.

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

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

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

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

Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Товары из Японии и Кореи”.

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.

Your homepage downloads 3.0 MB in 137 requests on a phone: images 1.7 MB (73), scripts 778 KiB (33) and stylesheets 246 KiB (15). Under 2 MB keeps phones on slow connections fast.

40 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example 7.jpg at 440 px wide, shown at 124 px. Resized copies would save about 33 KiB.

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

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

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

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

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

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

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

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

Your title is 70 characters, so Google will cut it off around 60: “Маленькая Япония японская бытовая химия оптом японская косметика оптом”.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 398 characters; Google truncates after about 160, so the end of your pitch is cut.

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 at https://minjapan.ru/sitemap.927154.xml.gz, so Google discovers your pages only by following links.

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

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

The homepage links to 246 pages on minjapan.ru and 12 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.

There is no https://minjapan.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.

Your homepage links to https://minjapan.ru/push_send, which answers with an error. Visitors hit a dead end and search engines drop it.

https://minjapan.ru/magazin/folder/153149411 took over 3 s to send its HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“`<source src>` with a `<picture>` parent is invalid and therefore ignored. Please use `<source srcs…”).

2 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'addEventListener')”.

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: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your longest form asks for 9 fields (0 required). Every extra field lowers completion.

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 425 words of visible text.

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.

Opening the homepage sets 15 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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.