4.9 sec in total
1.1 sec
3.6 sec
135 ms
Visit col.li now to see the best up-to-date Co L content and also check out these interesting facts you probably never knew about col.li
???? ??? ??????? ?????? ???????? ?? ?????? ????? ????? ????, ????, ?????, ???? ???? - ?????? ????? ????? ????????? ??????? ????? ????? ???????? ????? ?? ?????? ????? ???, ??????? ????? ?? ????? ???! D...
Visit col.liWe analyzed Col.li page load time and found that the first response time was 1.1 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
col.li performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value3.5 s
64/100
25%
Value9.7 s
11/100
10%
Value600 ms
49/100
30%
Value0.053
98/100
15%
Value9.8 s
28/100
10%
1098 ms
327 ms
278 ms
283 ms
75 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Col.li, 6% (3 requests) were made to Pagead2.googlesyndication.com and 6% (3 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Drix.co.il.
Page size can be reduced by 29.8 kB (8%)
365.7 kB
335.9 kB
In fact, the total size of Col.li main page is 365.7 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. 20% of websites need less resources to load. Javascripts take 262.7 kB which makes up the majority of the site volume.
Potential reduce by 21.2 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 21.2 kB or 78% of the original size.
Potential reduce by 1.8 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. Co L images are well optimized though.
Potential reduce by 6.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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 30 (63%)
48
18
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Co L. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
www.drix.co.il
1098 ms
Drix.asp
327 ms
swfobject.js
278 ms
check.js
283 ms
show_ads.js
75 ms
bg.jpg
144 ms
drix_01.jpg
143 ms
drix_03.jpg
144 ms
log-btn.jpg
283 ms
drix_05.jpg
286 ms
drix_06.jpg
285 ms
drix_08.jpg
285 ms
body_01.jpg
287 ms
body_02.jpg
286 ms
body_04.jpg
432 ms
body_05.jpg
434 ms
body_06.jpg
434 ms
body_07.jpg
436 ms
login.jpg
434 ms
body_11.jpg
435 ms
adv_01.jpg
572 ms
adv_02-prasim.jpg
574 ms
adv_03.jpg
573 ms
adv_04.jpg
574 ms
adv_06.jpg
576 ms
adv_07.jpg
574 ms
adv_08.jpg
712 ms
adv_09.jpg
714 ms
stats_01.jpg
715 ms
stats_02-new.jpg
717 ms
stats_03.jpg
717 ms
stats_04.jpg
716 ms
stats_06.jpg
852 ms
stats_07.jpg
854 ms
stats_08.jpg
855 ms
stats_09.jpg
855 ms
drix_10.jpg
856 ms
spacer.gif
855 ms
drix_04.jpg
977 ms
newest.jpg
971 ms
body_03.jpg
971 ms
adsbygoogle.js
379 ms
body_10.jpg
859 ms
best.jpg
999 ms
stats_05.jpg
859 ms
drix_11.jpg
856 ms
show_ads_impl.js
257 ms
zrt_lookup.html
42 ms
ads
129 ms
ads
484 ms
col.li 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
col.li best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
col.li SEO score
![]()
N/A
![]()
HE
WINDOWS-1255
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Col.li 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), while the claimed language is . Our system also found out that Col.li main page’s claimed encoding is windows-1255. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
col.li
Open Graph description is not detected on the main page of Co L. 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: