9.3 sec in total
1.5 sec
7.5 sec
319 ms
Click here to check amazing Vchera content. Otherwise, check out these important facts you probably never knew about vchera.com
Вчера.ком Vchera.com - Петербургская интернет-газета - все новости Санкт-Петербурга, Петербургские городские события и репортажи, происшествия и мнения городских знаменитостей, расследования и коммент...
Visit vchera.comWe analyzed Vchera.com page load time and found that the first response time was 1.5 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
vchera.com performance score
name
value
score
weighting
Value2.0 s
84/100
10%
Value4.7 s
33/100
25%
Value3.0 s
94/100
10%
Value600 ms
50/100
30%
Value0.049
99/100
15%
Value5.6 s
69/100
10%
1450 ms
4113 ms
10 ms
443 ms
17 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Vchera.com, 52% (55 requests) were made to Neva.today and 12% (13 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Neva.today.
Page size can be reduced by 599.2 kB (53%)
1.1 MB
539.4 kB
In fact, the total size of Vchera.com main page is 1.1 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. 50% of websites need less resources to load. Javascripts take 453.9 kB which makes up the majority of the site volume.
Potential reduce by 285.8 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 285.8 kB or 85% of the original size.
Potential reduce by 24.4 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. Vchera images are well optimized though.
Potential reduce by 250.5 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 250.5 kB or 55% of the original size.
Potential reduce by 38.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. Vchera.com needs all CSS files to be minified and compressed as it can save up to 38.5 kB or 80% of the original size.
Number of requests can be reduced by 49 (51%)
96
47
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vchera. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
vchera.com
1450 ms
neva.today
4113 ms
jquery.qtip.min.css
10 ms
style2016.css
443 ms
jquery.min.js
17 ms
jquery.qtip.min.js
15 ms
smartcrop.js
449 ms
jquery-scrolltofixed-min.js
448 ms
addtocopy.js
449 ms
openapi.js
422 ms
746 ms
orphus2016.js
321 ms
css
63 ms
css
77 ms
print2016.css
159 ms
3_1_FFFFFFFF_EFEFEFFF_0_pageviews
256 ms
logo;NevaToday
282 ms
neva.today.logo.2016.png
166 ms
th_transport%20(1)(1).png
168 ms
th_arrow(1).png
166 ms
down_theme.png
160 ms
18.png
163 ms
search_icon.png
195 ms
01n.png
295 ms
oil-icon.png
296 ms
vk_quad.png
305 ms
qpoint.png
305 ms
cmt_count.png
309 ms
like_count.png
348 ms
view_count.png
429 ms
vk2016.png
427 ms
fb2016.png
445 ms
twitter2016.png
445 ms
instagramm2016.png
451 ms
orphus.gif
471 ms
hourglass.gif
825 ms
hit;NevaToday
278 ms
msNrBgwx3ln3jjNy5b_Syw.ttf
88 ms
kTYfCWJhlldPf5LnG4ZnHC3USBnSvpkopQaUR-2r7iU.ttf
106 ms
watch.js
0 ms
analytics.js
50 ms
rtrg
144 ms
bg_header_2016.png
558 ms
m8_oFDuZMxdbJc[1].jpg
697 ms
tag_bg.png
560 ms
dsc_bg.png
564 ms
m9_%D0%BE%D0%B1%D1%8B%D1%81%D0%BA.jpeg
582 ms
m9_03883723[1].jpg
681 ms
m9_NLwwOkq6eCQ[1].jpg
700 ms
m9_umnov-pic4-452x302-20363[1].jpg
708 ms
nMvcGlU6E4hOvMdb6LrvyfesZW2xOQ-xsNqO47m55DA.ttf
136 ms
QABk9IxT-LFTJ_dQzv7xpFwIJl2YiaXHM0xUx_ugXFg.ttf
98 ms
m10_ugolvonoe_delo_6.jpg
719 ms
m10_%D1%81%D1%82%D1%80%D0%B5%D0%BB%D1%8C%D0%B1%D0%B02.jpg
822 ms
m10_34216_1371975662[1].jpg
839 ms
collect
18 ms
collect
60 ms
hit;NevaToday
128 ms
m10_DBM3zPFPDrQ[1].jpg
545 ms
m10_aec8be64-612d-4bfb-b7ed-6d544829d99b.jpg
692 ms
m10_kgiop2-300x169.jpg
636 ms
m9_jh3HC11chmQ[1].jpg
641 ms
m9_%D0%BB%D0%B0%D1%81%D1%82%D1%80%D0%B0.jpg
662 ms
m9_bfa9ac6d.jpg
683 ms
m9_%D1%81%D1%83%D0%BF%D0%B0.jpg
690 ms
m9_%D0%BF%D1%80%D0%BE%D0%BA%D0%BE2.jpg
703 ms
m9_aW1nLWZvdGtpLnlhbmRleC5ydS9nZXQvNTgyMS80MTA0ODA2My5hLzBfOTA2MTNfN2E4YTM4N2NfTA==[1].jpg
776 ms
m9_1391344506_981[1].jpg
829 ms
m9_esbe.jpg
842 ms
m9_tel.jpg
842 ms
m9_i.jpeg
843 ms
m9_482.jpg
856 ms
m9_2JxR3amQU0oGQPpmFezVMJiMO7JKkiiY.jpg
965 ms
m9_UCAZJ0vIp7I.jpg
968 ms
m9_%D0%B2%D0%B8%D1%82%D1%81%D0%B5%D0%BB%D1%8C.jpg
980 ms
1164b5fc24a5f3ac16a44c1c0acd540f23b597ac.js
318 ms
m9_%D1%81%D0%BE%D0%BB%D0%BE%D0%B2%D1%8C%D0%B5%D0%B2%20%D0%B8%D0%B2%D0%B0%D0%BD.jpg
967 ms
d71d4d8ca099cfbcba2c094f839062bf69a9a587.js
317 ms
upload.gif
121 ms
widget_community.php
323 ms
1164b5fc24a5f3ac16a44c1c0acd540f23b597ac.js
440 ms
htmlParser.js
150 ms
loader_nav19239_3.js
136 ms
lite.css
138 ms
lite.js
511 ms
lang3_0.js
289 ms
widget_community.css
290 ms
xdm.js
290 ms
al_community.js
290 ms
postscribe.js
151 ms
runtime.js
53 ms
04996928c60602c30fc82db3e06e69ad2a03581f.jpg
319 ms
1719
180 ms
7ea6cb9b8cd72b38bd443c0ec309e950eb5955af.jpg
319 ms
638
317 ms
2204
193 ms
-7JuzQD89f0.jpg
441 ms
eGVaq0Hr_xk.jpg
422 ms
j7Np0Ekec7M.jpg
437 ms
iuhuxm5CpWk.jpg
270 ms
kE0j-Qp_yVY.jpg
435 ms
RxD_vfdgpHk.jpg
261 ms
fqJ_Py2uhf4.jpg
443 ms
camera_50.png
124 ms
w_logo.png
150 ms
vchera.com 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
Image elements do not have [alt] attributes
Links do not have a discernible name
vchera.com 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
vchera.com 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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vchera.com 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 Vchera.com 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.
vchera.com
Open Graph description is not detected on the main page of Vchera. 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: