4.7 sec in total
407 ms
3.8 sec
419 ms
Visit whatcar.lv now to see the best up-to-date What Car content for Latvia and also check out these interesting facts you probably never knew about whatcar.lv
What Car? ir viens no pasaulē ietekmīgākajiem auto ekspertu medijiem, kas piedāvā objektīvu, neatkarīgu ekspertu vērtējumu par katru jauno auto. show:1
Visit whatcar.lvWe analyzed Whatcar.lv page load time and found that the first response time was 407 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
whatcar.lv performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value15.5 s
0/100
25%
Value10.6 s
7/100
10%
Value1,300 ms
18/100
30%
Value0.459
19/100
15%
Value19.4 s
2/100
10%
407 ms
768 ms
542 ms
321 ms
425 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 82% of them (76 requests) were addressed to the original Whatcar.lv, 3% (3 requests) were made to Galv.hit.gemius.pl and 3% (3 requests) were made to Track.adform.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Whatcar.lv.
Page size can be reduced by 901.2 kB (23%)
3.9 MB
3.0 MB
In fact, the total size of Whatcar.lv main page is 3.9 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. 60% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 99.8 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 42.0 kB, which is 36% 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 99.8 kB or 87% of the original size.
Potential reduce by 42.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. What Car images are well optimized though.
Potential reduce by 561.2 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 561.2 kB or 72% of the original size.
Potential reduce by 197.6 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.lv needs all CSS files to be minified and compressed as it can save up to 197.6 kB or 82% of the original size.
Number of requests can be reduced by 44 (54%)
82
38
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What Car. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
whatcar.lv
407 ms
www.whatcar.lv
768 ms
main.css
542 ms
swfobject.js
321 ms
head.js
425 ms
ads.js
320 ms
lib.min.js
908 ms
global.js
324 ms
sso.js
424 ms
jquery-ui.css
531 ms
jquery-ui.js
1125 ms
jquery.ui.autocomplete.html.js
529 ms
css
32 ms
analytics.js
98 ms
xgemius.js
745 ms
381 ms
sdk.js
110 ms
loading.gif
115 ms
wc-logo.png
114 ms
09454120022024-Peugeot_2008WhatCar1100x150px_lv.jpg
236 ms
56d2d727a174be0184e657e93e907886.jpg
236 ms
7e15640d8040064fcce90a88cbf52de3.jpg
426 ms
a17f103a5df43c2ce9bdd9ada26f9e39.jpg
236 ms
911f04bb40e28836aaf86bc103ec58a2.jpg
426 ms
2560ffd023fb99e4584ad2701dbaf7e6.jpg
426 ms
d0186c1913dd9ca699e5cbe9fa8a1dfa.jpg
327 ms
e02d2a55a396d15851693e66644b7d38.jpg
390 ms
e8e874dfa416d3d805a32fbf30013305.jpg
435 ms
429b41cc863e598b66f4f3e77cc7f309.jpg
496 ms
72e76daab0b63bc92693acb513034679.jpg
637 ms
rating-4.png
601 ms
28f55262abe152dea55d7b2f992217fc.jpg
602 ms
cdf83c30c8b10591787319fbd0b7d9f1.jpg
603 ms
170fa61bc38ff5700ccdd92fbacb5c02.jpg
615 ms
rating-5.png
617 ms
ecc18a721b6b5237441053e9bb1a2953.jpg
636 ms
fec7724808ad0c5d06109f1b4894e02a.jpg
637 ms
8e4ebba8bb509db0082394a6b014ff53.jpg
652 ms
76db4baf78d2557959f5cb1177c847b6.jpg
710 ms
ae0e6a99ea7a32f63a09c6cbe98ed634.jpg
715 ms
8542d633e41398ff5426be6633da7a33.jpg
848 ms
21171715112023-Citroen-hotoffer_300x250_2.jpg
741 ms
12493422032024-SV60-300x250-LV-q1-24.gif
743 ms
city.png
759 ms
city_alt.png
815 ms
small.png
821 ms
small_alt.png
847 ms
family.png
848 ms
family_alt.png
865 ms
estate.png
920 ms
estate_alt.png
927 ms
callback=lpidCallback
17 ms
collect
26 ms
sdk.js
5 ms
42 ms
collect
40 ms
js
65 ms
ClearSans-Light.woff
960 ms
ClearSans-Thin.woff
1061 ms
ClearSans-Regular.woff
729 ms
ClearSans-Medium.woff
749 ms
ClearSans-Bold.woff
801 ms
ss-gizmo.woff
749 ms
icomoon.woff
747 ms
trackpoint-async.js
54 ms
mpv.png
703 ms
98 ms
mpv_alt.png
719 ms
small-suv.png
728 ms
small-suv_alt.png
748 ms
large-suv.png
750 ms
large-suv_alt.png
704 ms
executive.png
737 ms
103 ms
executive_alt.png
658 ms
convertible.png
676 ms
convertible_alt.png
678 ms
coupe.png
667 ms
coupe_alt.png
691 ms
hot-hatch.png
718 ms
hot-hatch_alt.png
731 ms
sport.png
747 ms
sport_alt.png
735 ms
electric.png
678 ms
electric_alt.png
701 ms
fpdata.js
104 ms
lsget.html
546 ms
luxury.png
716 ms
luxury_alt.png
731 ms
haymarket-logo.png
731 ms
whatcar_lv_top100_2018.png
1211 ms
08515722042024-Toy_Tactical_CorX_1100x150_Lat.gif
676 ms
rexdot.js
106 ms
whatcar.lv 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
Links do not have a discernible name
whatcar.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
whatcar.lv SEO score
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
![]()
LV
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatcar.lv can be misinterpreted by Google and other search engines. Our service has detected that Latvian/Lettish is used on the page, and it does not match the claimed English language. Our system also found out that Whatcar.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.
whatcar.lv
Open Graph description is not detected on the main page of What Car. 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: