5.6 sec in total
1 sec
4.3 sec
252 ms
Click here to check amazing Npfa content for Japan. Otherwise, check out these important facts you probably never knew about npfa.or.jp
国民年金基金についてご紹介します。
Visit npfa.or.jpWe analyzed Npfa.or.jp page load time and found that the first response time was 1 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
npfa.or.jp performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value4.8 s
31/100
25%
Value8.2 s
20/100
10%
Value110 ms
98/100
30%
Value0.203
61/100
15%
Value10.6 s
23/100
10%
1013 ms
9 ms
9 ms
628 ms
499 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 87% of them (55 requests) were addressed to the original Npfa.or.jp, 3% (2 requests) were made to Code.jquery.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Npfa.or.jp.
Page size can be reduced by 176.5 kB (10%)
1.7 MB
1.5 MB
In fact, the total size of Npfa.or.jp main page is 1.7 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. 30% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 26.7 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 8.5 kB, which is 26% 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 26.7 kB or 81% of the original size.
Potential reduce by 15.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. Npfa images are well optimized though.
Potential reduce by 35.5 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 35.5 kB or 37% of the original size.
Potential reduce by 98.9 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. Npfa.or.jp needs all CSS files to be minified and compressed as it can save up to 98.9 kB or 84% of the original size.
Number of requests can be reduced by 10 (16%)
61
51
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Npfa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
npfa.or.jp
1013 ms
jquery-1.11.0.min.js
9 ms
jquery-migrate-1.2.1.min.js
9 ms
normalize.css
628 ms
footable.core.css
499 ms
style2.css
1345 ms
rem.min.js
510 ms
jquery.bxslider.js
334 ms
response.min.js
340 ms
footable.js
534 ms
footable.filter.js
291 ms
home.js
320 ms
conversion.js
15 ms
s_retargeting.js
544 ms
sp_logo.png
168 ms
ico_arrow_right.png
169 ms
btn_search.png
176 ms
sp_btn_request_out.png
176 ms
sp_btn_nav_toggle.png
158 ms
gnav_out.png
162 ms
bg_breadcrumb.png
314 ms
bg_home.jpg
639 ms
img_slide01.jpg
1167 ms
img_slide02.jpg
1331 ms
img_slide03.jpg
678 ms
tab_system_over.png
342 ms
top_lnav_triangle.png
468 ms
top_lnav_about.png
680 ms
top_lnav_profit.png
1163 ms
top_lnav_benefit.png
1279 ms
top_lnav_simulator.png
845 ms
tab_join_out.png
851 ms
top_lnav_increase.png
1017 ms
top_lnav_application.png
1361 ms
top_lnav_faq.png
1188 ms
top_lnav_link.png
1318 ms
ico_401k_arrow.png
1330 ms
bnr_nenkin.png
1357 ms
bnr_mhlw.png
1438 ms
bnr_mobile.png
1475 ms
bnr_k_kaku.png
1495 ms
bnr_kenshou.png
1498 ms
bnr_nenkinnet.png
1526 ms
sp_bnr_plan.png
2045 ms
blank.png
1598 ms
sp_bnr_faq.png
1943 ms
sp_bnr_reason.png
1828 ms
sp_bnr_movie.jpg
1832 ms
sp_bnr_chart.jpg
1865 ms
33 ms
sp_btn_pagetop.png
1689 ms
analytics.js
33 ms
32 ms
collect
13 ms
logo.png
1769 ms
btn_request_out.png
1842 ms
bnr_plan.png
1840 ms
bnr_faq.png
1870 ms
bnr_reason.png
2070 ms
bnr_movie.jpg
1930 ms
bnr_chart.jpg
1859 ms
ico_slider_pager.png
168 ms
ico_slider_pager_active.png
169 ms
npfa.or.jp accessibility score
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
npfa.or.jp 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
npfa.or.jp 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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Npfa.or.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Npfa.or.jp 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.
npfa.or.jp
Open Graph description is not detected on the main page of Npfa. 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: