Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

Page Load Speed

34.3 sec in total

First Response

6.1 sec

Resources Loaded

28 sec

Page Rendered

183 ms

mazan.ru screenshot

About Website

Visit mazan.ru now to see the best up-to-date Mazan content and also check out these interesting facts you probably never knew about mazan.ru

Visit mazan.ru

Key Findings

We analyzed Mazan.ru page load time and found that the first response time was 6.1 sec and then it took 28.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

mazan.ru performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value2,150 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

Network Requests Diagram

mazan.ru

6062 ms

mazan.ru

842 ms

all-styles.~E91185.css

507 ms

domain-shop-lot.~8D7636.css

527 ms

shop-widget.~BC12B1.css

394 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Mazan.ru, 37% (18 requests) were made to Reg.ru and 10% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Top-fwz1.mail.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 89.1 kB (56%)

Content Size

159.0 kB

After Optimization

69.9 kB

In fact, the total size of Mazan.ru main page is 159.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. HTML takes 98.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 78.8 kB

  • Original 98.2 kB
  • After minification 84.0 kB
  • After compression 19.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 14.2 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 78.8 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.9 kB
  • After minification 2.9 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Mazan images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 6.0 kB

  • Original 52.1 kB
  • After minification 52.1 kB
  • After compression 46.1 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 6.0 kB or 11% of the original size.

CSS Optimization

-75%

Potential reduce by 4.3 kB

  • Original 5.8 kB
  • After minification 5.8 kB
  • After compression 1.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Mazan.ru needs all CSS files to be minified and compressed as it can save up to 4.3 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (66%)

Requests Now

35

After Optimization

12

The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mazan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

mazan.ru accessibility score

75

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

High

[role]s are not contained by their required parent element

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

mazan.ru best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

mazan.ru SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mazan.ru can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Mazan.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Mazan. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: