4.8 sec in total
378 ms
4 sec
442 ms
Welcome to we.ee homepage info - get ready to check We best content right away, or after learning these important things about we.ee
Kodulehtede loomine, veebilahendused, e-poed
Visit we.eeWe analyzed We.ee page load time and found that the first response time was 378 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
we.ee performance score
name
value
score
weighting
Value2.2 s
79/100
10%
Value3.4 s
66/100
25%
Value3.7 s
86/100
10%
Value520 ms
56/100
30%
Value0
100/100
15%
Value11.7 s
17/100
10%
378 ms
1016 ms
219 ms
471 ms
240 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 67% of them (24 requests) were addressed to the original We.ee, 22% (8 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain We.ee.
Page size can be reduced by 250.3 kB (6%)
4.3 MB
4.1 MB
In fact, the total size of We.ee main page is 4.3 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. 50% of websites need less resources to load. Images take 4.2 MB which makes up the majority of the site volume.
Potential reduce by 13.4 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 2.6 kB, which is 15% 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 13.4 kB or 78% of the original size.
Potential reduce by 186.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. We images are well optimized though.
Potential reduce by 300 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 49.9 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. We.ee needs all CSS files to be minified and compressed as it can save up to 49.9 kB or 83% of the original size.
Number of requests can be reduced by 4 (15%)
26
22
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of We. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for CSS and as a result speed up the page load time.
we.ee
378 ms
www.we.ee
1016 ms
reset.css
219 ms
style.css
471 ms
uniform.css
240 ms
css
27 ms
css
40 ms
et.js
135 ms
minify_7b837737ad9aff221314adc1d0bb7af2
771 ms
ga.js
141 ms
ui.png
352 ms
icons.png
715 ms
52.jpg
1152 ms
6.png
1069 ms
304.jpg
587 ms
303.png
1213 ms
133.jpg
585 ms
131.png
813 ms
308.jpg
820 ms
307.png
1905 ms
126.jpg
1145 ms
125.png
2105 ms
129.jpg
1304 ms
130.png
1474 ms
316.jpg
1266 ms
317.png
2148 ms
ian.png
1384 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
37 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
38 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
37 ms
k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf
41 ms
CcKI4k9un7TZVWzRVT-T88DdSZkkecOE1hvV7ZHvhyU.ttf
35 ms
UAnF6lSK1JNc1tqTiG8pNALUuEpTyoUstqEm5AMlJo4.ttf
36 ms
8KhZd3VQBtXTAznvKjw-k8DdSZkkecOE1hvV7ZHvhyU.ttf
37 ms
JbtMzqLaYbbbCL9X6EvaI8DdSZkkecOE1hvV7ZHvhyU.ttf
36 ms
__utm.gif
18 ms
we.ee accessibility score
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
Form elements do not have associated labels
we.ee best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
we.ee SEO score
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
ET
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise We.ee can be misinterpreted by Google and other search engines. Our service has detected that Estonian is used on the page, and it matches the claimed language. Our system also found out that We.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.
we.ee
Open Graph description is not detected on the main page of We. 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: