9.6 sec in total
582 ms
8 sec
994 ms
Visit eva-drive.ru now to see the best up-to-date Eva Drive content for Russia and also check out these interesting facts you probably never knew about eva-drive.ru
Автоковрики EVA-DRIVE – новое явление на отечественном рынке. Мы расскажем, чем они отличаются от традиционных изделий и где в России купить коврик в салон автомобиля по низкой цене.
Visit eva-drive.ruWe analyzed Eva-drive.ru page load time and found that the first response time was 582 ms and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
eva-drive.ru performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value19.3 s
0/100
25%
Value10.6 s
7/100
10%
Value1,800 ms
9/100
30%
Value0.021
100/100
15%
Value17.4 s
4/100
10%
582 ms
1003 ms
417 ms
915 ms
1260 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 81% of them (78 requests) were addressed to the original Eva-drive.ru, 4% (4 requests) were made to Counter.yadro.ru and 3% (3 requests) were made to Kitbit.net. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Eva-drive.ru.
Page size can be reduced by 714.2 kB (30%)
2.4 MB
1.7 MB
In fact, the total size of Eva-drive.ru main page is 2.4 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. 55% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 34.6 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 7.5 kB, which is 16% 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 34.6 kB or 74% of the original size.
Potential reduce by 250.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. Obviously, Eva Drive needs image optimization as it can save up to 250.6 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 298.6 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 298.6 kB or 69% of the original size.
Potential reduce by 130.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. Eva-drive.ru needs all CSS files to be minified and compressed as it can save up to 130.5 kB or 88% of the original size.
Number of requests can be reduced by 24 (28%)
86
62
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eva Drive. 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 from 8 to 1 for CSS and as a result speed up the page load time.
eva-drive.ru
582 ms
www.eva-drive.ru
1003 ms
kernel_main.css
417 ms
template_8be50ed7f3a03ed1d3361808f7bb2d22.css
915 ms
core.js
1260 ms
core_ajax.js
1153 ms
reset.css
421 ms
skin.css
942 ms
jquery.fancybox.css
562 ms
fm.checkator.jquery.css
597 ms
style.css
743 ms
style.css
769 ms
jquery.10.2.js
1062 ms
jquery.jcarousel.js
934 ms
jquery.fancybox.js
1195 ms
fm.checkator.jquery.js
1083 ms
jquery-scrolltofixed-min.js
1083 ms
jquery.cslider.js
1195 ms
modernizr.custom.28468.js
1228 ms
script.js
1225 ms
top100.jcn
523 ms
spread.php
148 ms
analytics.js
93 ms
icons.png
384 ms
logo.jpg
391 ms
be92283c8265f05a3d49d85aaf1eb0fd.jpg
811 ms
bt.png
385 ms
e4307ec977477b84698292bd28d8a9a3.jpg
2608 ms
c26ab33accf27c6b75f1057522de014f.jpg
1646 ms
a12e93f0bfca0b6139cdd1f668e51675.jpg
836 ms
27f3ca7a3a8c31d4e6bb2530c8e09ea3.png
402 ms
8b7526f0662593025940788e098a6f76.png
427 ms
ce3bef34f484dfb6444dc843346cd4b7.png
445 ms
8364ff9d14b1d245595440e7f419718c.png
602 ms
20c7c6e42bb7750384ec0444d8841902.jpg
807 ms
8a86050b615d0ef050537db126f8b724.jpg
876 ms
d43395e3ddad3c20883583817df6fb49.png
944 ms
9ef0d988ff76c08621098ea807a7e1a6.png
1077 ms
ca3306107d47438e62cb6413320c28a4.jpg
970 ms
004857843945f61b997eee4091ae856a.png
1153 ms
6a223fe54ca2d9becef62a2e89c50d8a.jpg
1094 ms
94c0ca73d0ee3b36a998fe86a183c8f4.jpg
1117 ms
090a209e6c947d45fd864057c5abb4ee.png
1379 ms
53ac584e5794903d5bf2127789f4c05a.jpg
1231 ms
0ac86e33fa6430e3d4b2f5b1fcce0d84.jpg
1308 ms
9cdf930bfe127ad380d6522ee7903222.jpg
1313 ms
e00f179627a196b5e384265a24a3ed55.jpg
1395 ms
3431a7b34d585134b6bd8db02339008e.jpg
1478 ms
9a1ef17600f420e5f67e1bb7fc418fe5.jpg
1508 ms
de3ca9f3e6a3a14df42e096f7c5e975b.jpg
1551 ms
e2693e3bfac6decbb9d0719fa7b1cfe1.jpg
1575 ms
94dd96f67d3fcef26f2ae08fcb710873.jpg
1641 ms
5aa3e1a0fff55e05b017494385bbae34.jpg
1688 ms
bd0c0ab4c9de5c4e1ae39228190b132f.jpg
2602 ms
4357d8e91fff796b2a077d2917488168.jpg
1784 ms
f204f2e53664a5e984e42d6695e30d11.jpg
2441 ms
9e912615dfd377b704dce9cd3dfda927.jpg
1872 ms
b82ebd3485d9aa7e78d724eb6cb39a79.jpg
1923 ms
8cd15cd90cd87387f6559502a413265f.jpg
1925 ms
hit
308 ms
watch.js
259 ms
top100.scn
258 ms
sZ79ArWhvN
275 ms
pluso-like.js
295 ms
pfdintextpro-regular-webfont.woff
2309 ms
pfdintextpro-medium-webfont.woff
1792 ms
5004f2dd60f8cfbc7a54c188aecbac8b.jpg
1836 ms
collect
19 ms
widget_ru_RU.js
236 ms
hit
158 ms
pfdintextpro-bold-webfont.woff
1990 ms
becc8720dffa7a2c95a018cc547ff961.jpg
2005 ms
9a625598f8937c0091c02ac0fba7bb26.jpg
1994 ms
c9c799824e82ec365db9e74464839582.jpg
1818 ms
342acb55bf1eb8382e28b31c8e439529.jpg
1821 ms
9c64677e50fd486461ccd8ee02988533.jpg
1921 ms
textterra.png
1884 ms
or-enter.png
1828 ms
model-bg.jpg
1809 ms
next-prev.png
1707 ms
news-bg.jpg
3555 ms
social.png
1790 ms
footer-bg.jpg
2291 ms
logo-footer.jpg
1875 ms
quickorder.png
1620 ms
arrows-model.png
1616 ms
arrows-photo.png
1728 ms
arrows.png
1876 ms
hit;PLUSO
257 ms
kb.js
301 ms
collect_pluso.js
265 ms
hit;PLUSO
130 ms
dct.js
287 ms
h.gif
285 ms
s.js
288 ms
crossd_pluso_iframe.html
145 ms
eva-drive.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
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
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
eva-drive.ru 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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eva-drive.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Eva-drive.ru 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.
eva-drive.ru
Open Graph description is not detected on the main page of Eva Drive. 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: