3.7 sec in total
596 ms
2.4 sec
692 ms
Click here to check amazing Kokoo content for Japan. Otherwise, check out these important facts you probably never knew about kokoo.jp
こころが楽になる方法を心理の根本にアプローチしながら解説しています。 楽に自由になっていきましょう。
Visit kokoo.jpWe analyzed Kokoo.jp page load time and found that the first response time was 596 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
kokoo.jp performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value11.8 s
0/100
25%
Value8.8 s
16/100
10%
Value2,000 ms
8/100
30%
Value0.208
60/100
15%
Value17.5 s
4/100
10%
596 ms
11 ms
7 ms
9 ms
12 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 38% of them (28 requests) were addressed to the original Kokoo.jp, 27% (20 requests) were made to Static.xx.fbcdn.net and 18% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Kokoo.jp.
Page size can be reduced by 281.7 kB (56%)
504.1 kB
222.4 kB
In fact, the total size of Kokoo.jp main page is 504.1 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. 55% of websites need less resources to load. Javascripts take 217.2 kB which makes up the majority of the site volume.
Potential reduce by 55.5 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 55.5 kB or 81% of the original size.
Potential reduce by 9.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. Kokoo images are well optimized though.
Potential reduce by 135.1 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 135.1 kB or 62% of the original size.
Potential reduce by 81.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. Kokoo.jp needs all CSS files to be minified and compressed as it can save up to 81.3 kB or 72% of the original size.
Number of requests can be reduced by 33 (45%)
73
40
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kokoo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
kokoo.jp
596 ms
337880cd01e1fdd5892851ed0e405714.css
11 ms
styles.css
7 ms
pagenavi-css.css
9 ms
style.css
12 ms
genericons.css
50 ms
wpp.css
9 ms
mtssb-front.css
12 ms
style.css
6 ms
analytics.js
14 ms
sdk.js
242 ms
search.png
25 ms
%E3%82%84%E3%82%89%E3%81%84%E3%81%9F%E3%81%84%E3%81%93%E3%81%A8%E3%82%A6%E3%83%A6%E3%83%8B%E6%B9%96-500x320.jpg
25 ms
%E6%B0%97%E7%96%B2%E3%82%8C%E3%81%AA%E7%94%BA-500x320.jpg
1070 ms
collect
11 ms
ms_cp_capbg0.gif
517 ms
feedly-follow-rectangle-flat-big_2x.png
11 ms
platform.js
154 ms
fe95dd26f4d0c00abc8ff141918680ce.js
27 ms
%E5%84%AA%E6%9F%94%E4%B8%8D%E6%96%AD%E3%81%AA%E7%89%9B-500x320.jpg
117 ms
%E3%81%8A%E3%81%8B%E3%81%97%E3%81%84%E6%B5%B7-500x320.jpg
99 ms
%E3%81%82%E3%81%92%E3%81%BE%E3%82%93%E3%81%A8%E6%B5%B7-500x320.jpg
901 ms
%E6%9C%9F%E5%BE%85%E3%81%A8%E3%83%97%E3%83%AC%E3%83%83%E3%82%B7%E3%83%A3%E3%83%BC%E3%81%A8%E9%87%8E%E8%89%AF-500x320.jpg
943 ms
%E5%AB%8C%E3%81%84%E3%81%AA%E6%B0%B4%E8%BE%BA-500x320.jpg
1097 ms
%E3%82%A4%E3%83%A9%E3%82%A4%E3%83%A9%E3%81%99%E3%82%8B%E3%81%8B%E3%82%89%E5%B1%B1%E5%B0%8F%E5%B1%8B%E6%9A%AE%E3%82%89%E3%81%971-500x320.jpg
1265 ms
%E7%94%9F%E3%81%8D%E3%82%8B%E3%81%AE%E3%81%8C%E8%BE%9B%E3%81%84%E7%B6%9A%E3%81%8F%E7%B7%9A%E8%B7%AF-500x320.jpg
1500 ms
%E4%BB%95%E4%BA%8B%E3%81%AE%E3%82%84%E3%82%8A%E3%81%8C%E3%81%84%E3%81%A3%E3%81%A6%E4%BD%95%E3%81%A0%E3%82%8D%E3%81%86-500x320.jpg
1826 ms
prof-side.jpg
951 ms
ebookhyushi1.png
952 ms
work-banar.png
956 ms
open-banar.png
957 ms
amebro.gif
957 ms
download2.png
957 ms
ms_cp_icon_circle_right.gif
554 ms
ms_cp_btn0.gif
555 ms
wp-emoji-release.min.js
904 ms
130 ms
likebox.php
207 ms
xd_arbiter.php
146 ms
xd_arbiter.php
270 ms
likebox.php
204 ms
hDvwL1_H7g-.css
177 ms
56WNbrUYLbL.css
218 ms
1kPfZUdGrka.js
298 ms
Yuj_Y8xNH2C.js
375 ms
Mpe38fuBVZ2.js
329 ms
n8qIhCw3vMx.js
321 ms
GN27K_co9Wc.css
299 ms
d20DxWMAn1e.js
305 ms
qcMicXoOToy.js
432 ms
57RpJa05x58.js
398 ms
7B-2ZS3Qt8r.js
397 ms
pf3FNnit_ev.js
397 ms
BmFj6FmaQGO.js
319 ms
hGrOQrzI1QD.js
397 ms
qf1RiuO5N-I.js
397 ms
10556350_1495292870710770_8847500312060576137_n.jpg
183 ms
10354686_10150004552801856_220367501106153455_n.jpg
216 ms
11140401_912298878834474_5197158793575604455_n.jpg
220 ms
1896825_1379346442336762_1456316691_n.jpg
223 ms
11846721_512366562243789_6779254781523005640_n.jpg
228 ms
598862_246698195441485_1594086832_n.jpg
225 ms
12802780_1734757703409434_8090470489453771307_n.jpg
227 ms
wL6VQj7Ab77.png
45 ms
s7jcwEQH7Sx.png
45 ms
11751464_870705183022466_807342241142379892_n.jpg
282 ms
10341752_646086365513839_8558939886499981262_n.jpg
282 ms
10986647_1380490818933515_7639834507635710764_n.jpg
284 ms
12347664_1710697609162601_731098534548758400_n.jpg
283 ms
10574307_10201891449042043_7987867255926415750_n.jpg
282 ms
12790878_445333308998652_4244471019123155528_n.jpg
283 ms
gxbPuQdXIZP.png
44 ms
VXcANLwwL5J.js
152 ms
AmlxWlqMvlv.js
151 ms
kokoo.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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
kokoo.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
Page has valid source maps
kokoo.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Kokoo.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 Kokoo.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.
kokoo.jp
Open Graph data is detected on the main page of Kokoo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: