11.9 sec in total
3.7 sec
7.6 sec
577 ms
Welcome to neva.today homepage info - get ready to check Neva best content for Russia right away, or after learning these important things about neva.today
Neva.Today - интернет-газета новостей Санкт-Петербурга, Петербургские городские события и репортажи, происшествия и ДТП в СПб, комментарии экспертов
Visit neva.todayWe analyzed Neva.today page load time and found that the first response time was 3.7 sec and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
neva.today performance score
name
value
score
weighting
Value2.7 s
58/100
10%
Value8.3 s
2/100
25%
Value12.3 s
3/100
10%
Value2,260 ms
6/100
30%
Value0.392
26/100
15%
Value20.7 s
2/100
10%
3730 ms
41 ms
429 ms
76 ms
51 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 50% of them (55 requests) were addressed to the original Neva.today, 12% (13 requests) were made to Vk.com and 9% (10 requests) were made to Tk.promit.ru. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Neva.today.
Page size can be reduced by 783.7 kB (51%)
1.5 MB
757.1 kB
In fact, the total size of Neva.today main page is 1.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. 65% of websites need less resources to load. Javascripts take 646.5 kB which makes up the majority of the site volume.
Potential reduce by 285.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 285.2 kB or 86% of the original size.
Potential reduce by 47.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. Neva images are well optimized though.
Potential reduce by 390.0 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 390.0 kB or 60% of the original size.
Potential reduce by 60.6 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. Neva.today needs all CSS files to be minified and compressed as it can save up to 60.6 kB or 79% of the original size.
Number of requests can be reduced by 50 (52%)
97
47
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Neva. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
neva.today
3730 ms
jquery.qtip.min.css
41 ms
style2016.css
429 ms
jquery.min.js
76 ms
jquery.qtip.min.js
51 ms
smartcrop.js
409 ms
jquery-scrolltofixed-min.js
409 ms
addtocopy.js
410 ms
openapi.js
405 ms
837 ms
orphus2016.js
162 ms
css
140 ms
css
161 ms
print2016.css
142 ms
neva.today.logo.2016.png
283 ms
3_1_FFFFFFFF_EFEFEFFF_0_pageviews
295 ms
logo;NevaToday
386 ms
th_transport%20(1)(1).png
265 ms
th_arrow(1).png
265 ms
down_theme.png
263 ms
18.png
263 ms
search_icon.png
264 ms
04.png
384 ms
oil-icon.png
419 ms
vk_quad.png
382 ms
qpoint.png
417 ms
cmt_count.png
386 ms
like_count.png
419 ms
view_count.png
532 ms
vk2016.png
532 ms
fb2016.png
534 ms
twitter2016.png
885 ms
instagramm2016.png
877 ms
orphus.gif
876 ms
hourglass.gif
878 ms
hit;NevaToday
350 ms
msNrBgwx3ln3jjNy5b_Syw.ttf
331 ms
kTYfCWJhlldPf5LnG4ZnHC3USBnSvpkopQaUR-2r7iU.ttf
372 ms
watch.js
1 ms
analytics.js
96 ms
rtrg
227 ms
bg_header_2016.png
833 ms
m8_oFDuZMxdbJc[1].jpg
771 ms
tag_bg.png
767 ms
dsc_bg.png
764 ms
m9_%D0%BE%D0%B1%D1%8B%D1%81%D0%BA.jpeg
765 ms
m9_03883723[1].jpg
770 ms
m9_NLwwOkq6eCQ[1].jpg
771 ms
m9_umnov-pic4-452x302-20363[1].jpg
771 ms
m10_ugolvonoe_delo_6.jpg
756 ms
m10_%D1%81%D1%82%D1%80%D0%B5%D0%BB%D1%8C%D0%B1%D0%B02.jpg
830 ms
m10_34216_1371975662[1].jpg
833 ms
nMvcGlU6E4hOvMdb6LrvyfesZW2xOQ-xsNqO47m55DA.ttf
236 ms
QABk9IxT-LFTJ_dQzv7xpFwIJl2YiaXHM0xUx_ugXFg.ttf
273 ms
collect
137 ms
collect
527 ms
m10_DBM3zPFPDrQ[1].jpg
610 ms
m10_aec8be64-612d-4bfb-b7ed-6d544829d99b.jpg
767 ms
m10_kgiop2-300x169.jpg
610 ms
m9_5PajWJBAjzw[1].jpg
611 ms
m9_jh3HC11chmQ[1].jpg
670 ms
m9_%D0%BB%D0%B0%D1%81%D1%82%D1%80%D0%B0.jpg
680 ms
m9_bfa9ac6d.jpg
680 ms
m9_%D1%81%D1%83%D0%BF%D0%B0.jpg
765 ms
m9_aW1nLWZvdGtpLnlhbmRleC5ydS9nZXQvNTgyMS80MTA0ODA2My5hLzBfOTA2MTNfN2E4YTM4N2NfTA==[1].jpg
767 ms
m9_1391344506_981[1].jpg
825 ms
m9_esbe.jpg
831 ms
m9_tel.jpg
831 ms
m9_i.jpeg
936 ms
m9_482.jpg
935 ms
m9_2JxR3amQU0oGQPpmFezVMJiMO7JKkiiY.jpg
906 ms
m9_UCAZJ0vIp7I.jpg
957 ms
m9_%D0%B2%D0%B8%D1%82%D1%81%D0%B5%D0%BB%D1%8C.jpg
956 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
953 ms
combine.js
885 ms
1164b5fc24a5f3ac16a44c1c0acd540f23b597ac.js
154 ms
combine.js
1128 ms
d71d4d8ca099cfbcba2c094f839062bf69a9a587.js
239 ms
upload.gif
160 ms
widget_community.php
365 ms
1164b5fc24a5f3ac16a44c1c0acd540f23b597ac.js
636 ms
htmlParser.js
154 ms
runtime.js
161 ms
loader_nav19239_3.js
304 ms
lite.css
305 ms
lite.js
691 ms
lang3_0.js
398 ms
widget_community.css
395 ms
xdm.js
397 ms
al_community.js
395 ms
postscribe.js
286 ms
04996928c60602c30fc82db3e06e69ad2a03581f.jpg
414 ms
1719
249 ms
7ea6cb9b8cd72b38bd443c0ec309e950eb5955af.jpg
415 ms
638
416 ms
2204
407 ms
-7JuzQD89f0.jpg
448 ms
jW_kW9cx1JU.jpg
533 ms
iE5qFTe7wTc.jpg
537 ms
ZXtOgFhG4QE.jpg
447 ms
y0egUqIGKEs.jpg
535 ms
Av7oF3I9acE.jpg
533 ms
QDjVqwQA3CY.jpg
443 ms
camera_50.png
435 ms
util_cursor_storage_grab.cur
177 ms
w_logo.png
174 ms
util_cursor_storage_grabbing.cur
170 ms
util_cursor_storage_help.cur
172 ms
util_cursor_storage_zoom_in.cur
736 ms
neva.today 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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
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.
neva.today 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
Page has valid source maps
neva.today SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Neva.today 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 Neva.today 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.
neva.today
Open Graph description is not detected on the main page of Neva. 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: