Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

ngfr.ru

Нефть, газ и фондовый рынок

Page Load Speed

3.9 sec in total

First Response

584 ms

Resources Loaded

3.2 sec

Page Rendered

158 ms

ngfr.ru screenshot

About Website

Click here to check amazing Ngfr content for Russia. Otherwise, check out these important facts you probably never knew about ngfr.ru

В российской экономике нефтегазовая отрасль является одной из важнейших. Для принятия решения о покупке или продаже акций и облигаций необходима информация. Главное направление нашей деятельности - по...

Visit ngfr.ru

Key Findings

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

Performance Metrics

ngfr.ru performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

92/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value1,820 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value13.7 s

10/100

10%

Network Requests Diagram

ngfr.ru

584 ms

www.ngfr.ru

586 ms

style.css

268 ms

show_ads.js

69 ms

top100.jcn

436 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 18% of them (9 requests) were addressed to the original Ngfr.ru, 18% (9 requests) were made to Pagead2.googlesyndication.com and 10% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (774 ms) relates to the external source An.yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 227.4 kB (30%)

Content Size

750.7 kB

After Optimization

523.2 kB

In fact, the total size of Ngfr.ru main page is 750.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 586.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 35.7 kB

  • Original 42.9 kB
  • After minification 22.1 kB
  • After compression 7.3 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 20.8 kB, which is 48% 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 35.7 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 8.3 kB

  • Original 120.1 kB
  • After minification 111.8 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. Ngfr images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 183.3 kB

  • Original 586.3 kB
  • After minification 586.2 kB
  • After compression 403.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 183.3 kB or 31% of the original size.

CSS Optimization

-18%

Potential reduce by 246 B

  • Original 1.4 kB
  • After minification 1.4 kB
  • After compression 1.1 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. Ngfr.ru needs all CSS files to be minified and compressed as it can save up to 246 B or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (71%)

Requests Now

42

After Optimization

12

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ngfr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

ngfr.ru accessibility score

81

Accessibility Issues

Internationalization and localization

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

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

ngfr.ru best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ngfr.ru SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ngfr.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 Ngfr.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Ngfr. 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: