Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

212.by

Новости Витебской области: Витебск, Орша, Полоцк, Новополоцк

Page Load Speed

24 sec in total

First Response

1.7 sec

Resources Loaded

22 sec

Page Rendered

255 ms

212.by screenshot

About Website

Welcome to 212.by homepage info - get ready to check 212 best content for Belarus right away, or after learning these important things about 212.by

Новости Витебской области: Витебск, Орша, Полоцк, Новополоцк, Поставы, Верхнедвинск, Браслав, Новолукомль

Visit 212.by

Key Findings

We analyzed 212.by page load time and found that the first response time was 1.7 sec and then it took 22.2 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

212.by performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

95/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.043

99/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

212.by

1749 ms

zp.js

703 ms

style.css

286 ms

style.min.css

420 ms

pagenavi-css.css

285 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 50% of them (16 requests) were addressed to the original 212.by, 13% (4 requests) were made to W.uptolike.com and 6% (2 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Adobe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 91.7 kB (43%)

Content Size

214.7 kB

After Optimization

123.0 kB

In fact, the total size of 212.by main page is 214.7 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. 30% of websites need less resources to load. Javascripts take 86.7 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 54.5 kB

  • Original 72.3 kB
  • After minification 69.7 kB
  • After compression 17.8 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 54.5 kB or 75% of the original size.

Image Optimization

-98%

Potential reduce by 31.2 kB

  • Original 31.9 kB
  • After minification 720 B

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. Obviously, 212 needs image optimization as it can save up to 31.2 kB or 98% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 72 B

  • Original 86.7 kB
  • After minification 86.7 kB
  • After compression 86.6 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

-25%

Potential reduce by 5.9 kB

  • Original 23.8 kB
  • After minification 23.8 kB
  • After compression 17.8 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. 212.by needs all CSS files to be minified and compressed as it can save up to 5.9 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (26%)

Requests Now

23

After Optimization

17

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

Accessibility Review

212.by accessibility score

92

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Best Practices

212.by best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

212.by SEO score

71

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Document uses plugins

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 212.by can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that 212.by 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 data is detected on the main page of 212. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: