4.7 sec in total
685 ms
3.9 sec
164 ms
Welcome to live.err.ee homepage info - get ready to check Live Err best content for Estonia right away, or after learning these important things about live.err.ee
Eesti Rahvusringhäälingu programmid
Visit live.err.eeWe analyzed Live.err.ee page load time and found that the first response time was 685 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
live.err.ee performance score
name
value
score
weighting
Value11.5 s
0/100
10%
Value15.0 s
0/100
25%
Value11.6 s
5/100
10%
Value1,120 ms
23/100
30%
Value0.248
50/100
15%
Value14.1 s
9/100
10%
685 ms
344 ms
322 ms
574 ms
322 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 55% of them (37 requests) were addressed to the original Live.err.ee, 13% (9 requests) were made to Ee30481.err.ee and 6% (4 requests) were made to Ext.err.ee. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Err.spring-tns.net.
Page size can be reduced by 526.9 kB (66%)
794.7 kB
267.8 kB
In fact, the total size of Live.err.ee main page is 794.7 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. 40% of websites need less resources to load. Javascripts take 660.3 kB which makes up the majority of the site volume.
Potential reduce by 40.9 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 40.9 kB or 69% of the original size.
Potential reduce by 5.0 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, Live Err needs image optimization as it can save up to 5.0 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 435.4 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 435.4 kB or 66% of the original size.
Potential reduce by 45.7 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. Live.err.ee needs all CSS files to be minified and compressed as it can save up to 45.7 kB or 82% of the original size.
Number of requests can be reduced by 44 (71%)
62
18
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Live Err. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
live.err.ee
685 ms
344 ms
_styles.css
322 ms
_styles_screen.css
574 ms
otse.css
322 ms
jquery-1_4_2_min.js
670 ms
_errDomainMenu.css
429 ms
jquery-ui.min.js
35 ms
jquery.scrollTo-1.4.2-min.js
33 ms
swfobject.js
42 ms
flowplayer-3-12-12.js
451 ms
otse.js
456 ms
ScheduleJavaScripts.js
632 ms
_errDomainMenu.js
514 ms
ParsedQuerystring.js
463 ms
jquery_timeout.js
471 ms
otseStreamSelect.js
516 ms
springstreams.js
605 ms
addthis_widget.js
15 ms
spring.js
490 ms
ga.js
20 ms
sm-plus.gif
12 ms
bg_header.png
134 ms
logo.png
133 ms
bg_header_links.png
130 ms
bg_search_button.png
131 ms
ico_reply.png
131 ms
ico_bookmark.png
129 ms
email_16.png
214 ms
twitter_16.png
212 ms
facebook_16.png
214 ms
bg_box_header.png
215 ms
bg_box_tabs.png
216 ms
bg_box.png
220 ms
__utm.gif
70 ms
live-etv.html
285 ms
etv.js
290 ms
etv.js
297 ms
webchat.aspx
650 ms
right_menu.png
234 ms
nav.png
237 ms
20-03-2016-etv.html
242 ms
j0=,,,;+,cp=etv%2Fotse+url=http%3A%2F%2Flive.err.ee%2Fetv%2F;;;
2042 ms
survey.js
2056 ms
menuhandler.ashx
108 ms
hotbox.html
317 ms
300lo.json
19 ms
et.js
19 ms
like.php
172 ms
sh.8e5f85691f9aaa082472a194.html
31 ms
dropdown.png
116 ms
sites_must.jpg
214 ms
zwaoNywIX8f.js
38 ms
LVx-xkvaJ0b.png
31 ms
etv-morepower.js
912 ms
ico_nolive.gif
116 ms
ico_live.gif
113 ms
jquery-1.4.2.min.js
649 ms
json2.js
452 ms
jquery.jqote2.min.js
343 ms
ErrChatMin.js
584 ms
_styles_print.css
115 ms
arrow_back.png
200 ms
bg_button.png
209 ms
identify
458 ms
JoinChannel
428 ms
blank.gif
237 ms
live.err.ee accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
live.err.ee best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
live.err.ee SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Image elements do not have [alt] attributes
Document doesn't have a valid hreflang
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
Document uses legible font sizes
Tap targets are not sized appropriately
ET
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Live.err.ee can be misinterpreted by Google and other search engines. Our service has detected that Estonian 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 Live.err.ee 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.
live.err.ee
Open Graph description is not detected on the main page of Live Err. 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: