Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

webinar.ru

МТС Линк — российская экосистема сервисов для бизнес-коммуникаций и совместной работы | Платформа для проведения вебинаров, создания онлайн‑курсов

Page Load Speed

23.4 sec in total

First Response

634 ms

Resources Loaded

21.6 sec

Page Rendered

1.2 sec

webinar.ru screenshot

About Website

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

МТС Линк: проведение совещаний, вебинаров, курсов и мероприятий на платформах Встречи, Вебинары, Курсы и Comdi | Экосистема сервисов для онлайн встреч, совещаний, мероприятий, обучения и вебинаров.

Visit webinar.ru

Key Findings

We analyzed Webinar.ru page load time and found that the first response time was 634 ms and then it took 22.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% 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

webinar.ru performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value7.9 s

22/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

webinar.ru

634 ms

css

83 ms

styles.css

264 ms

device.min.js

252 ms

modernizr.custom.js

253 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 68% of them (64 requests) were addressed to the original Webinar.ru, 4% (4 requests) were made to Analytics.alloka.ru and 3% (3 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Mc.yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (20%)

Content Size

5.1 MB

After Optimization

4.1 MB

In fact, the total size of Webinar.ru main page is 5.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 346.9 kB

  • Original 394.3 kB
  • After minification 385.9 kB
  • After compression 47.3 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 346.9 kB or 88% of the original size.

Image Optimization

-4%

Potential reduce by 173.1 kB

  • Original 4.0 MB
  • After minification 3.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. Webinar images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 367.4 kB

  • Original 542.7 kB
  • After minification 517.5 kB
  • After compression 175.3 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 367.4 kB or 68% of the original size.

CSS Optimization

-86%

Potential reduce by 140.0 kB

  • Original 163.1 kB
  • After minification 133.0 kB
  • After compression 23.2 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. Webinar.ru needs all CSS files to be minified and compressed as it can save up to 140.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (28%)

Requests Now

87

After Optimization

63

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

Accessibility Review

webinar.ru accessibility score

72

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

webinar.ru best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

webinar.ru SEO score

86

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

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webinar.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 Webinar.ru main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Webinar. 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: