6.9 sec in total
344 ms
5.7 sec
914 ms
Visit ng.ru now to see the best up-to-date Ng content for Russia and also check out these interesting facts you probably never knew about ng.ru
Последние новости России и мировые новости. Политика. Экономика. Войны. Культура. Все свежие новости в «Независимой газете». Публикуем в реальном времени
Visit ng.ruWe analyzed Ng.ru page load time and found that the first response time was 344 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ng.ru performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value15.2 s
0/100
25%
Value12.8 s
2/100
10%
Value5,220 ms
0/100
30%
Value0.6
11/100
15%
Value21.9 s
1/100
10%
344 ms
955 ms
277 ms
188 ms
189 ms
Our browser made a total of 191 requests to load all elements on the main page. We found that 66% of them (126 requests) were addressed to the original Ng.ru, 5% (10 requests) were made to Static.xx.fbcdn.net and 4% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Ads.echoban.ru.
Page size can be reduced by 2.8 MB (44%)
6.4 MB
3.6 MB
In fact, the total size of Ng.ru main page is 6.4 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. 70% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 363.6 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 363.6 kB or 88% of the original size.
Potential reduce by 283.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. Ng images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 68% of the original size.
Potential reduce by 889.2 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. Ng.ru needs all CSS files to be minified and compressed as it can save up to 889.2 kB or 84% of the original size.
Number of requests can be reduced by 50 (27%)
184
134
The browser has sent 184 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ng. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
ng.ru
344 ms
www.ng.ru
955 ms
style.css
277 ms
dev_style.css
188 ms
modernizr-2.6.1.min.js
189 ms
jquery.min.js
13 ms
jquery-ui.min.js
45 ms
fileuploader.js
190 ms
plugins.js
197 ms
script.js
383 ms
adfox.asyn.code.ver3.js
329 ms
adfox.asyn.code.scroll.js
330 ms
core.css
331 ms
core_window.css
331 ms
ss.css
366 ms
style.css
381 ms
core.js
420 ms
core_ajax.js
455 ms
session.js
474 ms
core_window.js
567 ms
ss.js
475 ms
script.js
513 ms
adfox.custom.min.js
386 ms
ng.js
492 ms
tizerng.js
504 ms
2220454.png
546 ms
top100.cnt
325 ms
banner-88x31-rambler-black2.gif
427 ms
logo
327 ms
logo.png
138 ms
13-1-1.jpg
135 ms
default_picture_60.jpg
140 ms
13-8-1.jpg
138 ms
obzor0804-p.jpg
135 ms
vkr_c2.jpg
145 ms
13-4-2.jpg
216 ms
blansh-p.jpg
220 ms
2016-04-04_201413_c.jpg
233 ms
71-4-4.jpg
426 ms
71-4-1.jpg
422 ms
obzor0804-b.jpg
538 ms
prim-b.jpg
324 ms
nopic_user_150.gif
328 ms
71-6-1.jpg
328 ms
71-6-3.jpg
422 ms
71-7-01.jpg
515 ms
71-7-2.jpg
422 ms
71-7-1.jpg
511 ms
ng_stamp_new_80.jpg
509 ms
ng_stamp_new_80.jpg
512 ms
71-4-4.jpg
513 ms
71-4-1.jpg
599 ms
obzor0804-b.jpg
602 ms
red-b.jpg
607 ms
blansh-b.jpg
605 ms
fil-b.jpg
607 ms
71-5-1.jpg
630 ms
PSS_0020.jpg_Thumbnail0.jpg
690 ms
PSS_0198.jpg_Thumbnail0.jpg
694 ms
PSS_0558.jpg_Thumbnail0.jpg
695 ms
001.jpg_Thumbnail0.jpg
801 ms
005.jpg_Thumbnail0.jpg
699 ms
009.jpg_Thumbnail0.jpg
724 ms
cufevrfijg%20zlupyantljxnakohalbtqdnv%20ijn%20Bvlgarin.jpg_Thumbnail0.jpg
779 ms
analytics.js
42 ms
watch.js
2 ms
code.js
511 ms
hit
308 ms
aizjffctvmkpupph%20ksudcxrjbilxdh,%20teptouyq%20otdzjxpyezrzct,%20wudycowfvpkkiyfh%20otbrskphjuhbukur,%20expgllmh%20bwrjuwrjqtbieq.jpg_Thumbnail0.jpg
795 ms
all.js
61 ms
collect
44 ms
231 ms
plumbconreg-wf.woff
758 ms
nmqvsmgmcwko%20dlqufjexgleuqarc.jpg_Thumbnail0.jpg
676 ms
2016-03-28_204008_c.jpg
697 ms
21032016_c.jpg
743 ms
xd_arbiter.php
93 ms
xd_arbiter.php
139 ms
vkr_c2.jpg
760 ms
vkr_c2.jpg
756 ms
context.js
240 ms
bran-p.jpg
687 ms
66-5-1.jpg
721 ms
66-5-2.jpg
751 ms
hit
134 ms
1.gif
672 ms
montreal.jpg
760 ms
uran6.jpg
665 ms
mishiko_v.jpg
574 ms
zabor.jpg
626 ms
montreal.jpg
654 ms
uran6.jpg
665 ms
context_static_r1082.js
340 ms
mishiko_v.jpg
577 ms
zabor.jpg
577 ms
71-1-2.jpg
637 ms
82aba970ade411e2bfc922000a9e08f9_7.jpg
659 ms
%20js%20qa%20bcpynkhgabti.jpg
669 ms
counter2
161 ms
counter
165 ms
2220454.png
582 ms
71-3-1.jpg
651 ms
71-3-02.jpg
586 ms
208377_206007109429271_2957813_n.jpg
581 ms
01_5.jpg
647 ms
%20cigidilkqeqm.jpg
660 ms
img05.png
667 ms
71-8-5.jpg
642 ms
crash-b.jpg
590 ms
71-8-2.jpg
581 ms
71-8-01.jpg
651 ms
71-7-01.jpg
657 ms
71-7-2.jpg
637 ms
71-7-1.jpg
584 ms
watch.js
4 ms
ng_stamp_new_500.jpg
565 ms
vko-b.jpg
582 ms
71-2-1.jpg
645 ms
RTR2JXS5_b.jpg
624 ms
sirya-b.JPG
584 ms
sel-b.jpg
567 ms
71-6-2.jpg
567 ms
transp-p.jpg
586 ms
68-6-1.jpg
644 ms
115805
252 ms
71-12-1.jpg
600 ms
12-8-1.jpg
569 ms
6-8-1.jpg
562 ms
13-1-1.jpg
564 ms
13-4-1.jpg
596 ms
13-8-1.jpg
601 ms
13-10-1.jpg
574 ms
71-9-11.jpg
589 ms
71-9-2.jpg
585 ms
71-10-3.jpg
622 ms
71-9-3.jpg
623 ms
vko-p.jpg
593 ms
71-2-1.jpg
612 ms
RTR2JXS5_s.jpg
595 ms
71-5-1.jpg
598 ms
68-5-2.jpg
675 ms
68-5-1.jpg
675 ms
2016-04-07_185022.jpg
621 ms
elle0604-b.jpg
647 ms
160331-1-B.jpg
646 ms
160322-2-B.jpg
645 ms
nota.png
691 ms
topline.gif
684 ms
ajs.php
1069 ms
ramka.png
621 ms
search.png
662 ms
icons.png
768 ms
bgphoto.png
657 ms
2464952.jpg
721 ms
top100.js
268 ms
getCodeTest
165 ms
uploadingf0f25cf5329680bf9db11311c27f1b25-c719__.jpg
278 ms
uploadingf2d419936163934539aa2ceccabe253f-2171__.jpg
367 ms
uploading86dc825dc631581c715b72e0af086d50-5025__.jpg
275 ms
2632.js
279 ms
146010505115.jpg
268 ms
145995028742.jpg
278 ms
ping
136 ms
gold-rumi.jpg.70x50_q85_crop.jpg
158 ms
images_arxUGiG.jpg.70x50_q85_crop.jpg
314 ms
image001_a3bO1mj.jpg.70x50_q85_crop.jpg
309 ms
image002_OOMoGly.png.70x50_q85_crop.png
314 ms
3232.jpg.70x50_q85_crop.jpg
320 ms
informer
287 ms
like_box.php
163 ms
VDcXWt2API5.css
56 ms
NKmY6djv5D1.css
66 ms
SRSW8M763HA.js
152 ms
4uFOsJeWEIM.js
183 ms
y97Ig99UVTs.js
181 ms
KHAtULXOQuz.js
180 ms
528e873298a1088b6f51433552994e64.jpeg
296 ms
2d3a279053ad85c0c0509570f3a869b8.jpeg
297 ms
9abb4bad8b230ad2a17f037f40aac3b0.png
396 ms
12373346_1099274773439392_995153975292744581_n.jpg
78 ms
12376820_1099285253438344_4460119780627550383_n.jpg
41 ms
164446_108019492719841_1038965841_n.jpg
47 ms
10365938_159736734417040_1146736056081309669_n.jpg
45 ms
12928260_1553183278308268_5334436470601486765_n.jpg
53 ms
12715579_221820324833201_884023676048556263_n.jpg
54 ms
551531_851526418223191_3566580817270789656_n.jpg
52 ms
wL6VQj7Ab77.png
26 ms
1JLnMyDN79z.png
28 ms
VXcANLwwL5J.js
18 ms
i8XO-4kv8i7.js
21 ms
tracker
165 ms
ng.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
Heading elements are not in a sequentially-descending order
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
ng.ru 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
ng.ru 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
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ng.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Ng.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.
ng.ru
Open Graph description is not detected on the main page of Ng. 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: