5.8 sec in total
1.6 sec
3.6 sec
534 ms
Welcome to contra.ws homepage info - get ready to check Contra best content for Russia right away, or after learning these important things about contra.ws
contra.ws is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, contra.ws has it all. We hope you find what yo...
Visit contra.wsWe analyzed Contra.ws page load time and found that the first response time was 1.6 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
contra.ws performance score
1593 ms
601 ms
590 ms
374 ms
374 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 50% of them (31 requests) were addressed to the original Contra.ws, 27% (17 requests) were made to Vk.com and 6% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Contra.ws.
Page size can be reduced by 365.3 kB (39%)
941.9 kB
576.7 kB
In fact, the total size of Contra.ws main page is 941.9 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. 45% of websites need less resources to load. Images take 459.5 kB which makes up the majority of the site volume.
Potential reduce by 42.5 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 42.5 kB or 79% of the original size.
Potential reduce by 8.9 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. Contra images are well optimized though.
Potential reduce by 243.4 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 243.4 kB or 72% of the original size.
Potential reduce by 70.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. Contra.ws needs all CSS files to be minified and compressed as it can save up to 70.5 kB or 80% of the original size.
Number of requests can be reduced by 32 (55%)
58
26
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Contra. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
contra.ws
1593 ms
index.php
601 ms
index.php
590 ms
style.css
374 ms
engine.css
374 ms
dtree.css
384 ms
openapi.js
531 ms
openapi.js
826 ms
share.js
65 ms
show_ads.js
29 ms
de_dust2.jpg
197 ms
button.gif
199 ms
728-90.gif
475 ms
1364943355_1339445116_78727765.jpg
389 ms
1364944065_1339444422_25731530.jpg
388 ms
1364942390_1339000327_90658712.jpg
387 ms
1364941714_1337195706_22198538.jpg
467 ms
1364941194_1330188059_bosha.jpg
473 ms
wink.gif
462 ms
head_bg_left.png
462 ms
2.png
1030 ms
upload.gif
190 ms
strelka.png
576 ms
pochta.png
581 ms
plaska-left-bg2.gif
584 ms
plaska-left-verh.gif
609 ms
ca-pub-6522408277112495.js
282 ms
zrt_lookup.html
358 ms
show_ads_impl.js
289 ms
widget_like.php
362 ms
krest.png
588 ms
plaska-left-niz.gif
700 ms
plaska-right-bg4.gif
704 ms
plaska-right-verh2.gif
710 ms
plaska-right-niz2.gif
713 ms
input-bg.gif
695 ms
logbg.png
977 ms
widget_community.php
381 ms
3.png
964 ms
highlight_strong.png
966 ms
footer-bg.gif
964 ms
hit
307 ms
b-share-form-button.png
100 ms
watch.js
4 ms
b-share-form-button_share__icon.png
206 ms
b-share-icon.png
205 ms
b-share-popup_down__tail.png
204 ms
ads
186 ms
osd.js
21 ms
loader_nav19239_3.js
186 ms
lite.css
175 ms
lite.js
487 ms
lang3_0.js
296 ms
widgets.css
296 ms
xdm.js
298 ms
al_like.js
325 ms
widget_community.css
288 ms
al_community.js
410 ms
abg.js
39 ms
w_logo.png
136 ms
camera_50.png
141 ms
like_widget.png
153 ms
contra.ws accessibility score
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
<frame> or <iframe> elements do not have a title
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
contra.ws best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
contra.ws SEO score
N/A
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Contra.ws 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 Contra.ws main page’s claimed encoding is windows-1251. 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.
contra.ws
Open Graph description is not detected on the main page of Contra. 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: