Tools & Wizards About Us
kokuho-keisan.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

kokuho-keisan.com

国民健康保険料計算機｜全国の市区町村別に自動計算｜早見表あり

Page Load Speed

3.7 sec in total

First Response

605 ms

Resources Loaded

2.9 sec

Page Rendered

215 ms

kokuho-keisan.com screenshot

About Website

Click here to check amazing Kokuho Keisan content for Japan. Otherwise, check out these important facts you probably never knew about kokuho-keisan.com

あなたの年齢と年収からお住まいの市区町村の国民健康保険料を自動計算します。

Visit kokuho-keisan.com

Key Findings

We analyzed Kokuho-keisan.com page load time and found that the first response time was 605 ms and then it took 3.1 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

kokuho-keisan.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value1

2/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

kokuho-keisan.com

605 ms

www.kokuho-keisan.com

1313 ms

common.css

684 ms

logo.png

532 ms

topimage.jpg

911 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 55% of them (18 requests) were addressed to the original Kokuho-keisan.com, 27% (9 requests) were made to Pagead2.googlesyndication.com and 9% (3 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Kokuho-keisan.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 43.0 kB (12%)

Content Size

344.5 kB

After Optimization

301.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kokuho-keisan.com main page is 344.5 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. 45% of websites need less resources to load. Images take 221.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 9.3 kB

  • Original 12.4 kB
  • After minification 12.0 kB
  • After compression 3.1 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 9.3 kB or 75% of the original size.

Image Optimization

-6%

Potential reduce by 12.2 kB

  • Original 221.6 kB
  • After minification 209.4 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. Kokuho Keisan images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 9.8 kB

  • Original 96.4 kB
  • After minification 96.2 kB
  • After compression 86.5 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

-83%

Potential reduce by 11.7 kB

  • Original 14.1 kB
  • After minification 11.3 kB
  • After compression 2.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. Kokuho-keisan.com needs all CSS files to be minified and compressed as it can save up to 11.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (58%)

Requests Now

31

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kokuho-keisan.com

kokuho-keisan.com

605 ms

www.kokuho-keisan.com

www.kokuho-keisan.com

1313 ms

common.css

common.css

684 ms

logo.png

logo.png

532 ms

topimage.jpg

topimage.jpg

911 ms

modelcase01.jpg

modelcase01.jpg

485 ms

modelcase02.jpg

modelcase02.jpg

701 ms

r1.png

r1.png

366 ms

r2.png

r2.png

572 ms

r3.png

r3.png

572 ms

r4.png

r4.png

695 ms

r5.png

r5.png

694 ms

r6.png

r6.png

722 ms

r7.png

r7.png

727 ms

r8.png

r8.png

735 ms

r9.png

r9.png

755 ms

r10.png

r10.png

748 ms

adsbygoogle.js

adsbygoogle.js

5 ms

setuyaku.png

setuyaku.png

969 ms

ca-pub-5281375524168306.js

ca-pub-5281375524168306.js

83 ms

zrt_lookup.html

zrt_lookup.html

169 ms

show_ads_impl.js

show_ads_impl.js

67 ms

dc.js

dc.js

90 ms

ads

ads

256 ms

osd.js

osd.js

37 ms

__utm.gif

__utm.gif

22 ms

4781320055297797082

4781320055297797082

19 ms

abg.js

abg.js

7 ms

m_js_controller.js

m_js_controller.js

18 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

47 ms

s

s

29 ms

x_button_blue2.png

x_button_blue2.png

31 ms

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

3 ms

Accessibility Review

kokuho-keisan.com accessibility score

76

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

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

kokuho-keisan.com 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

Serves images with low resolution

SEO Factors

kokuho-keisan.com SEO score

67

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

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 Kokuho-keisan.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 Kokuho-keisan.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

kokuho-keisan.com

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