Access iihone.jp. 骨粗しょう症（骨粗鬆症）ホームページ/いいほね.jp(iihone.jp)

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.324

35/100

15%

TTI (Time to Interactive)

Value5.1 s

75/100

10%

iihone.jp

594 ms

common.css

311 ms

index.css

344 ms

jquery-1.4.2.min.js

1067 ms

ga.js

358 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 97% of them (67 requests) were addressed to the original Iihone.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Iihone.jp.

Content Size

1.8 MB

After Optimization

1.7 MB

In fact, the total size of Iihone.jp main page is 1.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. 25% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 70.0 kB

Original 81.6 kB
After minification 58.7 kB
After compression 11.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 22.9 kB, which is 28% 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 70.0 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 19.5 kB

Original 1.6 MB
After minification 1.6 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. Iihone images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 48.7 kB

Original 95.1 kB
After minification 94.9 kB
After compression 46.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 48.7 kB or 51% of the original size.

CSS Optimization

-81%

Potential reduce by 13.1 kB

Original 16.2 kB
After minification 12.8 kB
After compression 3.1 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. Iihone.jp needs all CSS files to be minified and compressed as it can save up to 13.1 kB or 81% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

JA
Encoding

SHIFT-JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iihone.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 Iihone.jp main page’s claimed encoding is shift-jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

iihone.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

骨粗しょう症（骨粗鬆症）ホームページ/いいほね.jp(iihone.jp)

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

iihone.jp

common.css

index.css

jquery-1.4.2.min.js

ga.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

iihone.jp

common.css

index.css

jquery-1.4.2.min.js

ga.js

top_randam_doctor.js

analytics.js

bg_main.jpg

logo.jpg

header_text.jpg

btn_search.jpg

gnavi_01.jpg

gnavi_02.jpg

gnavi_03.jpg

gnavi_04.jpg

gnavi_05.jpg

gnavi_06.jpg

gnavi_07.jpg

eyecatch.jpg

btn_check.jpg

line_dot.gif

bg_list.jpg

line_list.gif

img_test.jpg

tit_test.jpg

btn_test.jpg

img_treatment.jpg

tit_treatment.jpg

btn_treatment.jpg

img_prevention.jpg

tit_prevention.jpg

btn_prevention.jpg

h2.jpg

btn_know.jpg

btn_investigate.jpg

btn_disease.jpg

banner_dr-column.jpg

dot_ffcc01.gif

tit_search.jpg

btn_form.jpg

tit_teacher.jpg

ajax-loader.gif

getContents.php