5.9 sec in total
352 ms
5.4 sec
142 ms
Visit npfsb.ru now to see the best up-to-date Npfsb content for Russia and also check out these interesting facts you probably never knew about npfsb.ru
СберНПФ - 25 лет на пенсионном рынке России.
Visit npfsb.ruWe analyzed Npfsb.ru page load time and found that the first response time was 352 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
npfsb.ru performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value21.9 s
0/100
25%
Value18.6 s
0/100
10%
Value1,390 ms
16/100
30%
Value0
100/100
15%
Value26.4 s
0/100
10%
352 ms
672 ms
226 ms
257 ms
256 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Npfsb.ru, 68% (44 requests) were made to Npfsberbanka.ru and 11% (7 requests) were made to Api-maps.yandex.ru. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Npfsberbanka.ru.
Page size can be reduced by 615.6 kB (43%)
1.4 MB
829.3 kB
In fact, the total size of Npfsb.ru main page is 1.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. 25% of websites need less resources to load. Images take 628.1 kB which makes up the majority of the site volume.
Potential reduce by 108.5 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 108.5 kB or 62% of the original size.
Potential reduce by 36.0 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. Npfsb images are well optimized though.
Potential reduce by 374.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 374.1 kB or 71% of the original size.
Potential reduce by 97.0 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. Npfsb.ru needs all CSS files to be minified and compressed as it can save up to 97.0 kB or 83% of the original size.
Number of requests can be reduced by 33 (58%)
57
24
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Npfsb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
npfsb.ru
352 ms
www.npfsberbanka.ru
672 ms
226 ms
core.css
257 ms
fonts.css
256 ms
styles.css
383 ms
template_styles.css
919 ms
core.js
930 ms
core_ajax.js
798 ms
json2.min.js
519 ms
core_ls.js
657 ms
session.js
637 ms
ie.js
779 ms
load.min.js
902 ms
jquery-1.8.3.min.js
1572 ms
jquery.ezmark.min.js
1044 ms
jquery.cusel.min.js
1302 ms
jquery-ui-1.10.0.custom.min.js
1527 ms
jquery.validate.min.js
1515 ms
jquery.caret.js
1181 ms
jquery.groupinputs.js
1514 ms
jquery.coldshine-select.js
1515 ms
scripts.js
1838 ms
jquery.cycle.all.js
2208 ms
628 ms
combine.xml
564 ms
ef50ac9e93aaebe3299791c79f277f8e.cur
135 ms
3ce22e999d54bb9ca8150a59207f9d3e.cur
179 ms
4965b66fe115b2f2ed500ece66514d86.cur
290 ms
77492cf358d8b12629399322926c93f2.cur
403 ms
ba.js
169 ms
header.logo.png
438 ms
banner_status.jpg.jpg
1166 ms
banner_mln.jpg
1057 ms
npf_sber_banner.jpg
945 ms
imgo1.jpg
694 ms
index.feauture.npo.png
742 ms
index.feauture.ops.png
636 ms
index.feauture.corp.png
899 ms
footer.logo.napf.png
942 ms
footer.logo.asv.png
1127 ms
gtm.js
48 ms
header.i_personal2.png
1144 ms
forms.i_search.png
1178 ms
analytics.js
8 ms
watch.js
180 ms
collect
6 ms
collect
65 ms
collect
4 ms
collect
71 ms
watch.js
424 ms
bg_text_box.png
823 ms
index_banners-icon_update.png
951 ms
footer.border.png
1021 ms
btn_green.png
1060 ms
bx_stat
216 ms
common.social_icons.png
1136 ms
bg-form.png
1011 ms
headers-pager-active.png
1023 ms
headers-pager.png
1134 ms
PTS75F_W.woff
2101 ms
PTS55F_W.woff
2142 ms
advert.gif
84 ms
1
88 ms
20662768
208 ms
npfsb.ru accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
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
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
npfsb.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
npfsb.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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Npfsb.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 Npfsb.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.
npfsb.ru
Open Graph description is not detected on the main page of Npfsb. 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: