Tools & Wizards About Us
zaim.net screenshot

Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

zaim.net

家計簿アプリ Zaim：簡単・無料でできるお金の管理

Page Load Speed

3.5 sec in total

First Response

328 ms

Resources Loaded

2.7 sec

Page Rendered

516 ms

zaim.net screenshot

About Website

Welcome to zaim.net homepage info - get ready to check Zaim best content for Japan right away, or after learning these important things about zaim.net

テレビで話題！人気の家計簿アプリ Zaim。簡単・シンプルにお金を管理しましょう。現金メイン派ならレシートを撮るだけ、キャッシュレス派なら銀行・クレジットカードを連携するだけで、カンタンに記録ができます。

Visit zaim.net

Key Findings

We analyzed Zaim.net page load time and found that the first response time was 328 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

zaim.net performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.577

12/100

15%

TTI (Time to Interactive)

Value4.6 s

82/100

10%

Network Requests Diagram

zaim.net

328 ms

index-9a117a53622b8f7fe11b904320e0a7e3.css

458 ms

icon

60 ms

index-c42f390cfc8669a976113a3ff2aafb88.js

588 ms

application-84e9cf4be18e84d46a008111c25a56a7.js

963 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Zaim.net, 40% (23 requests) were made to Zaim-assets.s3-ap-northeast-1.amazonaws.com and 9% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Content.zaim.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 554.7 kB (36%)

Content Size

1.6 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zaim.net main page is 1.6 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. 50% of websites need less resources to load. Images take 727.4 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 19.1 kB

  • Original 28.0 kB
  • After minification 27.8 kB
  • After compression 8.9 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 19.1 kB or 68% of the original size.

Image Optimization

-4%

Potential reduce by 26.2 kB

  • Original 727.4 kB
  • After minification 701.3 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. Zaim images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 404.6 kB

  • Original 675.0 kB
  • After minification 674.8 kB
  • After compression 270.4 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 404.6 kB or 60% of the original size.

CSS Optimization

-83%

Potential reduce by 104.7 kB

  • Original 126.7 kB
  • After minification 125.7 kB
  • After compression 21.9 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. Zaim.net needs all CSS files to be minified and compressed as it can save up to 104.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (42%)

Requests Now

52

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zaim.net

zaim.net

328 ms

index-9a117a53622b8f7fe11b904320e0a7e3.css

index-9a117a53622b8f7fe11b904320e0a7e3.css

458 ms

icon

icon

60 ms

index-c42f390cfc8669a976113a3ff2aafb88.js

index-c42f390cfc8669a976113a3ff2aafb88.js

588 ms

application-84e9cf4be18e84d46a008111c25a56a7.js

application-84e9cf4be18e84d46a008111c25a56a7.js

963 ms

adsbygoogle.js

adsbygoogle.js

6 ms

analytics.js

analytics.js

32 ms

logo-large-7e525537b7befa7676895bd3f34dc5de.png

logo-large-7e525537b7befa7676895bd3f34dc5de.png

164 ms

img_01.jpg

img_01.jpg

1264 ms

under-logo-0c8faa20a42c2a97a20e4e8e5486e2b5.png

under-logo-0c8faa20a42c2a97a20e4e8e5486e2b5.png

239 ms

index-mainimage-bg-f2fafd1882d6e53aa8d9559ba0fb2d0a.png

index-mainimage-bg-f2fafd1882d6e53aa8d9559ba0fb2d0a.png

193 ms

index-list@2x-097d5e428e9b009b292f31b5da552ede.png

index-list@2x-097d5e428e9b009b292f31b5da552ede.png

1067 ms

index-title@2x-38af8da07d32f374f1d5ed94a9dfa2a8.png

index-title@2x-38af8da07d32f374f1d5ed94a9dfa2a8.png

484 ms

bg-shadow-a5029b92d125bb51db7e68de68b3cc21.png

bg-shadow-a5029b92d125bb51db7e68de68b3cc21.png

338 ms

badge.free-2bb9170893721261cf264097243f8b95.png

badge.free-2bb9170893721261cf264097243f8b95.png

326 ms

btn-web-f938b38722b9fbc6e82b5d60a02a6d2f.png

btn-web-f938b38722b9fbc6e82b5d60a02a6d2f.png

351 ms

download.apple-26ba45b1fc2c41c914a2d4fa2b5d4d57.png

download.apple-26ba45b1fc2c41c914a2d4fa2b5d4d57.png

397 ms

download.android-d700f4f7a34c0dc53f71fc9b65d1617e.png

download.android-d700f4f7a34c0dc53f71fc9b65d1617e.png

549 ms

download.windows-b8c67c582372d7d529ab442aa3ab5766.png

download.windows-b8c67c582372d7d529ab442aa3ab5766.png

549 ms

index-function-1-57058a54c49e7b0127a5a5ae8efcc0f6.png

index-function-1-57058a54c49e7b0127a5a5ae8efcc0f6.png

549 ms

index-function-3-300b8b247c269190852f1a7d0bbf32de.png

index-function-3-300b8b247c269190852f1a7d0bbf32de.png

585 ms

index-function-2-13d7ca83d3ffb79aa7d63250c13fd985.png

index-function-2-13d7ca83d3ffb79aa7d63250c13fd985.png

629 ms

index-icon-01-be66e707dbf37c2f28d056d41361ca98.png

index-icon-01-be66e707dbf37c2f28d056d41361ca98.png

712 ms

index-icon-04-43d560965fe257b4e0d7dba5abd4d7d1.png

index-icon-04-43d560965fe257b4e0d7dba5abd4d7d1.png

715 ms

dot-8d28da93accb0b9763029bfd0faf9d26.gif

dot-8d28da93accb0b9763029bfd0faf9d26.gif

712 ms

img_01.jpg

img_01.jpg

1172 ms

img_01.jpg

img_01.jpg

1191 ms

img_01.jpg

img_01.jpg

1189 ms

spinner-e410903fed1dd24b052bb4ea67d318bf.gif

spinner-e410903fed1dd24b052bb4ea67d318bf.gif

699 ms

media-d1d3062141d3c7ca104224f8fcd88aed.png

media-d1d3062141d3c7ca104224f8fcd88aed.png

765 ms

img_bookcover.png

img_bookcover.png

1116 ms

ca-pub-4172411565750343.js

ca-pub-4172411565750343.js

61 ms

zrt_lookup.html

zrt_lookup.html

56 ms

show_ads_impl.js

show_ads_impl.js

60 ms

collect

collect

25 ms

yellowline-4ec9d81347b3eac588396b5d3c0334f4.png

yellowline-4ec9d81347b3eac588396b5d3c0334f4.png

796 ms

blog.php

blog.php

1097 ms

collect

collect

85 ms

ads

ads

387 ms

osd.js

osd.js

12 ms

ads

ads

261 ms

ads

ads

259 ms

css

css

27 ms

m_js_controller.js

m_js_controller.js

40 ms

abg.js

abg.js

66 ms

favicon

favicon

181 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

178 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

142 ms

s

s

119 ms

x_button_blue2.svg

x_button_blue2.svg

99 ms

css

css

57 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

55 ms

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

5 ms

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

64 ms

nr-885.min.js

nr-885.min.js

23 ms

ui

ui

39 ms

dc0371340d

dc0371340d

51 ms

Accessibility Review

zaim.net accessibility score

82

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.

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

zaim.net 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

SEO Factors

zaim.net SEO score

97

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 Zaim.net 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 Zaim.net 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

zaim.net

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