Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

zecho.ru

Наружная реклама. Производство и изготовление наружной рекламы в Москве. Рекламное агентство ZECHO

Page Load Speed

13.5 sec in total

First Response

556 ms

Resources Loaded

12.6 sec

Page Rendered

331 ms

zecho.ru screenshot

About Website

Click here to check amazing ZECHO content for Russia. Otherwise, check out these important facts you probably never knew about zecho.ru

Рекламное производственная компания ZECHO работает с 2006 г. и за это время изготовило более 10 000 рекламных вывесок

Visit zecho.ru

Key Findings

We analyzed Zecho.ru page load time and found that the first response time was 556 ms and then it took 13 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

zecho.ru performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value1,690 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.107

88/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

zecho.ru

556 ms

zecho.ru

906 ms

template_styles.css

141 ms

template_styles.css

283 ms

lazyYT.css

408 ms

Our browser made a total of 415 requests to load all elements on the main page. We found that 97% of them (403 requests) were addressed to the original Zecho.ru, 1% (3 requests) were made to Mc.yandex.com and 0% (2 requests) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Zecho.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.8 MB (9%)

Content Size

33.0 MB

After Optimization

30.2 MB

In fact, the total size of Zecho.ru main page is 33.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 32.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 193.7 kB

  • Original 228.6 kB
  • After minification 180.0 kB
  • After compression 34.9 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 48.6 kB, which is 21% 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 193.7 kB or 85% of the original size.

Image Optimization

-8%

Potential reduce by 2.6 MB

  • Original 32.4 MB
  • After minification 29.8 MB

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. ZECHO images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 9.5 kB

  • Original 343.4 kB
  • After minification 343.4 kB
  • After compression 333.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-18%

Potential reduce by 4.6 kB

  • Original 26.1 kB
  • After minification 26.1 kB
  • After compression 21.4 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. Zecho.ru needs all CSS files to be minified and compressed as it can save up to 4.6 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (8%)

Requests Now

408

After Optimization

374

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

Accessibility Review

zecho.ru accessibility score

74

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

zecho.ru best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

zecho.ru SEO score

80

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

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

    RU

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zecho.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Zecho.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 ZECHO. 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: