5.4 sec in total
505 ms
4 sec
870 ms
Welcome to kover.ru homepage info - get ready to check Kover best content for Russia right away, or after learning these important things about kover.ru
▶ Магазины ковров kover.ru: 4000 дизайнов. ✔ 56 магазинов по России. ✔ Консультация декоратора. ✔ Сертифицированные изделия. ✔ Демонстрация ковра в интерьере ✈ Бесплатная доставка и примерка. ☎: 8 800...
Visit kover.ruWe analyzed Kover.ru page load time and found that the first response time was 505 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
kover.ru performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value20.0 s
0/100
25%
Value58.6 s
0/100
10%
Value71,260 ms
0/100
30%
Value0.069
96/100
15%
Value94.7 s
0/100
10%
505 ms
525 ms
128 ms
60 ms
250 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 83% of them (67 requests) were addressed to the original Kover.ru, 5% (4 requests) were made to Mc.yandex.ru and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Kover.ru.
Page size can be reduced by 737.8 kB (49%)
1.5 MB
776.2 kB
In fact, the total size of Kover.ru main page is 1.5 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. Javascripts take 701.9 kB which makes up the majority of the site volume.
Potential reduce by 70.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 33.0 kB, which is 41% 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 70.1 kB or 87% of the original size.
Potential reduce by 31.3 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. Kover images are well optimized though.
Potential reduce by 534.0 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 534.0 kB or 76% of the original size.
Potential reduce by 102.4 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. Kover.ru needs all CSS files to be minified and compressed as it can save up to 102.4 kB or 83% of the original size.
Number of requests can be reduced by 29 (38%)
76
47
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kover. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
kover.ru
505 ms
www.kover.ru
525 ms
module_default.css
128 ms
jquery.min.js
60 ms
kernel_main.css
250 ms
template_f00c6237b252a32da946776d106c50b9.css
248 ms
kernel_main.js
516 ms
jquery-1.8.3.min.js
382 ms
template_4c4eb286a48649b36aa359e67be1e585.js
257 ms
css
36 ms
css
89 ms
template.css
382 ms
adaptive.css
369 ms
jquery.liFixar.js
380 ms
jquery.cookie.js
491 ms
jquery.json-2.4.min.js
491 ms
jquery.reveal.js
510 ms
jPages.js
510 ms
respond.src.js
509 ms
jquery.BlackAndWhite.js
612 ms
windows.js
613 ms
jquery.validationEngine.js
639 ms
jquery.validationEngine-ru.js
637 ms
comparisson.js
633 ms
jquery-ias.js
644 ms
main.js
732 ms
additional.js
735 ms
placeholders.js
758 ms
ba.js
171 ms
analytics.js
56 ms
watch.js
170 ms
footer__logo.jpg
1289 ms
bx_stat
221 ms
header.png
129 ms
logo.png
133 ms
topmenu.png
133 ms
10644ccc2672535577f92cb1193e9f74.jpg
126 ms
10d7c9b2f3bd93498184101863a1c8f2.jpg
125 ms
aefd1ff161ed6cc8e2c08ef9c6d206ff.jpg
129 ms
24799c07db34aee3d9177424fe486569.jpg
249 ms
c2759f73ccb458ec5071ee72f0712da4.jpg
249 ms
705cca833890dde8f86837624253f5e4.jpg
257 ms
e38ba8c188c61985e9645a3a12c30de5.jpg
255 ms
05a9550a170bf6b77ec1708c5a4ac015.jpg
258 ms
soc-facebook.png
256 ms
soc-instagram.png
372 ms
soc-email.png
371 ms
topsearch.png
379 ms
1.jpg
1645 ms
2.jpg
1859 ms
3.jpg
1848 ms
4.jpg
1977 ms
menu_1.png
493 ms
menu_2.png
504 ms
menu_3.png
617 ms
menu_4.png
628 ms
f2b80f658e8dacb963cafb9f497d57f9.jpg
861 ms
latest_imgfn.png
753 ms
0e9016d837aeea700a401aa793bab501.jpg
1004 ms
1d7f67bfc4193b775fc2d20263839bf3.jpg
987 ms
f5cb6270e77a801d4e7253a6e6c4ab8b.jpg
1399 ms
subscription_bg.jpg
1130 ms
acymailing_imput_long.png
1256 ms
e1f6fa2101d20abe8c3ff9a3eadb8869.jpg
1883 ms
1ee70b4ce9bab4de6deaea1ead67ffe7.jpg
1780 ms
619e598de59ff9b74d06959a7f9f559a.jpg
1782 ms
a9811b7c83ae6aebd92981283ebda6fd.png
2167 ms
salon_2.jpg
1923 ms
EvPKapBawcLZ3hbihjhqAaCWcynf_cDxXwCLxiixG1c.ttf
11 ms
PFEncoreSansPro-ExtraThin.otf
1982 ms
collect
13 ms
collect
54 ms
watch.js
436 ms
PFEncoreSansPro-Thin.otf
1876 ms
ec40d5a7edbf633059a04794ef0a6746.jpg
1887 ms
df7aabafd7e1a7a80759acb15c9bc3ff.jpg
1926 ms
e07eb54c6ef6ddd9ea910960402b7421.jpg
1973 ms
d811e6c68b49c6170a73a2d47541a35d.jpg
1983 ms
partners.png
1992 ms
advert.gif
85 ms
1
87 ms
kover.ru accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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
kover.ru 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
kover.ru 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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kover.ru 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 Kover.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.
kover.ru
Open Graph description is not detected on the main page of Kover. 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: