Tools & Wizards About Us
how.or.jp screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 81% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

how.or.jp

住宅保証支援機構

Page Load Speed

3.9 sec in total

First Response

853 ms

Resources Loaded

2.7 sec

Page Rendered

293 ms

how.or.jp screenshot

About Website

Welcome to how.or.jp homepage info - get ready to check How best content for Japan right away, or after learning these important things about how.or.jp

一般財団法人住宅保証支援機構は住宅の性能保証等に係る調査研究を幅広く実施するとともに、住宅保証基金や住宅購入者等救済基金の運営を通じて、住宅購入者を大きな損害から守ります。

Visit how.or.jp

Key Findings

We analyzed How.or.jp page load time and found that the first response time was 853 ms and then it took 3 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

how.or.jp performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value170 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.2 s

74/100

10%

Network Requests Diagram

how.or.jp

853 ms

bootstrap_custom.css

1505 ms

bootstrap-icons.css

24 ms

base2.css

840 ms

analytics.js

340 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 62% of them (8 requests) were addressed to the original How.or.jp, 23% (3 requests) were made to Cdn.jsdelivr.net and 8% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain How.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 261.4 kB (44%)

Content Size

600.6 kB

After Optimization

339.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of How.or.jp main page is 600.6 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. 15% of websites need less resources to load. Images take 330.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 16.1 kB

  • Original 20.7 kB
  • After minification 17.6 kB
  • After compression 4.6 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 3.1 kB, which is 15% 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 16.1 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 21.9 kB

  • Original 330.6 kB
  • After minification 308.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. How images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 314 B

  • Original 715 B
  • After minification 597 B
  • After compression 401 B

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 314 B or 44% of the original size.

CSS Optimization

-90%

Potential reduce by 223.2 kB

  • Original 248.6 kB
  • After minification 177.9 kB
  • After compression 25.5 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. How.or.jp needs all CSS files to be minified and compressed as it can save up to 223.2 kB or 90% of the original size.

Requests Breakdown

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

Requests Now

11

After Optimization

7

  • Images
  • JavaScript
  • CSS

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of How. 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

how.or.jp

how.or.jp

853 ms

bootstrap_custom.css

bootstrap_custom.css

1505 ms

bootstrap-icons.css

bootstrap-icons.css

24 ms

base2.css

base2.css

840 ms

analytics.js

analytics.js

340 ms

bootstrap.min.js

bootstrap.min.js

5 ms

jquery-3.6.0.js

jquery-3.6.0.js

20 ms

script.js

script.js

171 ms

js

js

131 ms

logo_w_title.png

logo_w_title.png

505 ms

main_visual.jpg

main_visual.jpg

672 ms

jprs_siteseal_140x59_OV.png

jprs_siteseal_140x59_OV.png

339 ms

bootstrap-icons.woff

bootstrap-icons.woff

11 ms

Accessibility Review

how.or.jp accessibility score

93

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

Best Practices

how.or.jp 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

High

Page has valid source maps

SEO Factors

how.or.jp SEO score

98

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 How.or.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 How.or.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

how.or.jp

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