Tools & Wizards About Us
ifinance.ne.jp screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

ifinance.ne.jp

iFinance - 金融情報サイト

Page Load Speed

5.2 sec in total

First Response

543 ms

Resources Loaded

4.5 sec

Page Rendered

186 ms

ifinance.ne.jp screenshot

About Website

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

iFinanceは、マネー知識をワンストップで提供する金融情報サイトです。ファイナンシャル・リテラシー向上に役立つ基礎知識、商品ガイド、ブランド事典、用語集、データ集、リンク集、動画など多彩なコンテンツをご用意しています。

Visit ifinance.ne.jp

Key Findings

We analyzed Ifinance.ne.jp page load time and found that the first response time was 543 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

ifinance.ne.jp performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value1,950 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

ifinance.ne.jp

543 ms

www.ifinance.ne.jp

1311 ms

boilerplate.css

372 ms

style_top.css

486 ms

respond.min.js

523 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 12% of them (11 requests) were addressed to the original Ifinance.ne.jp, 12% (11 requests) were made to Platform.twitter.com and 12% (11 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Ifinance.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 230.9 kB (21%)

Content Size

1.1 MB

After Optimization

879.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ifinance.ne.jp main page is 1.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 701.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 55.0 kB

  • Original 70.1 kB
  • After minification 66.8 kB
  • After compression 15.1 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 55.0 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 12.7 kB

  • Original 275.4 kB
  • After minification 262.7 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. IFinance images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 110.1 kB

  • Original 701.9 kB
  • After minification 701.7 kB
  • After compression 591.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 110.1 kB or 16% of the original size.

CSS Optimization

-84%

Potential reduce by 53.1 kB

  • Original 63.0 kB
  • After minification 39.9 kB
  • After compression 10.0 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. Ifinance.ne.jp needs all CSS files to be minified and compressed as it can save up to 53.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (62%)

Requests Now

86

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ifinance.ne.jp

ifinance.ne.jp

543 ms

www.ifinance.ne.jp

www.ifinance.ne.jp

1311 ms

boilerplate.css

boilerplate.css

372 ms

style_top.css

style_top.css

486 ms

respond.min.js

respond.min.js

523 ms

js

js

78 ms

adsbygoogle.js

adsbygoogle.js

117 ms

cse.js

cse.js

51 ms

logo_ifinance.png

logo_ifinance.png

224 ms

clip_1.jpg

clip_1.jpg

435 ms

clip_2.jpg

clip_2.jpg

200 ms

clip_3.jpg

clip_3.jpg

267 ms

partition_2.gif

partition_2.gif

332 ms

banner_ifinancialtv.png

banner_ifinancialtv.png

579 ms

slotcar_library.js

slotcar_library.js

112 ms

show_ads_impl.js

show_ads_impl.js

249 ms

sdk.js

sdk.js

98 ms

sdk.js

sdk.js

12 ms

76 ms

cse_element__en.js

cse_element__en.js

28 ms

default+en.css

default+en.css

55 ms

default.css

default.css

56 ms

widgets.js

widgets.js

189 ms

async-ads.js

async-ads.js

76 ms

branding.png

branding.png

72 ms

clear.png

clear.png

66 ms

nav_logo114.png

nav_logo114.png

67 ms

page.php

page.php

142 ms

zrt_lookup.html

zrt_lookup.html

106 ms

ads

ads

980 ms

ads

ads

565 ms

ads

ads

522 ms

ads

ads

421 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

71 ms

btgk4h95XUy.css

btgk4h95XUy.css

45 ms

SHojUHmeyWm.js

SHojUHmeyWm.js

51 ms

xjg1QNQguf-.js

xjg1QNQguf-.js

43 ms

eQ3e44cCeXh.js

eQ3e44cCeXh.js

47 ms

qnn7MVQZYOT.js

qnn7MVQZYOT.js

47 ms

7CmGfGBVS6H.js

7CmGfGBVS6H.js

94 ms

q5lR_mVVI9t.js

q5lR_mVVI9t.js

99 ms

p55HfXW__mM.js

p55HfXW__mM.js

49 ms

settings

settings

177 ms

299795873_390950343183146_9010953698741896191_n.jpg

299795873_390950343183146_9010953698741896191_n.jpg

57 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

8 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

22 ms

fvgater

fvgater

64 ms

polyfills-3b821eda8863adcc4a4b.js

polyfills-3b821eda8863adcc4a4b.js

22 ms

runtime-a697c5a1ae32bd7e4d42.js

runtime-a697c5a1ae32bd7e4d42.js

49 ms

modules.20f98d7498a59035a762.js

modules.20f98d7498a59035a762.js

90 ms

main-fd9ef5eb169057cda26d.js

main-fd9ef5eb169057cda26d.js

76 ms

_app-88bf420a57d49e33be53.js

_app-88bf420a57d49e33be53.js

79 ms

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

92 ms

_buildManifest.js

_buildManifest.js

92 ms

_ssgManifest.js

_ssgManifest.js

92 ms

4706342425495021726

4706342425495021726

37 ms

load_preloaded_resource.js

load_preloaded_resource.js

44 ms

icon.png

icon.png

24 ms

abg_lite.js

abg_lite.js

35 ms

window_focus.js

window_focus.js

42 ms

qs_click_protection.js

qs_click_protection.js

42 ms

ufs_web_display.js

ufs_web_display.js

27 ms

bbae3fd3506d8d9338f85d10ea9db8af.js

bbae3fd3506d8d9338f85d10ea9db8af.js

179 ms

3b0c1a1c8750041eb27603629860e89a.js

3b0c1a1c8750041eb27603629860e89a.js

210 ms

f11bfab4e3c942216447974439595ef6.js

f11bfab4e3c942216447974439595ef6.js

213 ms

14763004658117789537

14763004658117789537

119 ms

s

s

125 ms

css

css

85 ms

activeview

activeview

252 ms

sa30O7WeJNzu8x7oKdCcujxNj08-gvZudrea3FT7Uzc.js

sa30O7WeJNzu8x7oKdCcujxNj08-gvZudrea3FT7Uzc.js

41 ms

reactive_library.js

reactive_library.js

223 ms

activeview

activeview

168 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

139 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

139 ms

ads

ads

384 ms

ads

ads

238 ms

7673313644131493955

7673313644131493955

77 ms

redir.html

redir.html

184 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

9 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

79 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

84 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

86 ms

redir.html

redir.html

223 ms

one_click_handler_one_afma.js

one_click_handler_one_afma.js

167 ms

2830811635178574984

2830811635178574984

96 ms

css

css

25 ms

activeview

activeview

127 ms

iframe.html

iframe.html

24 ms

iframe.html

iframe.html

25 ms

font

font

90 ms

font

font

92 ms

Accessibility Review

ifinance.ne.jp accessibility score

91

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.

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

ifinance.ne.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ifinance.ne.jp SEO score

90

Search Engine Optimization Advices

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 Ifinance.ne.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 Ifinance.ne.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

ifinance.ne.jp

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