3.1 sec in total
456 ms
2.5 sec
179 ms
Visit eb.ee now to see the best up-to-date Eb content for Estonia and also check out these interesting facts you probably never knew about eb.ee
Visit eb.eeWe analyzed Eb.ee page load time and found that the first response time was 456 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
eb.ee performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value2.6 s
87/100
25%
Value3.9 s
83/100
10%
Value100 ms
98/100
30%
Value0
100/100
15%
Value3.5 s
92/100
10%
456 ms
634 ms
223 ms
228 ms
224 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 47% of them (24 requests) were addressed to the original Eb.ee, 20% (10 requests) were made to Static.xx.fbcdn.net and 16% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (634 ms) belongs to the original domain Eb.ee.
Page size can be reduced by 280.2 kB (63%)
441.7 kB
161.4 kB
In fact, the total size of Eb.ee main page is 441.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 324.2 kB which makes up the majority of the site volume.
Potential reduce by 10.7 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 10.7 kB or 70% of the original size.
Potential reduce by 2.6 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. Eb images are well optimized though.
Potential reduce by 222.9 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 222.9 kB or 69% of the original size.
Potential reduce by 44.0 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. Eb.ee needs all CSS files to be minified and compressed as it can save up to 44.0 kB or 82% of the original size.
Number of requests can be reduced by 27 (59%)
46
19
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eb. 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 from 6 to 1 for CSS and as a result speed up the page load time.
eb.ee
456 ms
www.eb.ee
634 ms
__common.css
223 ms
__client.css
228 ms
__jquery_ui.css
224 ms
__forms.css
236 ms
__jquery.js
477 ms
__jquery_ui.js
460 ms
__i18n_et.js
442 ms
__javascript.js
441 ms
search.js
442 ms
key.png
113 ms
afr.php
370 ms
afr.php
562 ms
user-business.png
221 ms
megaphone.png
223 ms
logo_et_small.gif
223 ms
fenestra_468x60.gif
344 ms
zone
258 ms
niinijarauam.gif
455 ms
lt.png
245 ms
lv.png
350 ms
by.png
350 ms
ua.png
387 ms
md.png
467 ms
exclamation.png
365 ms
cross-small.png
413 ms
likebox.php
108 ms
fl.js
224 ms
410ucuAGgaJ.css
29 ms
tSbl8xBI27R.css
36 ms
q68gy-v_YMF.js
47 ms
FJmpeSpHpjS.js
70 ms
0wM5s1Khldu.js
68 ms
1bNoFZUdlYZ.js
67 ms
1623558_740232205994396_773726480_n.jpg
164 ms
1010266_168700473301825_232021778_n.jpg
17 ms
12804824_202887050074533_7287707100125513530_n.jpg
18 ms
12801352_688502091292913_5118239912907528301_n.jpg
16 ms
30064_123516404345742_5681528_n.jpg
14 ms
12805763_463292930543849_1221786590389314409_n.jpg
78 ms
1157608_549899061742268_1100454930_n.jpg
36 ms
11209455_708769265934676_1070367983196615201_n.jpg
17 ms
wL6VQj7Ab77.png
11 ms
s7jcwEQH7Sx.png
12 ms
1x1.gif
119 ms
8adc44eeee5077b47c4dea023e40ccad.jpg
226 ms
lg.php
240 ms
I6-MnjEovm5.js
5 ms
pQrUxxo5oQp.js
9 ms
ga.js
5 ms
eb.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.
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
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
eb.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
eb.ee SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eb.ee can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Eb.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.
eb.ee
Open Graph description is not detected on the main page of Eb. 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: