10.2 sec in total
1.6 sec
8.1 sec
457 ms
Click here to check amazing EVIDENCE content for Russia. Otherwise, check out these important facts you probably never knew about e-vidence.ru
EVIDENCE
Visit e-vidence.ruWe analyzed E-vidence.ru page load time and found that the first response time was 1.6 sec and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
e-vidence.ru performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value11.2 s
0/100
25%
Value8.2 s
20/100
10%
Value510 ms
57/100
30%
Value5.311
0/100
15%
Value14.5 s
8/100
10%
1609 ms
64 ms
95 ms
80 ms
97 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 89% of them (76 requests) were addressed to the original E-vidence.ru, 5% (4 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain E-vidence.ru.
Page size can be reduced by 568.7 kB (45%)
1.3 MB
684.6 kB
In fact, the total size of E-vidence.ru main page is 1.3 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. 40% of websites need less resources to load. Images take 834.5 kB which makes up the majority of the site volume.
Potential reduce by 27.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. 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 27.4 kB or 78% of the original size.
Potential reduce by 253.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, EVIDENCE needs image optimization as it can save up to 253.6 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 140.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 140.6 kB or 68% of the original size.
Potential reduce by 147.0 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. E-vidence.ru needs all CSS files to be minified and compressed as it can save up to 147.0 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 EVIDENCE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
e-vidence.ru
1609 ms
css
64 ms
css
95 ms
css
80 ms
css
97 ms
modal.css
319 ms
k2.css
1339 ms
shadowbox.css
553 ms
system.css
552 ms
general.css
549 ms
addons.css
934 ms
layout.css
906 ms
template.css
1255 ms
joomla.css
1217 ms
gk_stuff.css
1365 ms
typo.css
1192 ms
dark.css
1087 ms
default.css
1234 ms
light.css
1337 ms
nivo-slider.css
1356 ms
style.css
1674 ms
css3_style1.css
1395 ms
style1.css
1479 ms
mootools.js
1639 ms
domready_fix.js
1510 ms
k2store.js
1510 ms
modal.js
1534 ms
k2.js
1633 ms
caption.js
1526 ms
gk.script.js
1526 ms
yoo_effects.js.php
1573 ms
mega.css
1648 ms
mega.js
1652 ms
gk.video.js
1807 ms
gk.image_show.js
1268 ms
bg.png
168 ms
logo.png
169 ms
module_gradient.png
171 ms
iconsmenu.png
581 ms
apixcompact.png
166 ms
apixdome.png
169 ms
apixfisheye.png
288 ms
apixbox.png
288 ms
apixzbox.png
286 ms
apixtbullet2.png
293 ms
apixsdome.png
293 ms
apixthermal2.png
427 ms
apix-ex.png
432 ms
sigma.png
432 ms
delta.png
433 ms
alfa2.png
434 ms
mnvr.png
576 ms
analitics-va.png
582 ms
analitics-face.png
580 ms
analitics-lpr.png
584 ms
cross.png
583 ms
wifi.png
714 ms
widescreen.png
717 ms
ws.png
761 ms
1p-cam.png
896 ms
1p-serv.png
1098 ms
1p-comm.png
746 ms
1p-ws.png
881 ms
project.png
2727 ms
loader.gif
857 ms
header_bg.jpg
858 ms
gk_is_buttons2.png
1008 ms
gk_is_scale.png
1015 ms
uqFpzDRr-oQw71LHgsWhDw.ttf
34 ms
53FiIA9tShIIWgCiX49s-vesZW2xOQ-xsNqO47m55DA.ttf
60 ms
ctg_1p.png
1013 ms
bottom_bg.png
2474 ms
icon_1.png
1171 ms
analytics.js
31 ms
watch.js
2 ms
collect
19 ms
icon_2.png
1100 ms
icon_3.png
1105 ms
680289apix_compact_m2_slider.png
604 ms
380921slide_5_abf2.png
1873 ms
591196slide_5_abf1.png
1243 ms
298482apix_30zdome.png
1265 ms
479558img2.png
1304 ms
891879slide_3_wdr1.png
2344 ms
8671642xwdr.png
2036 ms
e-vidence.ru 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
e-vidence.ru 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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
e-vidence.ru SEO score
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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-vidence.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 E-vidence.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.
e-vidence.ru
Open Graph description is not detected on the main page of EVIDENCE. 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: