Tools & Wizards About Us
nikkoam.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

nikkoam.com

トップページ｜日興アセットマネジメント

Page Load Speed

5.3 sec in total

First Response

358 ms

Resources Loaded

4.7 sec

Page Rendered

249 ms

nikkoam.com screenshot

About Website

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

投資信託のことなら信頼と安心の日興アセットマネジメント。簡単便利なファンド検索やETF（上場投信）の詳細情報が満載で、あなたの資産運用を最大限に活かします。効果的な資産運用であなたを支援します。

Visit nikkoam.com

Key Findings

We analyzed Nikkoam.com page load time and found that the first response time was 358 ms and then it took 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.

Performance Metrics

nikkoam.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.558

13/100

15%

TTI (Time to Interactive)

Value9.1 s

32/100

10%

Network Requests Diagram

nikkoam.com

358 ms

www.nikkoam.com

1182 ms

slick.min.css

131 ms

bootstrap.min.css

218 ms

all.min.css

49 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 79% of them (65 requests) were addressed to the original Nikkoam.com, 13% (11 requests) were made to Cdn.jsdelivr.net and 4% (3 requests) were made to Cdn-au.onetrust.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Nikkoam.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (24%)

Content Size

4.4 MB

After Optimization

3.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nikkoam.com main page is 4.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. 55% of websites need less resources to load. Images take 4.3 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 50.0 kB

  • Original 63.9 kB
  • After minification 57.4 kB
  • After compression 13.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. 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 50.0 kB or 78% of the original size.

Image Optimization

-23%

Potential reduce by 1.0 MB

  • Original 4.3 MB
  • After minification 3.3 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. Obviously, Nikkoam needs image optimization as it can save up to 1.0 MB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 316 B

  • Original 29.2 kB
  • After minification 29.2 kB
  • After compression 28.9 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

-2%

Potential reduce by 838 B

  • Original 43.2 kB
  • After minification 43.1 kB
  • After compression 42.3 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. Nikkoam.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

78

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nikkoam.com

nikkoam.com

358 ms

www.nikkoam.com

www.nikkoam.com

1182 ms

slick.min.css

slick.min.css

131 ms

bootstrap.min.css

bootstrap.min.css

218 ms

all.min.css

all.min.css

49 ms

css

css

72 ms

common.min.css

common.min.css

345 ms

test.min.css

test.min.css

502 ms

slick-theme.min.css

slick-theme.min.css

502 ms

header.min.css

header.min.css

503 ms

basic-styles.min.css

basic-styles.min.css

507 ms

bootstrap-addition.min.css

bootstrap-addition.min.css

507 ms

print.min.css

print.min.css

509 ms

OtAutoBlock.js

OtAutoBlock.js

124 ms

otSDKStub.js

otSDKStub.js

149 ms

jquery-migrate@3

jquery-migrate@3

126 ms

slick.min.js

slick.min.js

48 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

47 ms

core.js

core.js

664 ms

head.min.js

head.min.js

665 ms

lib.min.js

lib.min.js

668 ms

common.min.js

common.min.js

670 ms

lodash.js

lodash.js

228 ms

video-loader.js

video-loader.js

692 ms

jquery.waypoints.js

jquery.waypoints.js

56 ms

lscache.min.js

lscache.min.js

139 ms

event-polyfill.min.js

event-polyfill.min.js

693 ms

vue-moment.min.js

vue-moment.min.js

734 ms

template.min.js

template.min.js

827 ms

6c96c980-6ccc-4d6b-8831-97d49d3c6501.json

6c96c980-6ccc-4d6b-8831-97d49d3c6501.json

33 ms

location

location

30 ms

logo_01.svg

logo_01.svg

177 ms

icon-flag-jp.png

icon-flag-jp.png

175 ms

icon-flag-nz.png

icon-flag-nz.png

183 ms

icon-flag-sg.png

icon-flag-sg.png

181 ms

icon-flag-hk.png

icon-flag-hk.png

180 ms

icon-flag-us.png

icon-flag-us.png

181 ms

icon-flag-de.png

icon-flag-de.png

332 ms

icon-flag-emea.png

icon-flag-emea.png

333 ms

icon-flag-world.png

icon-flag-world.png

333 ms

txt_your_goal_01.svg

txt_your_goal_01.svg

334 ms

img_card_fund_01.png

img_card_fund_01.png

502 ms

ico_close_01.svg

ico_close_01.svg

336 ms

ico_close_green_01.svg

ico_close_green_01.svg

497 ms

img_card_market_01.png

img_card_market_01.png

665 ms

img_card_fa_02.png

img_card_fa_02.png

663 ms

thumb_gnavi_about.jpg

thumb_gnavi_about.jpg

831 ms

Top-MainVisual_innovation-fundSP.png

Top-MainVisual_innovation-fundSP.png

1340 ms

Top-MainVisual_innovation-fundPC.png

Top-MainVisual_innovation-fundPC.png

1321 ms

Top-MainVisual_howtonisaSP.png

Top-MainVisual_howtonisaSP.png

1339 ms

Top-MainVisual_howtonisaPC.png

Top-MainVisual_howtonisaPC.png

1489 ms

Top-MainVisual_intheknowSP.png

Top-MainVisual_intheknowSP.png

1323 ms

Top-MainVisual_intheknowPC.png

Top-MainVisual_intheknowPC.png

1493 ms

Top-MainVisual_tracersN50SP.png

Top-MainVisual_tracersN50SP.png

1652 ms

Top-MainVisual_tracersN50PC.png

Top-MainVisual_tracersN50PC.png

1489 ms

Top-MainVisual_753_SP.png

Top-MainVisual_753_SP.png

1675 ms

Top-MainVisual_753_PC.png

Top-MainVisual_753_PC.png

1509 ms

img_card_fa_01.png

img_card_fa_01.png

1654 ms

ft_bnr-tracers_SP.png

ft_bnr-tracers_SP.png

1656 ms

ft_bnr-tracers_PC.png

ft_bnr-tracers_PC.png

1659 ms

ft_bnr-jp-equity-fund_SP.png

ft_bnr-jp-equity-fund_SP.png

1679 ms

ft_bnr-jp-equity-fund_PC.png

ft_bnr-jp-equity-fund_PC.png

1981 ms

ft_bnr-20lab_SP.png

ft_bnr-20lab_SP.png

1824 ms

ft_bnr-20lab_PC.png

ft_bnr-20lab_PC.png

1826 ms

bnr_wr-pj.png

bnr_wr-pj.png

1826 ms

bnr_intheknow02.png

bnr_intheknow02.png

1842 ms

bnr_cathie-qa2.png

bnr_cathie-qa2.png

1746 ms

fa-solid-900.woff

fa-solid-900.woff

18 ms

fa-regular-400.woff

fa-regular-400.woff

3 ms

bnr_digital.jpg

bnr_digital.jpg

1818 ms

bnr_report_ark.jpg

bnr_report_ark.jpg

1818 ms

bnr_sp_ark2024.jpg

bnr_sp_ark2024.jpg

1818 ms

bnr_kamiview.jpg

bnr_kamiview.jpg

1836 ms

bnr_rakuyomi.jpg

bnr_rakuyomi.jpg

1838 ms

bnr_fromhongokong.jpg

bnr_fromhongokong.jpg

1971 ms

bnr_etf.png

bnr_etf.png

1831 ms

bnr_tools.jpg

bnr_tools.jpg

1831 ms

bnr_ike.jpg

bnr_ike.jpg

1830 ms

bnr_jwrf.jpg

bnr_jwrf.jpg

1850 ms

bnr_invested-in-sustainability.png

bnr_invested-in-sustainability.png

1851 ms

ico_caution_01.svg

ico_caution_01.svg

1821 ms

ico_wakaba_01.svg

ico_wakaba_01.svg

1825 ms

Accessibility Review

nikkoam.com accessibility score

87

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

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

High

Links do not have a discernible name

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

nikkoam.com 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

High

Page has valid source maps

SEO Factors

nikkoam.com SEO score

99

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

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 Nikkoam.com 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 Nikkoam.com 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

nikkoam.com

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