Tools & Wizards About Us

Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

telo.by

Telo.by - телесная терапия. Биолокация. Энергоинформационная многомерная медицина. Массаж.

Page Load Speed

3.5 sec in total

First Response

908 ms

Resources Loaded

2.1 sec

Page Rendered

543 ms

About Website

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

Telo.by - информационный сайт о телесной терапии, методиках и техниках работы с телом. Практическая биолокация. Энергоинформационная многомерная медицина. Массаж. Целительство.

Visit telo.by

Key Findings

We analyzed Telo.by page load time and found that the first response time was 908 ms and then it took 2.6 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

telo.by performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.6 s

98/100

10%

Network Requests Diagram

telo.by

908 ms

default.css

264 ms

ajax.js

261 ms

top100.jcn

383 ms

therapyby_logo.jpg

619 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 74% of them (29 requests) were addressed to the original Telo.by, 8% (3 requests) were made to Counter.yadro.ru and 5% (2 requests) were made to Counter.rambler.ru. The less responsive or slowest element that took the longest time to load (920 ms) belongs to the original domain Telo.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 102.7 kB (20%)

Content Size

501.5 kB

After Optimization

398.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 101.2 kB

  • Original 122.8 kB
  • After minification 98.9 kB
  • After compression 21.6 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 23.9 kB, which is 19% 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 101.2 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 250 B

  • Original 334.8 kB
  • After minification 334.5 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. Telo images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 705 B

  • Original 39.7 kB
  • After minification 39.7 kB
  • After compression 39.0 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

-13%

Potential reduce by 559 B

  • Original 4.2 kB
  • After minification 4.2 kB
  • After compression 3.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. Telo.by needs all CSS files to be minified and compressed as it can save up to 559 B or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (32%)

Requests Now

28

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

telo.by accessibility score

77

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

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

Best Practices

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

High

Browser errors were logged to the console

SEO Factors

telo.by SEO score

77

Search Engine Optimization Advices

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 Telo.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 Telo.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 Telo. 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: