Tools & Wizards About Us
rls.tv screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

rls.tv

Прямой эфир - RLS.TV

Page Load Speed

4.6 sec in total

First Response

49 ms

Resources Loaded

4.2 sec

Page Rendered

281 ms

rls.tv screenshot

About Website

Click here to check amazing RLS content for Russia. Otherwise, check out these important facts you probably never knew about rls.tv

Стримы Новости Прямой эфир круглосуточно Гражданская война на Украине Антимайдан anti-maidan

Visit rls.tv

Key Findings

We analyzed Rls.tv page load time and found that the first response time was 49 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

rls.tv performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value42.3 s

0/100

10%

TBT (Total Blocking Time)

Value95,070 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.367

29/100

15%

TTI (Time to Interactive)

Value114.6 s

0/100

10%

Network Requests Diagram

rls.tv

49 ms

rls.tv

633 ms

am.css

586 ms

css

47 ms

css

64 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 24% of them (21 requests) were addressed to the original Rls.tv, 18% (16 requests) were made to Static.goodgame.ru and 10% (9 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Rls.tv.

Page Optimization Overview & Recommendations

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

Content Size

3.1 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rls.tv main page is 3.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. 55% of websites need less resources to load. Javascripts take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 14.5 kB

  • Original 20.6 kB
  • After minification 20.6 kB
  • After compression 6.1 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 14.5 kB or 71% of the original size.

Image Optimization

-18%

Potential reduce by 25.6 kB

  • Original 138.5 kB
  • After minification 112.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. Obviously, RLS needs image optimization as it can save up to 25.6 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-17%

Potential reduce by 391.7 kB

  • Original 2.2 MB
  • After minification 2.2 MB
  • After compression 1.8 MB

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 391.7 kB or 17% of the original size.

CSS Optimization

-16%

Potential reduce by 120.2 kB

  • Original 730.9 kB
  • After minification 730.9 kB
  • After compression 610.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. Rls.tv needs all CSS files to be minified and compressed as it can save up to 120.2 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (76%)

Requests Now

78

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rls.tv

rls.tv

49 ms

rls.tv

rls.tv

633 ms

am.css

am.css

586 ms

css

css

47 ms

css

css

64 ms

beacon.min.js

beacon.min.js

69 ms

adsbygoogle.js

adsbygoogle.js

160 ms

openapi.c340c125c61ec5745ebb2a98626e46ab.js

openapi.c340c125c61ec5745ebb2a98626e46ab.js

240 ms

cut.png

cut.png

608 ms

index.html

index.html

660 ms

header-shadow120-414.png

header-shadow120-414.png

671 ms

logo_rls-1-67.svg

logo_rls-1-67.svg

698 ms

events-list_big-.svg

events-list_big-.svg

673 ms

search__icon18x18w.svg

search__icon18x18w.svg

680 ms

sprite_section10.png

sprite_section10.png

1191 ms

telegram.png

telegram.png

1265 ms

okicon.png

okicon.png

1256 ms

vkicon.png

vkicon.png

1281 ms

youtubeicon.png

youtubeicon.png

1292 ms

shtorm_favicon.png

shtorm_favicon.png

1309 ms

svW.svg

svW.svg

1805 ms

font

font

323 ms

font

font

406 ms

upload.gif

upload.gif

169 ms

widget_community.php

widget_community.php

332 ms

c9b87c0b00cfff9b37f95b9c8e4eed42

c9b87c0b00cfff9b37f95b9c8e4eed42

907 ms

like_widget.png

like_widget.png

405 ms

widget_comments.php

widget_comments.php

515 ms

subscribe__icons-sprite20.png

subscribe__icons-sprite20.png

1780 ms

widget_comments.php

widget_comments.php

514 ms

hit

hit

549 ms

logo_rls-1other-41.svg

logo_rls-1other-41.svg

1774 ms

top_buttonL.png

top_buttonL.png

1772 ms

top_buttonR.png

top_buttonR.png

1810 ms

bot_button.png

bot_button.png

1849 ms

loader_nav211110173118_3.js

loader_nav211110173118_3.js

476 ms

fonts_cnt.c7a76efe.css

fonts_cnt.c7a76efe.css

731 ms

lite.6d09ff63.css

lite.6d09ff63.css

513 ms

lang3_2.js

lang3_2.js

391 ms

c3d11fba.093082a5.js

c3d11fba.093082a5.js

395 ms

xdm.js

xdm.js

383 ms

base.c26e5b58.css

base.c26e5b58.css

415 ms

lite.bcf10ece3464fec8b554bde483fa2494.js

lite.bcf10ece3464fec8b554bde483fa2494.js

360 ms

hit

hit

136 ms

embed.js

embed.js

771 ms

chat

chat

149 ms

style-new.css

style-new.css

135 ms

style-new.css

style-new.css

1229 ms

fonts.css

fonts.css

733 ms

jquery-1.11.2.js

jquery-1.11.2.js

1108 ms

lib.js

lib.js

731 ms

global.js

global.js

1236 ms

selector.js

selector.js

857 ms

main.1948ff20b514ce104587.js

main.1948ff20b514ce104587.js

1111 ms

polyfills.d58643acfb438fa0649f.js

polyfills.d58643acfb438fa0649f.js

985 ms

runtime.d3dd649403be46172352.js

runtime.d3dd649403be46172352.js

981 ms

vendor.a71de048add24ebb137e.js

vendor.a71de048add24ebb137e.js

1666 ms

libraries.js

libraries.js

1114 ms

ckeditor.js

ckeditor.js

1363 ms

all.js

all.js

1664 ms

addhtml.js

addhtml.js

1369 ms

hls.min.js

hls.min.js

276 ms

__isCandy.js

__isCandy.js

409 ms

css2

css2

19 ms

tag.js

tag.js

928 ms

index.js

index.js

1807 ms

style.7f1047e01d9621e2e3c8.css

style.7f1047e01d9621e2e3c8.css

1185 ms

style-new.css

style-new.css

1346 ms

browsers.png

browsers.png

103 ms

upload.gif

upload.gif

101 ms

code.js

code.js

677 ms

hls.min.js

hls.min.js

1096 ms

__isCandy.js

__isCandy.js

1255 ms

g

g

311 ms

chat_vk_logo.png

chat_vk_logo.png

43 ms

chat_telegram_logo.png

chat_telegram_logo.png

54 ms

chat_facebook_logo.png

chat_facebook_logo.png

43 ms

chat_google_logo.png

chat_google_logo.png

44 ms

no_connection.png

no_connection.png

26 ms

chatbro.woff

chatbro.woff

33 ms

counter

counter

126 ms

dyn-goal-config.js

dyn-goal-config.js

250 ms

counter

counter

371 ms

counter

counter

377 ms

tracker

tracker

132 ms

font

font

8 ms

tracker

tracker

126 ms

tracker

tracker

129 ms

Accessibility Review

rls.tv 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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

rls.tv best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

rls.tv SEO score

58

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

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 Rls.tv 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 Rls.tv 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

rls.tv

Open Graph description is not detected on the main page of RLS. 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: