3 sec in total
248 ms
2.5 sec
282 ms
Click here to check amazing EHR content for Latvia. Otherwise, check out these important facts you probably never knew about ehr.lv
EHR - Eiropas hītu radio. Klausies šeit European Hit Radio, eiropas hītu radio
Visit ehr.lvWe analyzed Ehr.lv page load time and found that the first response time was 248 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
ehr.lv performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value5.4 s
21/100
25%
Value5.9 s
47/100
10%
Value1,600 ms
12/100
30%
Value0.005
100/100
15%
Value11.1 s
20/100
10%
248 ms
321 ms
31 ms
87 ms
172 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 6% of them (6 requests) were addressed to the original Ehr.lv, 28% (28 requests) were made to Static.xx.fbcdn.net and 20% (20 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (795 ms) relates to the external source Facebook.com.
Page size can be reduced by 43.9 kB (31%)
142.7 kB
98.8 kB
In fact, the total size of Ehr.lv main page is 142.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. 65% of websites need less resources to load. Images take 55.3 kB which makes up the majority of the site volume.
Potential reduce by 28.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 28.1 kB or 74% of the original size.
Potential reduce by 5.1 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. EHR images are well optimized though.
Potential reduce by 10.7 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 10.7 kB or 22% of the original size.
Number of requests can be reduced by 54 (57%)
95
41
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EHR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
ehr.lv
248 ms
www.ehr.lv
321 ms
jquery.min.js
31 ms
crossorigin.min.js
87 ms
swfobject.js
172 ms
ga.js
48 ms
widgets.js
6 ms
show_ads.js
6 ms
www.ehr.lv
161 ms
__utm.gif
59 ms
plusone.js
146 ms
getplaylist.php
152 ms
__utm.gif
22 ms
ca-pub-4227162389337436.js
46 ms
zrt_lookup.html
62 ms
show_ads_impl.js
63 ms
all.js
118 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
25 ms
ads
266 ms
osd.js
30 ms
cb=gapi.loaded_0
93 ms
cb=gapi.loaded_1
125 ms
fastbutton
179 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
73 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
82 ms
like.php
306 ms
ads
223 ms
ads
257 ms
296 ms
xd_arbiter.php
46 ms
xd_arbiter.php
117 ms
postmessageRelay
67 ms
cb=gapi.loaded_0
57 ms
cb=gapi.loaded_1
39 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
102 ms
api.js
44 ms
core:rpc:shindig.random:shindig.sha1.js
81 ms
2536007149-postmessagerelay.js
69 ms
vpc6VNjRPXV.js
93 ms
LVx-xkvaJ0b.png
94 ms
m_js_controller.js
25 ms
abg.js
37 ms
favicon
67 ms
googlelogo_color_112x36dp.png
55 ms
nessie_icon_tiamat_white.png
26 ms
s
20 ms
x_button_blue2.png
11 ms
jot.html
5 ms
ui
35 ms
comments.php
795 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
13 ms
xd_arbiter.php
22 ms
xYm_UD1pmAz.css
9 ms
TGpOWuX6Pv8.css
17 ms
wYS8zfQHnFO.css
24 ms
xPdT2kQG4vz.css
31 ms
_rx8naC75Dy.js
30 ms
x5F9OMjKyLw.js
65 ms
ICDbTSzjQEg.js
27 ms
rFmE1g6Dkoz.js
82 ms
7cm7D75Y0Sf.js
80 ms
DKRU1bYTkTw.js
80 ms
LU4a_W5X-JG.js
81 ms
sj-JwAJi4AH.js
78 ms
AunibtBOmSk.js
132 ms
Nvkj5df-gdk.js
141 ms
336JejShbZp.js
141 ms
Q4A0UyjU8W2.js
140 ms
TTCre3391I0.js
147 ms
DnwTulctFaE.js
149 ms
odA9sNLrE86.jpg
131 ms
168595_107179342689841_3252035_n.jpg
212 ms
like.png
41 ms
fav.png
37 ms
12733630_1085540078164152_603485683540099573_n.jpg
36 ms
12644913_1036704006373000_5057987426025260718_n.jpg
40 ms
12743907_1678856252404145_8599905692868977908_n.jpg
150 ms
11855620_1049305118415565_7971661460808661209_n.jpg
69 ms
11755205_923287121072110_7123897977975899532_n.jpg
56 ms
11249094_899745900072824_751380216057009131_n.jpg
73 ms
10152601_1031228923600061_8995373636224826169_n.jpg
48 ms
430009_173930282724224_15676720_n.jpg
73 ms
483171_449144835155360_1989334922_n.jpg
70 ms
1480519_578568398885821_1486616433_n.jpg
75 ms
12647203_959250820833838_8504387617191201944_n.jpg
151 ms
1962793_909332032496720_3219230939892208661_n.jpg
110 ms
34006_106419076075620_1676410_n.jpg
88 ms
12717494_1080065345394223_8449875032195763763_n.jpg
94 ms
26926_112926795405762_6688971_n.jpg
116 ms
12552558_1236209139741536_9179900818467203882_n.jpg
210 ms
11072910_10153169612524663_4301039416616491181_n.jpg
102 ms
12241546_110083336024458_3289290075362857540_n.jpg
166 ms
944102_10200737054501591_766406469_n.jpg
144 ms
wL6VQj7Ab77.png
20 ms
a-ZN6WoEOje.png
18 ms
pimRBh7B6ER.png
17 ms
W0OV23mIOyO.js
10 ms
36TdwhIHusi.js
14 ms
I6-MnjEovm5.js
13 ms
vlXaquuXMrr.js
14 ms
ehr.lv 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ehr.lv 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ehr.lv 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
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
LV
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ehr.lv can be misinterpreted by Google and other search engines. Our service has detected that Latvian/Lettish 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 Ehr.lv 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.
ehr.lv
Open Graph description is not detected on the main page of EHR. 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: