Tools & Wizards About Us
invalance.co.jp screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

invalance.co.jp

72（ナナニー）｜お金の学びから実践まで（インヴァランス）

Page Load Speed

8.1 sec in total

First Response

996 ms

Resources Loaded

6.2 sec

Page Rendered

914 ms

invalance.co.jp screenshot

About Website

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

72（ナナニー）は、お金や投資のキホンから、不動産投資の実践までをトータルサポートしています。多くの投資用不動産の販売実績を持つインヴァランス（INVALANCE）が運営。マネーリテラシーの向上に役立つ情報を発信しています。

Visit invalance.co.jp

Key Findings

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

Performance Metrics

invalance.co.jp performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value34.3 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value5,050 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value23.9 s

1/100

10%

Network Requests Diagram

invalance.co.jp

996 ms

gtm.js

94 ms

js

93 ms

frontend-gtag.min.js

159 ms

jquery.min.js

43 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 71% of them (66 requests) were addressed to the original Invalance.co.jp, 10% (9 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Invalance.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 574.2 kB (7%)

Content Size

7.8 MB

After Optimization

7.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Invalance.co.jp main page is 7.8 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. Only a small number of websites need less resources to load. Images take 7.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 87.9 kB

  • Original 107.7 kB
  • After minification 95.6 kB
  • After compression 19.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. This page needs HTML code to be minified as it can gain 12.1 kB, which is 11% 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 87.9 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 485.2 kB

  • Original 7.4 MB
  • After minification 7.0 MB

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. Invalance images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 443 B

  • Original 171.2 kB
  • After minification 171.2 kB
  • After compression 170.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 758 B

  • Original 64.4 kB
  • After minification 64.3 kB
  • After compression 63.6 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. Invalance.co.jp has all CSS files already compressed.

Requests Breakdown

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

Requests Now

81

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

invalance.co.jp

invalance.co.jp

996 ms

gtm.js

gtm.js

94 ms

js

js

93 ms

frontend-gtag.min.js

frontend-gtag.min.js

159 ms

jquery.min.js

jquery.min.js

43 ms

jquery-migrate.min.js

jquery-migrate.min.js

45 ms

slick.min.js

slick.min.js

321 ms

css2

css2

58 ms

kitchen.juicer.cc

kitchen.juicer.cc

822 ms

css2

css2

76 ms

css

css

359 ms

swiper.css

swiper.css

436 ms

new_style.css

new_style.css

583 ms

js

js

108 ms

front.min.js

front.min.js

445 ms

t.min.js

t.min.js

448 ms

youtube.min.js

youtube.min.js

465 ms

swiper.min.js

swiper.min.js

833 ms

functions.js

functions.js

579 ms

new_common.js

new_common.js

589 ms

merit.js

merit.js

592 ms

utilityModule.min.js

utilityModule.min.js

1038 ms

e-202430.js

e-202430.js

39 ms

style.min.css

style.min.css

3 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

3 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

2 ms

css2

css2

18 ms

thumb_necessity002.jpg

thumb_necessity002.jpg

242 ms

72logo.svg

72logo.svg

213 ms

icn_header_nav_01.svg

icn_header_nav_01.svg

211 ms

icn_header_nav_02.svg

icn_header_nav_02.svg

216 ms

icn_header_link_01.svg

icn_header_link_01.svg

216 ms

icn_popup_01.svg

icn_popup_01.svg

419 ms

icn_link_01_dark.svg

icn_link_01_dark.svg

417 ms

img_mv_01_01.png

img_mv_01_01.png

507 ms

img_mv_01_02.png

img_mv_01_02.png

423 ms

img_mv_01_03.png

img_mv_01_03.png

506 ms

img_mv_01_04.png

img_mv_01_04.png

586 ms

img_mv_02_01.png

img_mv_02_01.png

573 ms

img_mv_02_02.png

img_mv_02_02.png

585 ms

img_mv_02_03.png

img_mv_02_03.png

571 ms

img_mv_02_04.png

img_mv_02_04.png

668 ms

img_mv_03_01.png

img_mv_03_01.png

853 ms

img_mv_03_02.png

img_mv_03_02.png

747 ms

img_mv_03_03.png

img_mv_03_03.png

747 ms

img_mv_03_04.png

img_mv_03_04.png

761 ms

img_basics_01.svg

img_basics_01.svg

758 ms

icn_book_01.svg

icn_book_01.svg

852 ms

icn_link_01.svg

icn_link_01.svg

911 ms

img_basics_02.svg

img_basics_02.svg

907 ms

icn_tiktok_01.svg

icn_tiktok_01.svg

1066 ms

img_tiktok_01.png

img_tiktok_01.png

1532 ms

img_grow_01.png

img_grow_01.png

1255 ms

img_grow_02.png

img_grow_02.png

1114 ms

img_grow_certainty_01.png

img_grow_certainty_01.png

1609 ms

owner_y_prof.jpg

owner_y_prof.jpg

1029 ms

owner_k_prof.jpg

owner_k_prof.jpg

1176 ms

72column_223i.png

72column_223i.png

1695 ms

72column_222i.png

72column_222i.png

1695 ms

72column_221i.png

72column_221i.png

1907 ms

icn_list_check_01.svg

icn_list_check_01.svg

1401 ms

img_lounge_woman_02.jpg

img_lounge_woman_02.jpg

1717 ms

thumb_necessity001.jpg

thumb_necessity001.jpg

231 ms

NISA_thumb.jpg

NISA_thumb.jpg

236 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

124 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEk75s.ttf

512 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk75s.ttf

552 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFM8k75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFM8k75s.ttf

561 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

560 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

560 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75s.ttf

561 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEj75s.ttf

659 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi75s.ttf

705 ms

X6XYTKIVDUW7GZTZPZNN4EUM5KH54KHF.woff

X6XYTKIVDUW7GZTZPZNN4EUM5KH54KHF.woff

70 ms

Satoshi-Bold.woff

Satoshi-Bold.woff

1481 ms

img_lounge_man_03.jpg

img_lounge_man_03.jpg

1548 ms

img_support_01.svg

img_support_01.svg

1636 ms

bg_about_01.jpg

bg_about_01.jpg

1956 ms

logo_about_01.svg

logo_about_01.svg

1622 ms

logo_footer_01.svg

logo_footer_01.svg

1428 ms

icn_social_youtube_01.svg

icn_social_youtube_01.svg

1485 ms

icn_social_tiktok_01.svg

icn_social_tiktok_01.svg

1567 ms

icn_social_twitter_01.svg

icn_social_twitter_01.svg

1570 ms

icn_social_instagram_01.svg

icn_social_instagram_01.svg

1499 ms

icn_social_rss_01.svg

icn_social_rss_01.svg

1546 ms

screen.min.css

screen.min.css

159 ms

screen.min.css

screen.min.css

158 ms

style.css

style.css

159 ms

style.css

style.css

159 ms

slick.min.css

slick.min.css

160 ms

slick.min.css

slick.min.css

158 ms

slick-theme.min.css

slick-theme.min.css

160 ms

slick-theme.min.css

slick-theme.min.css

159 ms

Accessibility Review

invalance.co.jp accessibility score

81

Accessibility Issues

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

Buttons do not have an accessible name

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

invalance.co.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

invalance.co.jp SEO score

99

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

invalance.co.jp

Open Graph data is detected on the main page of Invalance. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: