Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

dcnenkin.jp

個人型確定拠出年金ナビ(iDeCoナビ)~イデコ加入ガイド~

Page Load Speed

5.4 sec in total

First Response

697 ms

Resources Loaded

3.9 sec

Page Rendered

761 ms

About Website

Visit dcnenkin.jp now to see the best up-to-date Dcnenkin content for Japan and also check out these interesting facts you probably never knew about dcnenkin.jp

ここではイデコを始める上で必要な知識と情報を全て解説しています。(1)イデコのメリット (2)税控除のこと (3)金融機関の選び方 (4)商品の選び方 いずれもこれから始める方に、最初に知っておいてほしいことばかりです。

Visit dcnenkin.jp

Key Findings

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

Performance Metrics

dcnenkin.jp performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value8.8 s

36/100

10%

Network Requests Diagram

dcnenkin.jp

697 ms

dcnenkin.jp

934 ms

font-awesome.min.css

42 ms

style.css

231 ms

remodal.css

465 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 85% of them (34 requests) were addressed to the original Dcnenkin.jp, 5% (2 requests) were made to Maxcdn.bootstrapcdn.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Dcnenkin.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 54.2 kB (14%)

Content Size

396.3 kB

After Optimization

342.2 kB

In fact, the total size of Dcnenkin.jp main page is 396.3 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. Images take 281.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 29.5 kB

  • Original 38.7 kB
  • After minification 29.5 kB
  • After compression 9.2 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.2 kB, which is 24% 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 29.5 kB or 76% of the original size.

Image Optimization

-7%

Potential reduce by 19.2 kB

  • Original 281.4 kB
  • After minification 262.2 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. Dcnenkin images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 2.2 kB

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

CSS Optimization

-21%

Potential reduce by 3.3 kB

  • Original 16.0 kB
  • After minification 16.0 kB
  • After compression 12.7 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. Dcnenkin.jp needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (32%)

Requests Now

37

After Optimization

25

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

Accessibility Review

dcnenkin.jp accessibility score

68

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

dcnenkin.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

dcnenkin.jp SEO score

100

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dcnenkin.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Dcnenkin.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

Open Graph data is detected on the main page of Dcnenkin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: