Report Summary

  • 16

    Performance

    Renders faster than
    31% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 70% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

energobelarus.by

ЭнергоБеларусь - энергетика и энергосбережение Беларуси, новости отрасли

Page Load Speed

15.2 sec in total

First Response

1 sec

Resources Loaded

13.7 sec

Page Rendered

451 ms

energobelarus.by screenshot

About Website

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

Отраслевой информационно-аналитический портал, посвящённый энергетике Беларуси. Актуальные новости и события. Подробная информация о компаниях, товары и услуги.

Visit energobelarus.by

Key Findings

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

energobelarus.by performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value18.4 s

0/100

10%

TBT (Total Blocking Time)

Value3,030 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value27.2 s

0/100

10%

Network Requests Diagram

energobelarus.by

1039 ms

jquery-1.7.2.min.js

421 ms

jsapi

115 ms

page_88e6f4c8ae48685373f0907501786533.css

276 ms

template_f86edecc01566de9d02fedb5cb4d0b35.css

622 ms

Our browser made a total of 221 requests to load all elements on the main page. We found that 75% of them (165 requests) were addressed to the original Energobelarus.by, 5% (11 requests) were made to Vk.com and 4% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Energobelarus.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 799.6 kB (37%)

Content Size

2.2 MB

After Optimization

1.4 MB

In fact, the total size of Energobelarus.by main page is 2.2 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. 65% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 289.5 kB

  • Original 347.2 kB
  • After minification 276.1 kB
  • After compression 57.7 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 71.1 kB, which is 20% 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 289.5 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 71.8 kB

  • Original 1.2 MB
  • After minification 1.1 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. Energobelarus images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 240.5 kB

  • Original 382.6 kB
  • After minification 324.2 kB
  • After compression 142.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 240.5 kB or 63% of the original size.

CSS Optimization

-77%

Potential reduce by 197.8 kB

  • Original 256.3 kB
  • After minification 223.9 kB
  • After compression 58.6 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. Energobelarus.by needs all CSS files to be minified and compressed as it can save up to 197.8 kB or 77% of the original size.

Requests Breakdown

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

Requests Now

212

After Optimization

162

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

Accessibility Review

energobelarus.by accessibility score

88

Accessibility Issues

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.

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

Best Practices

energobelarus.by best practices score

58

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

High

Serves images with low resolution

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

energobelarus.by SEO score

83

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 Energobelarus.by 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 Energobelarus.by 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 Energobelarus. 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: