4.7 sec in total
1.1 sec
3.3 sec
229 ms
Click here to check amazing Whatcar content for Estonia. Otherwise, check out these important facts you probably never knew about whatcar.ee
What Car? on maailma üks mõjukamaid autoalaseid väljaandeid, mis pakub erapooletut, sõltumatut hinnangut iga uue auto jaoks.
Visit whatcar.eeWe analyzed Whatcar.ee page load time and found that the first response time was 1.1 sec and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
whatcar.ee performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value12.5 s
0/100
25%
Value5.5 s
55/100
10%
Value300 ms
79/100
30%
Value0.01
100/100
15%
Value13.8 s
10/100
10%
1101 ms
60 ms
446 ms
335 ms
332 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 75% of them (54 requests) were addressed to the original Whatcar.ee, 14% (10 requests) were made to Cdn.whatcar.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Whatcar.ee.
Page size can be reduced by 239.9 kB (41%)
591.2 kB
351.3 kB
In fact, the total size of Whatcar.ee main page is 591.2 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. 30% of websites need less resources to load. Images take 308.4 kB which makes up the majority of the site volume.
Potential reduce by 41.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. This page needs HTML code to be minified as it can gain 10.5 kB, which is 20% 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 41.1 kB or 80% of the original size.
Potential reduce by 21.5 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. Whatcar images are well optimized though.
Potential reduce by 84.8 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 84.8 kB or 69% of the original size.
Potential reduce by 92.5 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. Whatcar.ee needs all CSS files to be minified and compressed as it can save up to 92.5 kB or 85% of the original size.
Number of requests can be reduced by 34 (48%)
71
37
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whatcar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.whatcar.ee
1101 ms
adServer.bs
60 ms
styles.css
446 ms
local.css
335 ms
glasses.css
332 ms
base.css
350 ms
AC_RunActiveContent.js
235 ms
functions.js
324 ms
whatcar.js
352 ms
jquery.js
549 ms
jquery.selectboxes.js
448 ms
swfobject.js
451 ms
moveobj.js
464 ms
logo2.jpg
586 ms
17142505012015-Profi_webi_700x100.jpg
660 ms
16174327012016-Corolla_970x115_EST.GIF
770 ms
img2.php
894 ms
news_main_bullet.jpg
579 ms
news_sub_bullet.jpg
656 ms
resize.php
696 ms
resize.php
699 ms
resize.php
673 ms
a82c1ce1fec40d340e7dc4a78fff5d29.jpg
674 ms
resize.php
719 ms
resize.php
721 ms
resize.php
782 ms
resize.php
784 ms
resize.php
787 ms
resize.php
852 ms
resize.php
853 ms
resize.php
893 ms
11205915022016-2016_01_EE_X-Trail_Crossover_Q4_300x250.jpg
1003 ms
home_reader_verdict_5.gif
895 ms
bt_ietaupi.jpg
871 ms
bt_jauta.jpg
918 ms
bt_compare.jpg
920 ms
bt_advices.jpg
968 ms
1305 ms
spacer.gif
888 ms
greybg.gif
852 ms
bn_my_whatcar.png
847 ms
bn_my_profile.png
887 ms
bn_sitemap.png
874 ms
bn_privacy.png
881 ms
bn_contact_us.png
846 ms
bn_facebook.png
846 ms
bn_send_to_a_friend.png
879 ms
rss.png
870 ms
logo_haymarket.gif
792 ms
sdk.js
370 ms
bg_mainNavWrapper3.gif
59 ms
bg_mainNavWrapper4_active.gif
40 ms
bg_mainNavWrapper1_active.gif
42 ms
bg_mainNavWrapper2.gif
39 ms
bg_mainNav.gif
40 ms
bg_mainNav_active.gif
41 ms
bg_blankTabLeft.gif
42 ms
bg_blankTabRight.gif
42 ms
bg_reviewsLandingCheckBoxWrapper.gif
43 ms
bg_reviewsLandingCheckBoxWrapper2.gif
45 ms
ga.js
7 ms
getCarManufacturers.php
842 ms
homepageTabBG.gif
825 ms
__utm.gif
12 ms
homePageFormBG.gif
781 ms
button.gif
783 ms
homepageMarker.gif
754 ms
bg_contentBox2.gif
824 ms
136 ms
xd_arbiter.php
210 ms
xd_arbiter.php
418 ms
script
429 ms
whatcar.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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
whatcar.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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
whatcar.ee SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Whatcar.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 Whatcar.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.
whatcar.ee
Open Graph description is not detected on the main page of Whatcar. 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: