6.2 sec in total
1.1 sec
4.8 sec
323 ms
Welcome to kolex.ru homepage info - get ready to check KOLEX best content for Russia right away, or after learning these important things about kolex.ru
Шины и диски в Самаре. Доставка по всей России. Отдел розничной продажи — телефон: 8 (800) 234-73-43; почта: info@kolex.ru | Отдел оптовой продажи — телефон: +7 (927) 603-22-25; почта: info@kolex.ru |...
Visit kolex.ruWe analyzed Kolex.ru page load time and found that the first response time was 1.1 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
kolex.ru performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value5.5 s
19/100
25%
Value13.1 s
2/100
10%
Value19,300 ms
0/100
30%
Value0.06
98/100
15%
Value28.0 s
0/100
10%
1087 ms
301 ms
303 ms
305 ms
304 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 86% of them (83 requests) were addressed to the original Kolex.ru, 4% (4 requests) were made to Google-analytics.com and 3% (3 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Kolex.ru.
Page size can be reduced by 910.1 kB (36%)
2.5 MB
1.6 MB
In fact, the total size of Kolex.ru main page is 2.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. 45% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 119.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 29.6 kB, which is 21% 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 119.4 kB or 86% of the original size.
Potential reduce by 160.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. KOLEX images are well optimized though.
Potential reduce by 587.3 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 587.3 kB or 78% of the original size.
Potential reduce by 42.8 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. Kolex.ru needs all CSS files to be minified and compressed as it can save up to 42.8 kB or 86% of the original size.
Number of requests can be reduced by 22 (24%)
92
70
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of KOLEX. 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 6 to 1 for CSS and as a result speed up the page load time.
kolex.ru
1087 ms
main.css
301 ms
menu.css
303 ms
jqModal.css
305 ms
jquery.jgrowl.css
304 ms
jquery.js
750 ms
jquery.scrollTo-min.js
304 ms
jquery-ui-custom.min.js
887 ms
jquery-ui-touch.js
442 ms
jquery.livequery.js
454 ms
jqModal.js
455 ms
jquery.jgrowl_minimized.js
442 ms
yepnope-min.js
585 ms
jquery.address.min.js
586 ms
functions.js
767 ms
jquery.maskedinput.js
604 ms
jcarousellite.js
728 ms
share.js
12 ms
barousel_demo.css
726 ms
jquery.barousel.min.js
763 ms
analytics.js
55 ms
header_pad.jpg
288 ms
logo.png
185 ms
f_basket_header.png
186 ms
f_basket_pad.jpg
186 ms
content_pad.jpg
300 ms
search_pad.jpg
184 ms
search.png
322 ms
x.png
318 ms
send.png
321 ms
f_enter_header.png
316 ms
f_enter_pad.jpg
431 ms
enter.png
446 ms
ts.png
458 ms
sto.png
462 ms
banner2.jpg
612 ms
recall.png
468 ms
phone2.png
575 ms
f_news_header.png
602 ms
f_news_pad.jpg
601 ms
9e53b30ac8d15d871e124d905f0a768528c9fbbc.jpg
604 ms
822348cae01dfa57147a0d9f39f01ed5474bb63e.jpg
616 ms
cc394f63fbcecf1edb9aced2c1e474ad833e9a34.jpg
725 ms
3_1_FFFFFFFF_EFEFEFFF_0_pageviews
242 ms
logo
266 ms
logo_clients_white.png
280 ms
f_tyre_header.png
720 ms
f_padding.jpg
722 ms
select.png
716 ms
f_disc_header.png
866 ms
39.jpg
1029 ms
40.jpg
1420 ms
35.jpg
1468 ms
38.jpg
1172 ms
36.jpg
1500 ms
37.jpg
1644 ms
29.jpg
1344 ms
24.jpg
1764 ms
25.jpg
2264 ms
30.jpg
1749 ms
ec.js
12 ms
collect
106 ms
collect
7 ms
watch.js
0 ms
b-share-icon.png
14 ms
watch.js
0 ms
hit
264 ms
kajax
1941 ms
barum_bravuris_2.jpg
1484 ms
buy.png
1510 ms
champiro_eco.jpg
1625 ms
collect
4 ms
barum_vanis.jpg
1559 ms
yokohama_v802.jpg
1645 ms
cordiant_comfort.jpg
1641 ms
maxxis_ms800.jpg
1639 ms
barum_bravuris_4x4.jpg
1668 ms
barum_bravuris_3hm.jpg
1790 ms
vr30.jpg
1678 ms
hit
128 ms
rx_512.jpg
1663 ms
mt_msr005_amb.jpg
1678 ms
replay_b181.jpg
1787 ms
kik_m56.jpg
1808 ms
replica_baosh_vega.jpg
1680 ms
replica_ns29.jpg
1683 ms
replay_ci15.jpg
1809 ms
k187.jpg
1830 ms
kosei_op_unison.jpg
1796 ms
bg_barousel_content.png
1802 ms
f_spec_header.png
1722 ms
loading.gif
1703 ms
f_cat_header.png
1956 ms
footer_pad.jpg
1785 ms
jcarousellite.js
1653 ms
jcarousellite.js
163 ms
paper.css
145 ms
kolex.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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
kolex.ru 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
kolex.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kolex.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Kolex.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.
kolex.ru
Open Graph description is not detected on the main page of KOLEX. 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: