Tools & Wizards About Us
ifinance.ne.jp screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

ifinance.ne.jp

iFinance - 金融情報サイト

Page Load Speed

3.3 sec in total

First Response

846 ms

Resources Loaded

2.3 sec

Page Rendered

184 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 846 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

ifinance.ne.jp performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value5,100 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.108

87/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

ifinance.ne.jp

846 ms

boilerplate.css

520 ms

style_top.css

527 ms

respond.min.js

354 ms

brand

25 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 14% of them (9 requests) were addressed to the original Ifinance.ne.jp, 16% (10 requests) were made to Static.xx.fbcdn.net and 13% (8 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (899 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 109.4 kB (39%)

Content Size

280.2 kB

After Optimization

170.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ifinance.ne.jp main page is 280.2 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. 60% of websites need less resources to load. Images take 155.2 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 24.8 kB

  • Original 32.8 kB
  • After minification 29.5 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 24.8 kB or 76% of the original size.

Image Optimization

-16%

Potential reduce by 24.4 kB

  • Original 155.2 kB
  • After minification 130.8 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. Obviously, IFinance needs image optimization as it can save up to 24.4 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 43.3 kB

  • Original 72.4 kB
  • After minification 72.2 kB
  • After compression 29.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 43.3 kB or 60% of the original size.

CSS Optimization

-86%

Potential reduce by 16.9 kB

  • Original 19.8 kB
  • After minification 9.2 kB
  • After compression 2.8 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 16.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (50%)

Requests Now

58

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 58 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 21 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ifinance.ne.jp

ifinance.ne.jp

846 ms

boilerplate.css

boilerplate.css

520 ms

style_top.css

style_top.css

527 ms

respond.min.js

respond.min.js

354 ms

brand

brand

25 ms

brand

brand

55 ms

adsbygoogle.js

adsbygoogle.js

10 ms

analytics.js

analytics.js

40 ms

logo_ifinance.png

logo_ifinance.png

220 ms

clip_1.jpg

clip_1.jpg

365 ms

clip_2.jpg

clip_2.jpg

354 ms

clip_3.jpg

clip_3.jpg

219 ms

partition_2.gif

partition_2.gif

360 ms

sdk.js

sdk.js

87 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

70 ms

ca-pub-2203861498642265.js

ca-pub-2203861498642265.js

78 ms

zrt_lookup.html

zrt_lookup.html

123 ms

show_ads_impl.js

show_ads_impl.js

71 ms

collect

collect

52 ms

118 ms

collect

collect

122 ms

ads

ads

719 ms

xd_arbiter.php

xd_arbiter.php

100 ms

xd_arbiter.php

xd_arbiter.php

158 ms

osd.js

osd.js

30 ms

ads

ads

899 ms

widgets.js

widgets.js

84 ms

ads

ads

845 ms

page.php

page.php

121 ms

timeline.1b43d11859b7663a2225b885f87704a5.js

timeline.1b43d11859b7663a2225b885f87704a5.js

123 ms

xPv7gOXb_eI.css

xPv7gOXb_eI.css

103 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

141 ms

t-KLv3gqZy0.js

t-KLv3gqZy0.js

184 ms

uLtKx7ldlvR.js

uLtKx7ldlvR.js

217 ms

syndication

syndication

128 ms

357322962933796864

357322962933796864

239 ms

283151_391456954253309_2057772991_n.jpg

283151_391456954253309_2057772991_n.jpg

77 ms

7465_315937608540825_1483246658_n.jpg

7465_315937608540825_1483246658_n.jpg

24 ms

1779674_1399121110350323_1671087728_n.jpg

1779674_1399121110350323_1671087728_n.jpg

26 ms

180443_105461479528523_3589763_n.jpg

180443_105461479528523_3589763_n.jpg

25 ms

1003660_467778619980683_1425457561_n.jpg

1003660_467778619980683_1425457561_n.jpg

27 ms

12438991_825934747551667_5797945916133111618_n.jpg

12438991_825934747551667_5797945916133111618_n.jpg

26 ms

11665690_793320624114458_5673657248422580418_n.jpg

11665690_793320624114458_5673657248422580418_n.jpg

26 ms

11137151_708887262557017_4102963807479812717_n.jpg

11137151_708887262557017_4102963807479812717_n.jpg

27 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

28 ms

CSXXCvknpgK.png

CSXXCvknpgK.png

27 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

31 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

187 ms

R9a_DtVRZgv.js

R9a_DtVRZgv.js

30 ms

cUDgRFxaoIk.js

cUDgRFxaoIk.js

29 ms

0JBr1QHp8Gi.js

0JBr1QHp8Gi.js

50 ms

kDOzhTr2W91.js

kDOzhTr2W91.js

172 ms

clip1_normal.jpg

clip1_normal.jpg

367 ms

m_js_controller.js

m_js_controller.js

130 ms

abg.js

abg.js

150 ms

favicon

favicon

92 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

90 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

65 ms

s

s

51 ms

5171746271700867932

5171746271700867932

32 ms

x_button_blue2.png

x_button_blue2.png

35 ms

favicon

favicon

123 ms

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

22 ms

Accessibility Review

ifinance.ne.jp accessibility score

79

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-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

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

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: