Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

true.by

Хостинг сайта в Беларуси → VPS, VDS хостинг → Купить SSL сертификат, домены

Page Load Speed

11.2 sec in total

First Response

2.9 sec

Resources Loaded

7.6 sec

Page Rendered

697 ms

true.by screenshot

About Website

Visit true.by now to see the best up-to-date True content for Belarus and also check out these interesting facts you probably never knew about true.by

Хостинг в Беларуси ¤ Купить домен ¤ Хостинг VPS и VDS без ограничения по трафику™ ¤ Тестовый период 7 дней ¤ SSL сертификаты DV/OV/EV

Visit true.by

Key Findings

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

Performance Metrics

true.by performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value23.7 s

0/100

10%

TBT (Total Blocking Time)

Value18,910 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.078

94/100

15%

TTI (Time to Interactive)

Value31.7 s

0/100

10%

Network Requests Diagram

true.by

2905 ms

dcdb7cabd0a29294ee94d86efdf93452.js

470 ms

dcdb7cabd0a29294ee94d86efdf93452.js

754 ms

c16730cb74814fdd9077e2154338dae3.css

640 ms

css

94 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 64% of them (58 requests) were addressed to the original True.by, 14% (13 requests) were made to Embed.tawk.to and 10% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain True.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 96.2 kB (12%)

Content Size

827.2 kB

After Optimization

731.0 kB

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

HTML Optimization

-80%

Potential reduce by 76.8 kB

  • Original 95.8 kB
  • After minification 95.7 kB
  • After compression 19.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 76.8 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 13.0 kB

  • Original 523.9 kB
  • After minification 510.9 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. True images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 6.5 kB

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

Requests Breakdown

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

Requests Now

75

After Optimization

41

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

Accessibility Review

true.by accessibility score

53

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

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

true.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

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

true.by SEO score

81

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

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise True.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 True.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 description is not detected on the main page of True. 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: