Tools & Wizards About Us
npfa.or.jp screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

npfa.or.jp

国民年金基金連合会

Page Load Speed

5.7 sec in total

First Response

11 ms

Resources Loaded

5.6 sec

Page Rendered

178 ms

npfa.or.jp screenshot

About Website

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

Key Findings

We analyzed Npfa.or.jp page load time and found that the first response time was 11 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

npfa.or.jp performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

38/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value420 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value1.037

2/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

npfa.or.jp

11 ms

npfa.or.jp

718 ms

normalize.css

688 ms

footable.core.css

709 ms

style2.css

709 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 58% of them (59 requests) were addressed to the original Npfa.or.jp, 4% (4 requests) were made to Live.rezync.com and 2% (2 requests) were made to S.primead.jp. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Npfa.or.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.2 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Npfa.or.jp main page is 1.2 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. 45% of websites need less resources to load. Images take 983.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 30.6 kB

  • Original 38.4 kB
  • After minification 28.6 kB
  • After compression 7.8 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 9.8 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 30.6 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 31.3 kB

  • Original 983.5 kB
  • After minification 952.3 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.

JavaScript Optimization

-50%

Potential reduce by 69.9 kB

  • Original 140.0 kB
  • After minification 122.8 kB
  • After compression 70.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 69.9 kB or 50% of the original size.

CSS Optimization

-39%

Potential reduce by 12.1 kB

  • Original 31.0 kB
  • After minification 30.6 kB
  • After compression 18.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 12.1 kB or 39% of the original size.

Requests Breakdown

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

Requests Now

92

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

npfa.or.jp

npfa.or.jp

11 ms

npfa.or.jp

npfa.or.jp

718 ms

normalize.css

normalize.css

688 ms

footable.core.css

footable.core.css

709 ms

style2.css

style2.css

709 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

22 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

24 ms

rem.min.js

rem.min.js

705 ms

ytag.js

ytag.js

785 ms

jquery.bxslider.js

jquery.bxslider.js

781 ms

response.min.js

response.min.js

691 ms

footable.js

footable.js

1372 ms

footable.filter.js

footable.filter.js

1360 ms

home.js

home.js

1379 ms

conversion.js

conversion.js

88 ms

s_retargeting.js

s_retargeting.js

857 ms

959 ms

fbevents.js

fbevents.js

72 ms

sp_logo.png

sp_logo.png

735 ms

ico_arrow_right.png

ico_arrow_right.png

733 ms

btn_search.png

btn_search.png

724 ms

sp_btn_request_out.png

sp_btn_request_out.png

1299 ms

sp_btn_nav_toggle.png

sp_btn_nav_toggle.png

1331 ms

gnav_out.png

gnav_out.png

832 ms

bg_breadcrumb.png

bg_breadcrumb.png

907 ms

bg_home.jpg

bg_home.jpg

919 ms

img_slide01_2023.png

img_slide01_2023.png

1420 ms

img_slide05_request_220324.png

img_slide05_request_220324.png

1495 ms

img_slide04_kokky_960_300.jpg

img_slide04_kokky_960_300.jpg

1086 ms

img_slide05_2023.png

img_slide05_2023.png

1603 ms

img_slide04_2023.png

img_slide04_2023.png

1592 ms

tab_system_over.png

tab_system_over.png

1987 ms

top_lnav_triangle.png

top_lnav_triangle.png

1560 ms

top_lnav_about.png

top_lnav_about.png

2097 ms

top_lnav_profit.png

top_lnav_profit.png

2169 ms

top_lnav_benefit.png

top_lnav_benefit.png

1710 ms

top_lnav_simulator.png

top_lnav_simulator.png

1776 ms

tab_join_out.png

tab_join_out.png

1787 ms

top_lnav_increase.png

top_lnav_increase.png

1888 ms

top_lnav_application.png

top_lnav_application.png

1960 ms

top_lnav_faq.png

top_lnav_faq.png

1967 ms

top_lnav_link.png

top_lnav_link.png

2090 ms

tab_motto_out.png

tab_motto_out.png

2476 ms

top_lnav_comic.png

top_lnav_comic.png

2143 ms

top_lnav_movie.png

top_lnav_movie.png

2162 ms

top_lnav_motto.png

top_lnav_motto.png

2772 ms

ico_401k_arrow.png

ico_401k_arrow.png

2601 ms

bnr_nenkin.png

bnr_nenkin.png

2342 ms

bnr_mhlw.png

bnr_mhlw.png

2336 ms

bnr_nenkinp.png

bnr_nenkinp.png

2311 ms

bnr_kenshou2022_1.png

bnr_kenshou2022_1.png

2972 ms

bnr_nenkinnet.png

bnr_nenkinnet.png

2396 ms

bnr_zenkoku202212.png

bnr_zenkoku202212.png

1901 ms

analytics.js

analytics.js

26 ms

48 ms

tc.min.js

tc.min.js

34 ms

aaprimead-data-aggregation.js

aaprimead-data-aggregation.js

853 ms

bnrshika202212.png

bnrshika202212.png

2492 ms

collect

collect

15 ms

ca.html

ca.html

392 ms

collect

collect

43 ms

js

js

80 ms

48 ms

bnr_shihousyosi202212.png

bnr_shihousyosi202212.png

1991 ms

bnr_bengoshi202212.png

bnr_bengoshi202212.png

2550 ms

sp_bnr_ideco.jpg

sp_bnr_ideco.jpg

2159 ms

sp_bnr_chart.jpg

sp_bnr_chart.jpg

2121 ms

sp_btn_pagetop.png

sp_btn_pagetop.png

2165 ms

logo.png

logo.png

2722 ms

pixel

pixel

137 ms

pixel

pixel

91 ms

Pug

Pug

85 ms

cksync.php

cksync.php

137 ms

128 ms

360947.gif

360947.gif

109 ms

rocketfuel_sync

rocketfuel_sync

197 ms

sync

sync

78 ms

g.pixel

g.pixel

87 ms

btn_request_out.png

btn_request_out.png

2106 ms

demconf.jpg

demconf.jpg

6 ms

cm

cm

278 ms

bounce

bounce

33 ms

sd

sd

28 ms

sync

sync

16 ms

bnr_ideco.jpg

bnr_ideco.jpg

1901 ms

bnr_chart.jpg

bnr_chart.jpg

1921 ms

match

match

2708 ms

pixel

pixel

70 ms

pixel

pixel

101 ms

mtx_cnt.gif

mtx_cnt.gif

222 ms

set_cookie_after_run.html

set_cookie_after_run.html

170 ms

sync

sync

45 ms

pixel

pixel

72 ms

td.min.js

td.min.js

17 ms

pa_pageviews_sayo

pa_pageviews_sayo

684 ms

sync

sync

32 ms

global_id

global_id

171 ms

mtx_cnt.gif

mtx_cnt.gif

157 ms

ico_slider_pager.png

ico_slider_pager.png

181 ms

blank.png

blank.png

179 ms

ico_slider_pager_active.png

ico_slider_pager_active.png

178 ms

Accessibility Review

npfa.or.jp accessibility score

82

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

Image elements do not have [alt] attributes

Best Practices

npfa.or.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

npfa.or.jp SEO score

82

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

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

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

    JA

  • Language Claimed

    JA

  • Encoding

    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.

Social Sharing Optimization

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: