6.6 sec in total
992 ms
5.3 sec
338 ms
Welcome to coco.to homepage info - get ready to check Coco best content for Japan right away, or after learning these important things about coco.to
映画レビューまとめサイト。ツイッターのつぶやきを自動解析し、映画レビューをしてしまうサービス。世間の生の声が反映される信憑性抜群の映画レビューが読めます。
Visit coco.toWe analyzed Coco.to page load time and found that the first response time was 992 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
coco.to performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value8.2 s
2/100
25%
Value10.1 s
9/100
10%
Value1,010 ms
27/100
30%
Value0.001
100/100
15%
Value11.9 s
16/100
10%
992 ms
361 ms
551 ms
401 ms
6 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 27% of them (26 requests) were addressed to the original Coco.to, 46% (44 requests) were made to Usagi.be and 6% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Usagi.be.
Page size can be reduced by 241.5 kB (17%)
1.4 MB
1.2 MB
In fact, the total size of Coco.to main page is 1.4 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. 40% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 56.8 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 56.8 kB or 81% of the original size.
Potential reduce by 115.6 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. Coco images are well optimized though.
Potential reduce by 59.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 59.4 kB or 35% of the original size.
Potential reduce by 9.7 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. Coco.to needs all CSS files to be minified and compressed as it can save up to 9.7 kB or 75% of the original size.
Number of requests can be reduced by 16 (17%)
93
77
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Coco. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
coco.to
992 ms
base.css
361 ms
jquery.js
551 ms
jquery.lazyload.min.js
401 ms
adsbygoogle.js
6 ms
images.gif
614 ms
StoriesFactory_normal.gif
358 ms
f30d07b83577ee005b818a23a7342140_normal.jpeg
385 ms
UkqD1T85_normal.jpg
489 ms
parts.png
760 ms
21d7f4280971decdb404935c4a7824c0.jpg
637 ms
73883c76819c77a6cee67bac116c1e20.jpg
672 ms
a469fcb1ef57981126a8a1eb02b5d423.jpg
514 ms
085f0492fd938187562365c968798361.jpg
534 ms
64f0a2b14a7ee761e53e2e81712fc8fe.jpg
1043 ms
4ceaec16729a72b5094de0614d242d12.jpg
1088 ms
aaeaed19e2e2dcf02e9f0287ad58473c.jpg
1164 ms
7ad5ddee456dcf09b13ad595344f6d2e.jpg
1180 ms
a410251b80a103b6e9b1f5a2fe79b1c9.jpg
1034 ms
1279b9e76962d98dedde3c7f90fc0a3b.jpg
1355 ms
c7c0f19ea5dfe9aee45a3473d925cdcc.jpg
1429 ms
af5c3716e059ef8fbdf1e374980d61ec.jpg
1621 ms
971dd474e1b26dd3a1d61e09824961cb.jpg
1682 ms
f44b906e1a870a3c780f23548f478208.jpg
1760 ms
442f56f29bbf03519f6bc1176e602f1e.jpg
1706 ms
7f4e296f75519530d7dcd28bff647721.jpg
1882 ms
9f75f981dcb5b15bd730231c226b79fe.jpg
1793 ms
d88602c607af5a0f5537e7b92a9a7625.jpg
2204 ms
1c9b24b39fd722d8163c043c6854d46a.jpg
2233 ms
3a5e770fe7b66b82cd16b8b465ef91a3.jpg
2259 ms
866fbcfd36889e36c54608be01d8ce1c.jpg
2275 ms
4bc28be9aeb6ae28155e02772204f4a6.jpg
2332 ms
loading_thumbnail.gif
2223 ms
75390ddd7498e3b31dc85fd25713619d.jpg
2573 ms
93164c5d1216f1d010db55b9c88117ca.jpg
2796 ms
4906d594ee774985a445e274f855c6e7.jpg
2824 ms
94515ee38c33eaefbeafd17c82939a8d.jpg
2869 ms
02c638790f3f6b08228735c0ac5ab95d.jpg
2678 ms
c6e56f0c5e0456c1693b2c3a2fef1317.jpg
2734 ms
49a12a6f74d65292213e87b270669a34.jpg
2964 ms
08f20caec58db2a3b8ea3b92465935f1.jpg
3020 ms
4ceaec16729a72b5094de0614d242d12.jpg
3133 ms
a469fcb1ef57981126a8a1eb02b5d423.jpg
3183 ms
73883c76819c77a6cee67bac116c1e20.jpg
3247 ms
banner_40260_ss.jpg
343 ms
banner_39522_ss.jpg
346 ms
banner_40330_ss.jpg
360 ms
paranoiafreaks
369 ms
yukigame
367 ms
xxtonchiki
383 ms
d_hinata
707 ms
sa9237a
717 ms
admiralgoto
772 ms
tamiki
773 ms
nagamasa_san
777 ms
yako802
774 ms
banner_40260_se.jpg
1229 ms
banner_40434_se.jpg
1417 ms
banner_39304_se.jpg
1277 ms
banner_38551_se.jpg
1319 ms
banner_coco2015_result_se.jpg
1335 ms
banner_40260_sp.jpg
1530 ms
banner_39522_sp.jpg
1941 ms
banner_40330_sp.jpg
1965 ms
ajs.php
368 ms
coco.woff
1645 ms
lg.php
184 ms
ca-pub-6234989545654371.js
155 ms
zrt_lookup.html
37 ms
show_ads_impl.js
56 ms
ga.js
107 ms
7ad5ddee456dcf09b13ad595344f6d2e.jpg
2790 ms
971dd474e1b26dd3a1d61e09824961cb.jpg
2812 ms
ads
274 ms
osd.js
44 ms
scroll_top.png
1137 ms
ed7b182d035aa12d6bf2fc2b50a01bb0.jpg
2756 ms
__utm.gif
25 ms
ads
256 ms
10c8d727141306d28f69a455a878bc08.jpg
2873 ms
collect
55 ms
2d57a615df70c44c713d0d6dfc20b5f2.jpg
2948 ms
06167c8e90644c71f555af8cf19aa205.jpg
2877 ms
2298538139600426920
62 ms
abg.js
66 ms
m_js_controller.js
84 ms
googlelogo_color_112x36dp.png
108 ms
5171746271700867932
64 ms
s
32 ms
redir.html
45 ms
x_button_blue2.png
28 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
2 ms
iframe.html
16 ms
2c4ee403dcc8e04f8d9c3480a5fb150e.jpg
2646 ms
switch_site.gif
2661 ms
activeview
14 ms
coco.to 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.
coco.to best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the notification permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
coco.to SEO score
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Coco.to 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 Coco.to 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.
coco.to
Open Graph data is detected on the main page of Coco. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: