23.6 sec in total
10.3 sec
13.2 sec
146 ms
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.jpWe analyzed Kodomo-qq.jp page load time and found that the first response time was 10.3 sec and then it took 13.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
kodomo-qq.jp performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value4.9 s
29/100
25%
Value6.6 s
38/100
10%
Value360 ms
71/100
30%
Value0.024
100/100
15%
Value4.7 s
80/100
10%
10302 ms
354 ms
1058 ms
363 ms
365 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 80% of them (72 requests) were addressed to the original Kodomo-qq.jp, 9% (8 requests) were made to Apis.google.com and 3% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (10.3 sec) belongs to the original domain Kodomo-qq.jp.
Page size can be reduced by 158.8 kB (41%)
387.5 kB
228.7 kB
In fact, the total size of Kodomo-qq.jp main page is 387.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. 35% of websites need less resources to load. Images take 225.9 kB which makes up the majority of the site volume.
Potential reduce by 11.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 1.8 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 11.9 kB or 71% of the original size.
Potential reduce by 50.3 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 50.3 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 76.8 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 76.8 kB or 64% of the original size.
Potential reduce by 19.8 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 19.8 kB or 82% of the original size.
Number of requests can be reduced by 24 (27%)
88
64
The browser has sent 88 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 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
kodomo-qq.jp
10302 ms
style.css
354 ms
jquery-1.8.0.min.js
1058 ms
aw_enquete.js
363 ms
rollover.js
365 ms
jquery.smoothScroll.js
725 ms
base.css
172 ms
common.css
177 ms
contents.css
549 ms
ttl_header.png
341 ms
line_side_top.png
177 ms
ttl_side_nav.png
178 ms
btn_side_01.png
185 ms
btn_side_02.png
182 ms
btn_side_03.png
181 ms
btn_side_04.png
354 ms
btn_side_05.png
354 ms
btn_side_06.png
361 ms
btn_side_07.png
363 ms
btn_side_08.png
365 ms
btn_side_09.png
511 ms
btn_side_10.png
530 ms
btn_side_11.png
529 ms
btn_side_12.png
541 ms
btn_side_13.png
544 ms
btn_side_14.png
546 ms
btn_side_15.png
682 ms
btn_side_16.png
705 ms
btn_side_17.png
705 ms
btn_side_18.png
721 ms
btn_side_19.png
725 ms
btn_ban_jiko.png
727 ms
ban_side_kodomoqq.png
851 ms
ban_side_n8000.png
881 ms
ban_side_koikisaigai.png
882 ms
ttl_top.png
901 ms
img_top_s1.png
905 ms
ttl_top_s1.png
908 ms
img_top_s2.png
1021 ms
ttl_top_s2.png
1057 ms
img_top_s3.png
1056 ms
ttl_top_s3.png
1080 ms
img_top_s4.png
1086 ms
ttl_top_s4.png
1090 ms
widgets.js
36 ms
img_top_e1.png
1182 ms
plusone.js
98 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
16 ms
like.php
200 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
18 ms
cb=gapi.loaded_0
19 ms
cb=gapi.loaded_1
35 ms
fastbutton
92 ms
postmessageRelay
36 ms
btn_top_rules.png
1062 ms
ban_top_e1.png
1063 ms
ban_top_e2.png
1085 ms
btn_ban_4pc.png
1095 ms
line_main_top.png
1095 ms
3193398744-postmessagerelay.js
58 ms
rpc:shindig_random.js
45 ms
cb=gapi.loaded_0
38 ms
cb=gapi.loaded_1
35 ms
grlryt2bdKIyfMSOhzd1eA.woff
77 ms
jot
105 ms
cb=gapi.loaded_0
10 ms
fy8tT2klpgR.js
290 ms
LVx-xkvaJ0b.png
329 ms
bg_footer.png
1028 ms
ico_footer_admin.png
1060 ms
btn_side_01_o.png
172 ms
btn_side_02_o.png
178 ms
btn_side_03_o.png
179 ms
btn_side_04_o.png
183 ms
btn_side_05_o.png
183 ms
btn_side_06_o.png
182 ms
btn_side_07_o.png
342 ms
btn_side_08_o.png
354 ms
btn_side_09_o.png
354 ms
btn_side_10_o.png
362 ms
btn_side_11_o.png
363 ms
btn_side_12_o.png
365 ms
btn_side_13_o.png
512 ms
btn_side_14_o.png
530 ms
btn_side_15_o.png
531 ms
btn_side_16_o.png
541 ms
btn_side_17_o.png
544 ms
btn_side_18_o.png
545 ms
btn_side_19_o.png
682 ms
btn_top_rules_o.png
706 ms
kodomo-qq.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
kodomo-qq.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
kodomo-qq.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
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.
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: