Tools & Wizards About Us
whatzmoney.com screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

whatzmoney.com

WhatzMoney (ワッツマネー) 株式会社

Page Load Speed

5.6 sec in total

First Response

314 ms

Resources Loaded

4.6 sec

Page Rendered

636 ms

whatzmoney.com screenshot

About Website

Click here to check amazing Whatz Money content. Otherwise, check out these important facts you probably never knew about whatzmoney.com

WhatzMoney株式会社は、「すべての人に最適なお金の選択を」というミッションを実現するために、 お金に関する問題を解決するサービスを展開しています。 このコーポレートサイトでは、弊社からのお知らせや会社情報、採用情報なども掲載しております。

Visit whatzmoney.com

Key Findings

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

whatzmoney.com performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value19.4 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

whatzmoney.com

314 ms

whatzmoney.com

1052 ms

common.css

439 ms

style.css

925 ms

common.js

777 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 95% of them (92 requests) were addressed to the original Whatzmoney.com, 3% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Whatzmoney.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 304.0 kB (27%)

Content Size

1.1 MB

After Optimization

836.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whatzmoney.com 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. 45% of websites need less resources to load. Images take 790.2 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 39.8 kB

  • Original 46.0 kB
  • After minification 27.7 kB
  • After compression 6.3 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 18.3 kB, which is 40% 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 39.8 kB or 86% of the original size.

Image Optimization

-5%

Potential reduce by 38.2 kB

  • Original 790.2 kB
  • After minification 752.0 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. Whatz Money images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 77.0 kB

  • Original 136.2 kB
  • After minification 131.9 kB
  • After compression 59.2 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 77.0 kB or 57% of the original size.

CSS Optimization

-89%

Potential reduce by 149.0 kB

  • Original 167.8 kB
  • After minification 120.8 kB
  • After compression 18.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. Whatzmoney.com needs all CSS files to be minified and compressed as it can save up to 149.0 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (4%)

Requests Now

94

After Optimization

90

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whatzmoney.com

whatzmoney.com

314 ms

whatzmoney.com

whatzmoney.com

1052 ms

common.css

common.css

439 ms

style.css

style.css

925 ms

common.js

common.js

777 ms

index.js

index.js

454 ms

jquery.ah-placeholder.js

jquery.ah-placeholder.js

458 ms

analytics.js

analytics.js

141 ms

logo.png

logo.png

225 ms

img_main.jpg

img_main.jpg

376 ms

img_ttl.png

img_ttl.png

231 ms

icon_search.png

icon_search.png

234 ms

bank_smbc.png

bank_smbc.png

232 ms

bank_btmu.png

bank_btmu.png

372 ms

bank_mizuho.png

bank_mizuho.png

380 ms

bank_risona.png

bank_risona.png

383 ms

bank_sumishin.png

bank_sumishin.png

385 ms

bank_mutb.png

bank_mutb.png

517 ms

bank_shinsei.png

bank_shinsei.png

523 ms

bank_aozora.png

bank_aozora.png

530 ms

9999.png

9999.png

532 ms

bank_sumishin_sbi.png

bank_sumishin_sbi.png

533 ms

0035.png

0035.png

664 ms

bank_rakuten.png

bank_rakuten.png

671 ms

bank_roukin.png

bank_roukin.png

679 ms

bank_ja.png

bank_ja.png

681 ms

bank_shinkin.png

bank_shinkin.png

683 ms

bank_hokkaido.png

bank_hokkaido.png

811 ms

bank_aomori.png

bank_aomori.png

820 ms

bank_akita.png

bank_akita.png

830 ms

bank_iwate.png

bank_iwate.png

832 ms

bank_yamagata.png

bank_yamagata.png

833 ms

bank_77.png

bank_77.png

856 ms

bank_toho.png

bank_toho.png

957 ms

bank_gunma.png

bank_gunma.png

967 ms

bank_ashikaga.png

bank_ashikaga.png

981 ms

bank_jouyou.png

bank_jouyou.png

983 ms

bank_musashino.png

bank_musashino.png

984 ms

bank_chiba.png

bank_chiba.png

1005 ms

bank_tomin.png

bank_tomin.png

1103 ms

bank_yokohama.png

bank_yokohama.png

1116 ms

bank_daishi.png

bank_daishi.png

1131 ms

bank_yamanashichuo.png

bank_yamanashichuo.png

1133 ms

bank_82.png

bank_82.png

1034 ms

linkid.js

linkid.js

7 ms

collect

collect

4 ms

collect

collect

53 ms

ga-audiences

ga-audiences

29 ms

bank_hokuriku.png

bank_hokuriku.png

941 ms

bank_hokkoku.png

bank_hokkoku.png

1027 ms

bank_fukui.png

bank_fukui.png

1040 ms

bank_shizuoka.png

bank_shizuoka.png

1056 ms

bank_nagoya.png

bank_nagoya.png

918 ms

bank_16.png

bank_16.png

919 ms

bank_105.png

bank_105.png

934 ms

bank_shiga.png

bank_shiga.png

1019 ms

bank_kyoto.png

bank_kyoto.png

1034 ms

bank_ikedasenshu.png

bank_ikedasenshu.png

924 ms

bank_nanto.png

bank_nanto.png

919 ms

bank_kiyou.png

bank_kiyou.png

915 ms

bank_minato.png

bank_minato.png

932 ms

bank_tottori.png

bank_tottori.png

1016 ms

bank_sanninngoudou.png

bank_sanninngoudou.png

905 ms

bank_chugoku.png

bank_chugoku.png

919 ms

bank_hiroshima.png

bank_hiroshima.png

913 ms

bank_yamaguchi.png

bank_yamaguchi.png

914 ms

bank_awagin.png

bank_awagin.png

933 ms

bank_114.png

bank_114.png

886 ms

bank_iyo.png

bank_iyo.png

897 ms

bank_shikoku.png

bank_shikoku.png

912 ms

bank_fukuoka.png

bank_fukuoka.png

912 ms

bank_saga.png

bank_saga.png

913 ms

bank_18.png

bank_18.png

910 ms

bank_higo.png

bank_higo.png

887 ms

bank_oita.png

bank_oita.png

899 ms

bank_miyazaki.png

bank_miyazaki.png

911 ms

bank_kagoshima.png

bank_kagoshima.png

911 ms

bank_ryukyu.png

bank_ryukyu.png

911 ms

img_feature01_pc.png

img_feature01_pc.png

911 ms

img_feature01.png

img_feature01.png

886 ms

img_feature02_pc.png

img_feature02_pc.png

898 ms

img_feature02.png

img_feature02.png

910 ms

img_feature03_pc.png

img_feature03_pc.png

910 ms

img_feature03.png

img_feature03.png

912 ms

img_feature04_pc.png

img_feature04_pc.png

911 ms

img_feature04.png

img_feature04.png

887 ms

img_voice01.jpg

img_voice01.jpg

898 ms

img_voice01_sp.jpg

img_voice01_sp.jpg

911 ms

img_voice02.jpg

img_voice02.jpg

912 ms

img_voice02_sp.jpg

img_voice02_sp.jpg

1063 ms

img_voice03.jpg

img_voice03.jpg

911 ms

img_voice03_sp.jpg

img_voice03_sp.jpg

887 ms

img_voice04.jpg

img_voice04.jpg

899 ms

img_voice04_sp.jpg

img_voice04_sp.jpg

911 ms

icon_home.png

icon_home.png

910 ms

icon_tw.png

icon_tw.png

932 ms

icon_fb.png

icon_fb.png

972 ms

Accessibility Review

whatzmoney.com accessibility score

86

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

Links do not have a discernible name

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>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

whatzmoney.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

whatzmoney.com SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Whatzmoney.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 Whatzmoney.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

whatzmoney.com

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