Tools & Wizards About Us
pfrf.ru screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

pfrf.ru

Социальный фонд России

Page Load Speed

22.4 sec in total

First Response

463 ms

Resources Loaded

21.6 sec

Page Rendered

294 ms

pfrf.ru screenshot

About Website

Visit pfrf.ru now to see the best up-to-date Pfrf content for Russia and also check out these interesting facts you probably never knew about pfrf.ru

Интернет портал «Социальный фонд России»

Visit pfrf.ru

Key Findings

We analyzed Pfrf.ru page load time and found that the first response time was 463 ms and then it took 21.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

pfrf.ru performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value400 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value6.3 s

60/100

10%

Network Requests Diagram

pfrf.ru

463 ms

sfr.gov.ru

904 ms

mainpage.css

228 ms

vendors.css

342 ms

styles.css

352 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Pfrf.ru, 71% (40 requests) were made to Sfr.gov.ru and 7% (4 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Stat.sputnik.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 192.4 kB (12%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pfrf.ru 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. 35% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 73.7 kB

  • Original 89.9 kB
  • After minification 77.4 kB
  • After compression 16.1 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 12.5 kB, which is 14% 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 73.7 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 99.2 kB

  • Original 1.2 MB
  • After minification 1.1 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. Pfrf images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 17.7 kB

  • Original 197.5 kB
  • After minification 196.5 kB
  • After compression 179.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-5%

Potential reduce by 1.8 kB

  • Original 37.9 kB
  • After minification 37.9 kB
  • After compression 36.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. Pfrf.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 19 (37%)

Requests Now

52

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pfrf.ru

pfrf.ru

463 ms

sfr.gov.ru

sfr.gov.ru

904 ms

mainpage.css

mainpage.css

228 ms

vendors.css

vendors.css

342 ms

styles.css

styles.css

352 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

460 ms

jquery.cookie.min.js

jquery.cookie.min.js

384 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

529 ms

assist.js

assist.js

293 ms

script.js

script.js

345 ms

ereporter.js

ereporter.js

347 ms

chunk-vendors.js

chunk-vendors.js

1422 ms

app.js

app.js

1282 ms

tag.js

tag.js

884 ms

top100.cnt

top100.cnt

653 ms

banner-88x31-rambler-blue3.gif

banner-88x31-rambler-blue3.gif

635 ms

logo.svg

logo.svg

117 ms

c85c9d7a-9a31-42e8-9d40-7ca150afb95b-small.jpg

c85c9d7a-9a31-42e8-9d40-7ca150afb95b-small.jpg

233 ms

2288fb71-cbba-4866-81bf-9dc41460853a-small.jpg

2288fb71-cbba-4866-81bf-9dc41460853a-small.jpg

940 ms

f23c3813-3276-4460-bec4-fe144eaa8d3c-small.jpg

f23c3813-3276-4460-bec4-fe144eaa8d3c-small.jpg

579 ms

c8760105-b7ae-4eeb-8bd6-1d816bc687b2-small.jpg

c8760105-b7ae-4eeb-8bd6-1d816bc687b2-small.jpg

797 ms

622923b4-506e-4be0-8864-754cfa878739-small.jpg

622923b4-506e-4be0-8864-754cfa878739-small.jpg

259 ms

67ce75da-ceb8-49e9-89f5-d837007fab4f-small.jpg

67ce75da-ceb8-49e9-89f5-d837007fab4f-small.jpg

233 ms

lkzl.svg

lkzl.svg

350 ms

socpays.svg

socpays.svg

352 ms

pension.svg

pension.svg

390 ms

disabled.svg

disabled.svg

469 ms

calc.svg

calc.svg

471 ms

ik.svg

ik.svg

522 ms

kstr.svg

kstr.svg

588 ms

operations.svg

operations.svg

589 ms

edo.svg

edo.svg

652 ms

DisabilityCertificate.svg

DisabilityCertificate.svg

774 ms

reports.svg

reports.svg

776 ms

software.svg

software.svg

776 ms

wrench.svg

wrench.svg

783 ms

lip.svg

lip.svg

814 ms

info.svg

info.svg

828 ms

dv.svg

dv.svg

825 ms

interact.svg

interact.svg

915 ms

photo_2024-04-26_16-49-48.jpg

photo_2024-04-26_16-49-48.jpg

927 ms

School01.svg

School01.svg

931 ms

catalog_tsr.svg

catalog_tsr.svg

943 ms

fri.svg

fri.svg

945 ms

certificate_tsr.svg

certificate_tsr.svg

1045 ms

egisso.svg

egisso.svg

1060 ms

mkgu_widget.js

mkgu_widget.js

966 ms

cnt

cnt

33 ms

hit

hit

508 ms

cnt.js

cnt.js

19760 ms

advert.gif

advert.gif

678 ms

counter2

counter2

570 ms

widget.css

widget.css

118 ms

sync_cookie_image_decide

sync_cookie_image_decide

143 ms

1

1

137 ms

1

1

276 ms

Accessibility Review

pfrf.ru accessibility score

93

Accessibility Issues

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

Buttons do not have an accessible name

Best Practices

pfrf.ru best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pfrf.ru SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pfrf.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 Pfrf.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

pfrf.ru

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