7.9 sec in total
315 ms
7.3 sec
279 ms
Visit cocolotus.com now to see the best up-to-date Cocolotus content for Japan and also check out these interesting facts you probably never knew about cocolotus.com
多くの人の経験や思い、生き方を通じて、自分自身の生き方や周囲との「つながり」を見つめていく さまざまなコンテンツを提供しています。
Visit cocolotus.comWe analyzed Cocolotus.com page load time and found that the first response time was 315 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
cocolotus.com performance score
315 ms
1185 ms
293 ms
295 ms
15 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 94% of them (80 requests) were addressed to the original Cocolotus.com, 2% (2 requests) were made to Ajax.googleapis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Cocolotus.com.
Page size can be reduced by 165.5 kB (11%)
1.5 MB
1.3 MB
In fact, the total size of Cocolotus.com main page is 1.5 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. 30% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 32.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. This page needs HTML code to be minified as it can gain 4.9 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 32.1 kB or 78% of the original size.
Potential reduce by 81.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. Cocolotus images are well optimized though.
Potential reduce by 11.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 11.5 kB or 17% of the original size.
Potential reduce by 40.6 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. Cocolotus.com needs all CSS files to be minified and compressed as it can save up to 40.6 kB or 86% of the original size.
Number of requests can be reduced by 20 (24%)
83
63
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cocolotus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
cocolotus.com
315 ms
www.cocolotus.com
1185 ms
style.css
293 ms
ks.css
295 ms
jsapi
15 ms
jquery.fade.js
295 ms
jquery.min.js
30 ms
jquery.fancybox-1.3.4.pack.js
438 ms
jquery.fancybox-1.3.4.css
295 ms
reset.css
292 ms
common.css
584 ms
jquery.min.js
13 ms
rogo.jpg
295 ms
submn_arrow.jpg
293 ms
mainimg.jpg
1457 ms
mainimg1.jpg
1319 ms
mainimg2.jpg
1309 ms
mainimg3.jpg
1476 ms
mainimg4.jpg
1598 ms
g_navi0.jpg
582 ms
g_navi1.jpg
1032 ms
g_navi2.jpg
1323 ms
g_navi3.jpg
1745 ms
search_bg.jpg
1611 ms
search_title.jpg
1613 ms
search_btn.jpg
1745 ms
banner-validation.jpg
1914 ms
banner-tsuyuno.jpg
1887 ms
banner-moyamoya.jpg
2048 ms
box_base_top.jpg
1903 ms
box_base.jpg
2034 ms
box_title.jpg
2035 ms
box_title0.jpg
2185 ms
list_btn.jpg
2193 ms
dot.jpg
2204 ms
qa_icon.jpg
2324 ms
category_icon.jpg
2325 ms
kiji_icon_101.jpg
2341 ms
kiji_icon_204.jpg
2475 ms
kiji_icon_306.jpg
2483 ms
kiji_icon_310.jpg
2494 ms
column_icon.jpg
2615 ms
kiji_icon_102.jpg
2614 ms
kiji_icon_304.jpg
2631 ms
info_icon.jpg
2766 ms
kiji_icon_108.jpg
2772 ms
kiji_icon_307.jpg
2791 ms
kiji_icon_313.jpg
2904 ms
ga.js
14 ms
__utm.gif
14 ms
kiji_icon_316.jpg
2639 ms
kiji_icon_105.jpg
2637 ms
kiji_icon_315.jpg
2482 ms
kiji_icon_404.jpg
2048 ms
kiji_icon_402.jpg
1782 ms
box_title2.jpg
1886 ms
medal_gold.jpg
1888 ms
interview_icon.jpg
1766 ms
kiji_icon_103.jpg
1879 ms
kiji_icon_104.jpg
1773 ms
kiji_icon_107.jpg
1778 ms
kiji_icon_201.jpg
1880 ms
kiji_icon_206.jpg
1757 ms
kiji_icon_317.jpg
1764 ms
kiji_icon_401.jpg
1756 ms
medal_silver.jpg
1756 ms
medal_bronze.jpg
1765 ms
kiji_icon_207.jpg
1749 ms
kiji_icon_303.jpg
1755 ms
kiji_icon_312.jpg
1751 ms
box_base_bottom.jpg
1748 ms
page_top.jpg
1756 ms
ichigo_bg.jpg
1911 ms
ichigo_title.jpg
1748 ms
ichigo_footer.jpg
1754 ms
popularity_word_title.jpg
1746 ms
subnavi_dot.jpg
1748 ms
link_title.jpg
1756 ms
harukanaruhigashi_banner.jpg
1869 ms
harukanaruhigashi_banner2.jpg
1755 ms
tayutau_banner.jpg
1763 ms
footer_bg.jpg
2531 ms
footer_navi_arrow.jpg
1747 ms
footer_dot.jpg
1755 ms
footer_navi_dot.gif
1861 ms
cocolotus.com SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cocolotus.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Cocolotus.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.
cocolotus.com
Open Graph description is not detected on the main page of Cocolotus. 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: