Tools & Wizards About Us
kodomo-qq.jp screenshot

Report Summary

  • 81

    Performance

    Renders faster than
    86% 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

  • 90

    SEO

    Google-friendlier than
    68% of websites

kodomo-qq.jp

こどもの救急（ONLINE-QQ)

Page Load Speed

5.3 sec in total

First Response

783 ms

Resources Loaded

4.4 sec

Page Rendered

102 ms

kodomo-qq.jp screenshot

About Website

Click here to check amazing Kodomo QQ content for Japan. Otherwise, check out these important facts you probably never knew about kodomo-qq.jp

こどもの救急（ONLINE-QQ)

Visit kodomo-qq.jp

Key Findings

We analyzed Kodomo-qq.jp page load time and found that the first response time was 783 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

kodomo-qq.jp performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

kodomo-qq.jp

783 ms

style.css

365 ms

jquery-1.8.0.min.js

913 ms

aw_enquete.js

372 ms

rollover.js

374 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 84% of them (97 requests) were addressed to the original Kodomo-qq.jp, 5% (6 requests) were made to Apis.google.com and 3% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Kodomo-qq.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 175.4 kB (28%)

Content Size

622.2 kB

After Optimization

446.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kodomo-qq.jp main page is 622.2 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 309.0 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 15.0 kB

  • Original 20.3 kB
  • After minification 18.0 kB
  • After compression 5.3 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 2.4 kB, which is 12% 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 15.0 kB or 74% of the original size.

Image Optimization

-20%

Potential reduce by 62.2 kB

  • Original 309.0 kB
  • After minification 246.8 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. Obviously, Kodomo QQ needs image optimization as it can save up to 62.2 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-27%

Potential reduce by 71.3 kB

  • Original 259.6 kB
  • After minification 257.6 kB
  • After compression 188.3 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 71.3 kB or 27% of the original size.

CSS Optimization

-81%

Potential reduce by 26.9 kB

  • Original 33.2 kB
  • After minification 26.5 kB
  • After compression 6.3 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. Kodomo-qq.jp needs all CSS files to be minified and compressed as it can save up to 26.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (33%)

Requests Now

112

After Optimization

75

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kodomo-qq.jp

kodomo-qq.jp

783 ms

style.css

style.css

365 ms

jquery-1.8.0.min.js

jquery-1.8.0.min.js

913 ms

aw_enquete.js

aw_enquete.js

372 ms

rollover.js

rollover.js

374 ms

jquery.smoothScroll.js

jquery.smoothScroll.js

379 ms

base.css

base.css

183 ms

common.css

common.css

193 ms

contents.css

contents.css

378 ms

locale.css

locale.css

196 ms

modified.css

modified.css

206 ms

ttl_header.png

ttl_header.png

388 ms

line_side_top.png

line_side_top.png

187 ms

ttl_side_nav.png

ttl_side_nav.png

184 ms

btn_side_01.png

btn_side_01.png

183 ms

btn_side_02.png

btn_side_02.png

193 ms

btn_side_03.png

btn_side_03.png

187 ms

btn_side_04.png

btn_side_04.png

364 ms

btn_side_05.png

btn_side_05.png

365 ms

btn_side_06.png

btn_side_06.png

371 ms

btn_side_07.png

btn_side_07.png

374 ms

btn_side_08.png

btn_side_08.png

387 ms

btn_side_10.png

btn_side_10.png

546 ms

btn_side_11.png

btn_side_11.png

547 ms

btn_side_12.png

btn_side_12.png

557 ms

btn_side_13.png

btn_side_13.png

560 ms

btn_side_14.png

btn_side_14.png

573 ms

btn_side_15.png

btn_side_15.png

574 ms

btn_side_16.png

btn_side_16.png

727 ms

btn_side_17.png

btn_side_17.png

729 ms

btn_side_18.png

btn_side_18.png

742 ms

btn_side_19.png

btn_side_19.png

746 ms

line_main_top.png

line_main_top.png

763 ms

ttl_top.png

ttl_top.png

764 ms

img_top_s1.png

img_top_s1.png

908 ms

ttl_top_s1.png

ttl_top_s1.png

911 ms

img_top_s2.png

img_top_s2.png

927 ms

ttl_top_s2.png

ttl_top_s2.png

932 ms

img_top_s3.png

img_top_s3.png

954 ms

ttl_top_s3.png

ttl_top_s3.png

955 ms

img_top_s4.png

img_top_s4.png

1088 ms

ttl_top_s4.png

ttl_top_s4.png

1093 ms

btn_p6_top_kiyaku.png

btn_p6_top_kiyaku.png

1113 ms

btn_top_p12_ban01.png

btn_top_p12_ban01.png

1118 ms

img_p5_top_right01.png

img_p5_top_right01.png

1145 ms

ttl_p5_top_jiko.png

ttl_p5_top_jiko.png

1145 ms

widgets.js

widgets.js

73 ms

btn_p5_top_jiko01.png

btn_p5_top_jiko01.png

1245 ms

like.php

like.php

261 ms

plusone.js

plusone.js

35 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

27 ms

fastbutton

fastbutton

51 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

159 ms

postmessageRelay

postmessageRelay

78 ms

developers.google.com

developers.google.com

358 ms

btn_p5_top_jikonav01.png

btn_p5_top_jikonav01.png

1096 ms

btn_p5_top_jikonav02.png

btn_p5_top_jikonav02.png

1119 ms

btn_p5_top_jikonav03.png

btn_p5_top_jikonav03.png

1122 ms

btn_p5_top_jikonav04.png

btn_p5_top_jikonav04.png

1153 ms

btn_p5_top_jikonav05.png

btn_p5_top_jikonav05.png

1149 ms

3604799710-postmessagerelay.js

3604799710-postmessagerelay.js

17 ms

rpc:shindig_random.js

rpc:shindig_random.js

12 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

settings

settings

74 ms

TttXWwYVW0v.js

TttXWwYVW0v.js

23 ms

FEppCFCt76d.png

FEppCFCt76d.png

22 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

25 ms

btn_p5_top_jikonav06.png

btn_p5_top_jikonav06.png

1091 ms

btn_p5_top_jikonav07.png

btn_p5_top_jikonav07.png

1096 ms

btn_p5_top_jikonav08.png

btn_p5_top_jikonav08.png

1116 ms

btn_p5_top_ban01.png

btn_p5_top_ban01.png

1121 ms

btn_p5_top_ban02.png

btn_p5_top_ban02.png

1145 ms

btn_p6_top_ban03.png

btn_p6_top_ban03.png

1144 ms

embeds

embeds

22 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

34 ms

btn_p6_top_ban04.png

btn_p6_top_ban04.png

1091 ms

btn_p6_top_ban05.png

btn_p6_top_ban05.png

1096 ms

bg_p5_top_jiko.png

bg_p5_top_jiko.png

1116 ms

bg_footer.png

bg_footer.png

1121 ms

ico_footer_admin.png

ico_footer_admin.png

1149 ms

btn_side_01_o.png

btn_side_01_o.png

192 ms

btn_side_02_o.png

btn_side_02_o.png

187 ms

btn_side_03_o.png

btn_side_03_o.png

183 ms

btn_side_04_o.png

btn_side_04_o.png

182 ms

btn_side_05_o.png

btn_side_05_o.png

192 ms

btn_side_06_o.png

btn_side_06_o.png

188 ms

btn_side_07_o.png

btn_side_07_o.png

364 ms

btn_side_08_o.png

btn_side_08_o.png

365 ms

btn_side_10_o.png

btn_side_10_o.png

371 ms

btn_side_11_o.png

btn_side_11_o.png

373 ms

btn_side_12_o.png

btn_side_12_o.png

382 ms

btn_side_13_o.png

btn_side_13_o.png

383 ms

btn_side_14_o.png

btn_side_14_o.png

545 ms

btn_side_15_o.png

btn_side_15_o.png

547 ms

btn_side_16_o.png

btn_side_16_o.png

557 ms

btn_side_17_o.png

btn_side_17_o.png

560 ms

btn_side_18_o.png

btn_side_18_o.png

573 ms

btn_side_19_o.png

btn_side_19_o.png

573 ms

btn_p6_top_kiyaku_o.png

btn_p6_top_kiyaku_o.png

726 ms

ttl_p5_top_jiko_o.png

ttl_p5_top_jiko_o.png

729 ms

btn_p5_top_jiko01_o.png

btn_p5_top_jiko01_o.png

742 ms

btn_p5_top_jikonav01_o.png

btn_p5_top_jikonav01_o.png

745 ms

btn_p5_top_jikonav02_o.png

btn_p5_top_jikonav02_o.png

763 ms

btn_p5_top_jikonav03_o.png

btn_p5_top_jikonav03_o.png

764 ms

btn_p5_top_jikonav04_o.png

btn_p5_top_jikonav04_o.png

907 ms

btn_p5_top_jikonav05_o.png

btn_p5_top_jikonav05_o.png

910 ms

btn_p5_top_jikonav06_o.png

btn_p5_top_jikonav06_o.png

927 ms

btn_p5_top_jikonav07_o.png

btn_p5_top_jikonav07_o.png

932 ms

btn_p5_top_jikonav08_o.png

btn_p5_top_jikonav08_o.png

954 ms

btn_p5_top_ban01_o.png

btn_p5_top_ban01_o.png

955 ms

btn_p5_top_ban02_o.png

btn_p5_top_ban02_o.png

1089 ms

btn_p6_top_ban03_o.png

btn_p6_top_ban03_o.png

1092 ms

btn_p6_top_ban04_o.png

btn_p6_top_ban04_o.png

1113 ms

btn_p6_top_ban05_o.png

btn_p6_top_ban05_o.png

1119 ms

Accessibility Review

kodomo-qq.jp accessibility score

81

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

kodomo-qq.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

kodomo-qq.jp SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Kodomo-qq.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 Kodomo-qq.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

kodomo-qq.jp

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