Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

udf.by

Новости Беларуси - последние новости на сегодня - UDF

Page Load Speed

3.4 sec in total

First Response

568 ms

Resources Loaded

2.5 sec

Page Rendered

405 ms

udf.by screenshot

About Website

Click here to check amazing UDF content for Belarus. Otherwise, check out these important facts you probably never knew about udf.by

Новости Республики Беларусь ➤ Обзор новостей с фото и видео ➤ Узнавайте первыми последние белорусские новости на сайте UDF

Visit udf.by

Key Findings

We analyzed Udf.by page load time and found that the first response time was 568 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

udf.by performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

76/100

10%

LCP (Largest Contentful Paint)

Value20.3 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value2,450 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.165

71/100

15%

TTI (Time to Interactive)

Value24.7 s

0/100

10%

Network Requests Diagram

udf.by

568 ms

cloudflare.min.js

21 ms

index.php

413 ms

OneSignalSDK.js

39 ms

css

58 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 74% of them (59 requests) were addressed to the original Udf.by, 5% (4 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Acint.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Udf.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 200.6 kB (18%)

Content Size

1.1 MB

After Optimization

914.4 kB

In fact, the total size of Udf.by main page is 1.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. 45% of websites need less resources to load. Images take 911.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 84.5 kB

  • Original 106.4 kB
  • After minification 106.4 kB
  • After compression 22.0 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 84.5 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 59.1 kB

  • Original 911.3 kB
  • After minification 852.2 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. UDF images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 14.2 kB

  • Original 43.8 kB
  • After minification 43.2 kB
  • After compression 29.7 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 14.2 kB or 32% of the original size.

CSS Optimization

-80%

Potential reduce by 42.9 kB

  • Original 53.4 kB
  • After minification 52.4 kB
  • After compression 10.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. Udf.by needs all CSS files to be minified and compressed as it can save up to 42.9 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (29%)

Requests Now

70

After Optimization

50

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

Accessibility Review

udf.by accessibility score

97

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.

Best Practices

udf.by 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

udf.by SEO score

93

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

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

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Udf.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 Udf.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 UDF. 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: