14.5 sec in total
5.4 sec
8 sec
1.2 sec
Visit err.ee now to see the best up-to-date ERR content for Estonia and also check out these interesting facts you probably never knew about err.ee
ERR uudised.
Visit err.eeWe analyzed Err.ee page load time and found that the first response time was 5.4 sec and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster. This domain responded with an error, which can significantly jeopardize Err.ee rating and web reputation
err.ee performance score
name
value
score
weighting
Value13.2 s
0/100
10%
Value30.1 s
0/100
25%
Value22.7 s
0/100
10%
Value31,400 ms
0/100
30%
Value0.54
14/100
15%
Value51.2 s
0/100
10%
5389 ms
664 ms
335 ms
230 ms
345 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 54% of them (55 requests) were addressed to the original Err.ee, 36% (37 requests) were made to Static.err.ee and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Err.ee.
Page size can be reduced by 395.3 kB (27%)
1.5 MB
1.1 MB
In fact, the total size of Err.ee main page is 1.5 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. 70% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 263.3 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 82.6 kB, which is 27% 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 263.3 kB or 85% of the original size.
Potential reduce by 58.3 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. ERR images are well optimized though.
Potential reduce by 73.6 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 73.6 kB or 67% of the original size.
Number of requests can be reduced by 18 (26%)
68
50
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 13 to 1 for JavaScripts and as a result speed up the page load time.
err.ee
5389 ms
headerjs
664 ms
headercss
335 ms
playercss
230 ms
bootstrap.less
345 ms
vendor
230 ms
client
590 ms
layoutpageincludes
216 ms
player
590 ms
iframe_api
74 ms
froogaloop2.min.js
11 ms
jquery.cookie.js
242 ms
analytics.js
137 ms
94751DB2A876FC5F725C8591F0E9643AD60C8CFB494DC898B65C48CDDF34CB7C.png
583 ms
761C864A532B0F7B9FE9F6B431AA5047DECD5A512C87E2FB5D0E8BE88F479742.png
581 ms
E2C599F0FEEED5217780C437D4C19437B2D3B5A441E8539FACA083ADD4AFA8D5.png
580 ms
C8840EC085B467FF0A80E284B0568D476F6E79A16561326F3A8D9C087D76B0F2.png
581 ms
87C98E871A539E60132CD860EF3837778116713BBE752584239CC3FF2454EBA6.png
581 ms
D00D706DB1B69B38B9F488972E65F9E98D784723AAEE5E39EDE17870208A84CA.png
578 ms
7789FD9E6479EFC43CC666FDCB279D29BEC67E44F087EF6C18A54BBB59D4700A.png
686 ms
7F3672B3DC91E768DC40B9F7C58D6155A11FDE61CCB07ED0CD1EABED25C0A5A7.png
713 ms
6DF739BB098415D456080A5DCFA1B09DBF6A4F94BD24DECEBBDFA0E04C95D9C1.png
794 ms
54B79D463A4F232102C5F742AEC662C5C1B219AD80DF03A017789418001D5271.png
858 ms
906C0F6EF8CC125DA53CB8E02ED159A1A205D122FE49E57D9B3AB843A727CC73.jpg
857 ms
0D053971CD7BBB78B130377E14E5CF75C3F3E751552563ADB1162DB2C787DB8B.gif
980 ms
07C78AFE798D4F34D36DCAEBBCF1FF30654E27D0C398490ADC16F3A6213C28D2.png
857 ms
E2A9FFFD367BC616E7F418C84E9FA28FB3ED3D1609EF16DC0A4F8FA6D22C100C.png
819 ms
BFA1819C3E83F14A4FCDC12EDDCF6090712DB4D563CC087CEE870D4CEB0E988D.gif
1038 ms
02470378586F37B92D3DCAE7C71727DBDE88FB2038FC5401B8D34E95E935A3FC.png
978 ms
DE4C25C352BF3E487AB8B48799FCFA21B1E75ECFEABDECE71F3F44B1AE4A301B.gif
775 ms
41CAEC92A04AA591960E187B170B1864766C34A40A7A07A0CACBF008F584DA70.png
980 ms
E1DCA9D0FBA60F7255D15E96EC0F16BE39755078BFFD1738EDE8953D403C73A2.gif
1165 ms
F2537F4726826D586930059CB00E9F87E92A5269F789EC40842EBE632D3DEEF9.png
979 ms
5E4FE39B22DA33DB4B71A4C2C8383D3EC10DEB133CF8EF2531574D994B3F69D9.gif
1164 ms
3AE9E83B1C15CBDFCF77DB75F155C1CF1BD87895ABBBE29074B2923699C91AF3.jpg
1163 ms
CA16CB849D79911E279E5EEAB90CCB90592ABDA495C3DFBADA9A78D986DD5B46.jpg
980 ms
err-ee-logo-valge.png
118 ms
Estonia-icon.png
118 ms
Russia-icon.png
119 ms
United-Kingdom-icon.png
118 ms
err-logo-pikk.png
116 ms
err_logo_146x45.png
136 ms
searchIcon1.png
447 ms
EL-logo.png
447 ms
proximanova-bold-webfont.woff
330 ms
proximanova-bold-webfont.woff
453 ms
proximanova-extrabold-webfont.woff
330 ms
proximanova-extrabold-webfont.woff
330 ms
proximanova-semibold-webfont.woff
450 ms
proximanova-semibold-webfont.woff
454 ms
proximanova-medium-webfont.woff
451 ms
proximanova-medium-webfont.woff
450 ms
proximanova-regular-webfont.woff
452 ms
proximanova-regular-webfont.woff
585 ms
proximanova-light-webfont.woff
583 ms
proximanova-light-webfont.woff
731 ms
proximanova-thin-webfont.woff
584 ms
proximanova-thin-webfont.woff
584 ms
icomoon.woff
584 ms
exo-extrabold-webfont.svg
729 ms
exo-regular-webfont.svg
727 ms
exo-thin-webfont.svg
695 ms
proximanova-semiboldit-webfont.woff
729 ms
proximanova-semiboldit-webfont.woff
799 ms
proximanova-boldit-webfont.woff
853 ms
proximanova-boldit-webfont.woff
852 ms
proximanova-extraboldit-webfont.woff
854 ms
proximanova-extraboldit-webfont.woff
854 ms
proximanova-mediumit-webfont.woff
940 ms
proximanova-mediumit-webfont.woff
1009 ms
proximanova-regularit-webfont.woff
915 ms
proximanova-regularit-webfont.woff
937 ms
proximanova-lightit-webfont.woff
938 ms
proximanova-lightit-webfont.woff
939 ms
proximanova-thinit-webfont.woff
1037 ms
proximanova-thinit-webfont.woff
1037 ms
collect
309 ms
collect
310 ms
widgets.js
353 ms
spring.js
975 ms
www-widgetapi.js
330 ms
getradiolistcontent
893 ms
2C02E5940FD9D19C2E5CD514039AD6E067F63F28C5505F7BDF8380177CDAA782.jpg
477 ms
2D33B5895A508FAF482C8F835961E0AD66755107059F08EA01CF92770EAFB287.jpg
327 ms
9E58DDA4542E8819CC2455A1D9141871FC3705407A4A9AEC8384A1002887DD8D.jpg
358 ms
4A9DC8D9EB2E3C9B2649F7B452F9ACFB2050C26F62DDFA7D21C6C7BB33194FA5.jpg
532 ms
93A57C772189468F5F690B3D79BB4830CD8741753C1120080870AE7AF4DFDCE7.jpg
408 ms
1521FC22782A09FB480FD551D440D97D95D83BF50C70721E4C294ED85AE5D891.jpg
717 ms
5AC4E89D73A404C0EC535FCA60CFE28F8D91437F81E078D622D6226C1E884EAA.jpg
588 ms
5800EAAA207F16BF7315D94BDBD0853A0ADA8B01A1E53D54D3650F6DB2729761.jpg
616 ms
2714A72D7FD74350857B801DD58B2C78B2100422CF571595BAA7D1CB9A9221A4.jpg
588 ms
7B4828F5B4940907D694D44E05A31D74E74DAD37979246553884221878F195B6.jpg
617 ms
0FE7462481C850A58C6F42F94096E50C78456BD03DEADC0CB88322778CC6EF00.jpg
672 ms
C9DCE3D9B2B53CD94CCE4C241B2BE3EE1988191D92BEB41FBB3CCE87E504EB53.jpg
677 ms
46262676CE5A41D0AC051B57D043BC984AE7B527EACEC52A9C93E00891CF0902.jpg
680 ms
9D0E982278B62C5B2169A44B02AD59815D10FF3DA432E10EE6CCB4D19BD531A2.jpg
593 ms
exo-regular-webfont.woff
311 ms
proximanova-boldit-webfont.ttf
264 ms
j0=,,,;+,cp=uudised%2Ferr.ee_avaleht+url=http%3A%2F%2Ferr.ee%2F;;;
524 ms
survey.js
536 ms
proximanova-boldit-webfont.svg
116 ms
blank.gif
255 ms
err.ee accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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
ET
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 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.
err.ee
Open Graph description is not detected on the main page of 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: