Access ng.ru. Независимая газета

ng.ru screenshot

8

Performance

Renders faster than
22% of other websites
90

Accessibility

Visual factors better than
that of 74% of websites
67

Best Practices

More advanced features
available than in
24% of websites
91

SEO

Google-friendlier than
70% of websites

First Response

317 ms

Resources Loaded

5.3 sec

Page Rendered

622 ms

ng.ru screenshot

About Website

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.ru

Key Findings

We analyzed Ng.ru page load time and found that the first response time was 317 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value2,190 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.727

6/100

15%

TTI (Time to Interactive)

Value21.4 s

1/100

10%

ng.ru

317 ms

ng.ru

149 ms

www.ng.ru

388 ms

www.ng.ru

274 ms

mpf-mediator.min.js

256 ms

Our browser made a total of 166 requests to load all elements on the main page. We found that 77% of them (127 requests) were addressed to the original Ng.ru, 3% (5 requests) were made to Pagead2.googlesyndication.com and 3% (5 requests) were made to Top-fwz1.mail.ru. The less responsive or slowest element that took the longest time to load (994 ms) relates to the external source Yandex.ru.

Content Size

2.5 MB

After Optimization

1.9 MB

In fact, the total size of Ng.ru main page is 2.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 301.3 kB

Original 339.2 kB
After minification 295.9 kB
After compression 38.0 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. This page needs HTML code to be minified as it can gain 43.3 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 301.3 kB or 89% of the original size.

Image Optimization

-6%

Potential reduce by 87.0 kB

Original 1.4 MB
After minification 1.3 MB

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.

JavaScript Optimization

-19%

Potential reduce by 118.8 kB

Original 638.9 kB
After minification 598.1 kB
After compression 520.1 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 118.8 kB or 19% of the original size.

CSS Optimization

-82%

Potential reduce by 115.2 kB

Original 140.9 kB
After minification 115.7 kB
After compression 25.7 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 115.2 kB or 82% of the original size.

Requests Now

158

After Optimization

130

The browser has sent 158 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 22 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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.

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

RU
Language Claimed

EN
Encoding

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.

Social Sharing Optimization

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: