Report Summary

  • 29

    Performance

    Renders faster than
    50% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 63% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

coco.to

coco - 映画レビューサイト

Page Load Speed

6.6 sec in total

First Response

992 ms

Resources Loaded

5.3 sec

Page Rendered

338 ms

coco.to screenshot

About Website

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.to

Key Findings

We 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 70% of websites can load faster.

Performance Metrics

coco.to performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value1,010 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value11.9 s

16/100

10%

Network Requests Diagram

coco.to

992 ms

base.css

361 ms

jquery.js

551 ms

jquery.lazyload.min.js

401 ms

adsbygoogle.js

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 Optimization Overview & Recommendations

Page size can be reduced by 265.5 kB (19%)

Content Size

1.4 MB

After Optimization

1.1 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.

HTML Optimization

-81%

Potential reduce by 56.8 kB

  • Original 70.4 kB
  • After minification 66.5 kB
  • After compression 13.7 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.

Image Optimization

-10%

Potential reduce by 115.6 kB

  • Original 1.2 MB
  • After minification 1.0 MB

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.

JavaScript Optimization

-58%

Potential reduce by 83.4 kB

  • Original 143.5 kB
  • After minification 140.6 kB
  • After compression 60.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 83.4 kB or 58% of the original size.

CSS Optimization

-75%

Potential reduce by 9.7 kB

  • Original 13.0 kB
  • After minification 11.6 kB
  • After compression 3.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. 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.

Requests Breakdown

Number of requests can be reduced by 16 (17%)

Requests Now

93

After Optimization

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.

Accessibility Review

coco.to accessibility score

86

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

coco.to best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

coco.to SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    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.

Social Sharing Optimization

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: