5.2 sec in total
348 ms
4.4 sec
444 ms
Click here to check amazing Cocoro H content for Japan. Otherwise, check out these important facts you probably never knew about cocoro-h.jp
なかなか寝付けない、何もやる気がしない、できれば薬は飲みたくない - うつ病を正しく理解しましょう。- うつ病とパニック障害の情報・サポートサイト こころの陽だまり
Visit cocoro-h.jpWe analyzed Cocoro-h.jp page load time and found that the first response time was 348 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
cocoro-h.jp performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value14.2 s
0/100
25%
Value6.9 s
34/100
10%
Value260 ms
83/100
30%
Value0.321
36/100
15%
Value7.9 s
43/100
10%
348 ms
160 ms
673 ms
445 ms
790 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 96% of them (50 requests) were addressed to the original Cocoro-h.jp, 2% (1 request) were made to Pfizer.co.jp and 2% (1 request) were made to Pfizer.122.2o7.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Cocoro-h.jp.
Page size can be reduced by 437.4 kB (14%)
3.1 MB
2.7 MB
In fact, the total size of Cocoro-h.jp main page is 3.1 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 2.8 MB which makes up the majority of the site volume.
Potential reduce by 9.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.5 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 9.9 kB or 75% of the original size.
Potential reduce by 141.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. Cocoro H images are well optimized though.
Potential reduce by 195.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 195.4 kB or 71% of the original size.
Potential reduce by 90.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. Cocoro-h.jp needs all CSS files to be minified and compressed as it can save up to 90.5 kB or 88% of the original size.
Number of requests can be reduced by 8 (16%)
51
43
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cocoro H. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
cocoro-h.jp
348 ms
initialize.css
160 ms
general.css
673 ms
top.css
445 ms
jquery.lib.js
790 ms
base.js
477 ms
jquery.bxslider.min.js
476 ms
top.js
320 ms
urchin.js
809 ms
jquery.belatedPNG.js
161 ms
html5shiv.js
164 ms
s_code_cocoro-h.js
160 ms
s_code_common.js
716 ms
__utm.gif
160 ms
hdr_bg_t_pc.jpg
163 ms
hdr_img_leaf_pc.png
444 ms
hdr_h_pc.png
152 ms
hdr_search_btn.png
163 ms
hdr_logo_pfizer.png
164 ms
bnr_qa_pc.png
278 ms
bnr_qa.png
595 ms
bnr_selfcheck_pc.png
320 ms
bnr_selfcheck.png
806 ms
bnr_checklist_pc.png
648 ms
bnr_checklist.png
1083 ms
bnr_meal_pc.png
812 ms
bnr_meal.png
901 ms
top_intro_bg_pc.jpg
1064 ms
top_slide_img_01.jpg
1300 ms
top_slide_img_02.jpg
1299 ms
top_slide_img_03.jpg
1471 ms
top_slide_img_04.jpg
1222 ms
bnr_hospital.png
1533 ms
top_content_bg_t_pc.png
1251 ms
top_content_bg_l_pc.jpg
1381 ms
top_content_bg_r_pc.jpg
1572 ms
top_content_bg_m_pc.jpg
1480 ms
top_content_img_l_pc.png
1644 ms
top_content_img_r_02_pc.png
1547 ms
top_content_img_r_01_pc.png
1640 ms
top_purpose_box_01_bg_pc.png
1651 ms
top_purpose_box_02_bg_pc.png
1713 ms
top_purpose_box_03_bg_pc.png
1722 ms
top_purpose_box_04_bg_pc.png
1898 ms
top_partner_box_01_bg_pc.png
1966 ms
top_partner_box_02_bg_pc.png
2127 ms
ftr_pagetop.png
1816 ms
ftr_bnr_panic.png
1864 ms
ftr_logo_pfizer.png
1868 ms
top_slide_arw_l.png
1864 ms
top_slide_arw_r.png
1868 ms
s85909137488342
45 ms
cocoro-h.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.
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
Links do not have a discernible name
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.
cocoro-h.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
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
cocoro-h.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 Cocoro-h.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 Cocoro-h.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.
cocoro-h.jp
Open Graph description is not detected on the main page of Cocoro H. 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: