Tools & Wizards About Us
dc.morningstar.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

dc.morningstar.co.jp

DC (確定拠出年金) ニュース | モーニングスター

Page Load Speed

3.2 sec in total

First Response

532 ms

Resources Loaded

2.5 sec

Page Rendered

141 ms

dc.morningstar.co.jp screenshot

About Website

Welcome to dc.morningstar.co.jp homepage info - get ready to check DC Morningstar best content for Japan right away, or after learning these important things about dc.morningstar.co.jp

『投信評価のグローバルスタンダード』モーニングスターの総合金融情報サイトです。投資信託を中心とし、株式、上場投資信託(ETF)、ニュース、レーティング、各種ランキング情報を提供し、資産運用に役立つポートフォリオや便利なツールが豊富です。

Visit dc.morningstar.co.jp

Key Findings

We analyzed Dc.morningstar.co.jp page load time and found that the first response time was 532 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

dc.morningstar.co.jp performance score

0

Network Requests Diagram

dc.morningstar.co.jp

532 ms

system.base.css

151 ms

system.menus.css

297 ms

system.messages.css

297 ms

system.theme.css

300 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 42% of them (29 requests) were addressed to the original Dc.morningstar.co.jp, 9% (6 requests) were made to Omt.shinobi.jp and 7% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (764 ms) belongs to the original domain Dc.morningstar.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 160.2 kB (57%)

Content Size

281.8 kB

After Optimization

121.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dc.morningstar.co.jp main page is 281.8 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. 40% of websites need less resources to load. Javascripts take 144.5 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 27.2 kB

  • Original 35.2 kB
  • After minification 33.3 kB
  • After compression 8.0 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 27.2 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 2.2 kB

  • Original 31.7 kB
  • After minification 29.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. DC Morningstar images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 74.6 kB

  • Original 144.5 kB
  • After minification 129.3 kB
  • After compression 69.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 74.6 kB or 52% of the original size.

CSS Optimization

-80%

Potential reduce by 56.2 kB

  • Original 70.5 kB
  • After minification 52.2 kB
  • After compression 14.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. Dc.morningstar.co.jp needs all CSS files to be minified and compressed as it can save up to 56.2 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (72%)

Requests Now

67

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DC Morningstar. 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 22 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

dc.morningstar.co.jp

dc.morningstar.co.jp

532 ms

system.base.css

system.base.css

151 ms

system.menus.css

system.menus.css

297 ms

system.messages.css

system.messages.css

297 ms

system.theme.css

system.theme.css

300 ms

aggregator.css

aggregator.css

296 ms

date.css

date.css

296 ms

datepicker.1.7.css

datepicker.1.7.css

297 ms

date_repeat_field.css

date_repeat_field.css

440 ms

field.css

field.css

441 ms

node.css

node.css

442 ms

user.css

user.css

443 ms

views.css

views.css

444 ms

ckeditor.css

ckeditor.css

445 ms

entity_embed.css

entity_embed.css

586 ms

colorbox_style.css

colorbox_style.css

589 ms

ctools.css

ctools.css

587 ms

layout.css

layout.css

592 ms

css_injector_1.css

css_injector_1.css

589 ms

css_injector_2.css

css_injector_2.css

592 ms

css_injector_3.css

css_injector_3.css

733 ms

css_injector_9.css

css_injector_9.css

737 ms

jquery.js

jquery.js

32 ms

js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js

js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js

735 ms

js_0xWri-HqjpOgDcpJP_qSnhX7UwXgffIjymbxk6tDcis.js

js_0xWri-HqjpOgDcpJP_qSnhX7UwXgffIjymbxk6tDcis.js

764 ms

79c4ab9af7d51040bbac6255486b11f8

79c4ab9af7d51040bbac6255486b11f8

370 ms

show_ads.js

show_ads.js

9 ms

morningstar_0.gif

morningstar_0.gif

166 ms

new.png

new.png

167 ms

btn01.gif

btn01.gif

153 ms

btn02.gif

btn02.gif

153 ms

dc.js

dc.js

28 ms

gtm.js

gtm.js

73 ms

bg_h1.gif

bg_h1.gif

161 ms

ninja_onetag.css

ninja_onetag.css

366 ms

trac.js

trac.js

339 ms

__utm.gif

__utm.gif

10 ms

analytics.js

analytics.js

6 ms

linkid.js

linkid.js

5 ms

collect

collect

7 ms

collect

collect

68 ms

collect

collect

3 ms

collect

collect

4 ms

collect

collect

69 ms

collect

collect

81 ms

ca-pub-1846352880545134.js

ca-pub-1846352880545134.js

106 ms

zrt_lookup.html

zrt_lookup.html

52 ms

show_ads_impl.js

show_ads_impl.js

54 ms

twitter_tweet_ninja_l.png

twitter_tweet_ninja_l.png

195 ms

google_plusone_ninja_l.png

google_plusone_ninja_l.png

374 ms

line_ninja_30x30.png

line_ninja_30x30.png

376 ms

pocket_ninja_l.png

pocket_ninja_l.png

434 ms

like.php

like.php

137 ms

ads

ads

256 ms

osd.js

osd.js

11 ms

ads

ads

271 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

34 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

13 ms

cookiesync

cookiesync

518 ms

14037899131858443586

14037899131858443586

39 ms

abg.js

abg.js

44 ms

m_js_controller.js

m_js_controller.js

60 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

33 ms

s

s

42 ms

x_button_blue2.png

x_button_blue2.png

43 ms

favicon

favicon

69 ms

favicon

favicon

64 ms

nessie_icon_thin_arrow_big_white.png

nessie_icon_thin_arrow_big_white.png

10 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

3 ms

SEO Factors

dc.morningstar.co.jp SEO score

0

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 Dc.morningstar.co.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 Dc.morningstar.co.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

dc.morningstar.co.jp

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