Tools & Wizards About Us
crunchyroll.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

crunchyroll.com

Crunchyroll logo

Page Load Speed

779 ms in total

First Response

20 ms

Resources Loaded

435 ms

Page Rendered

324 ms

crunchyroll.com screenshot

About Website

Visit crunchyroll.com now to see the best up-to-date Crunchyroll content for United States and also check out these interesting facts you probably never knew about crunchyroll.com

Visit crunchyroll.com

Key Findings

We analyzed Crunchyroll.com page load time and found that the first response time was 20 ms and then it took 759 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

crunchyroll.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

crunchyroll.com

20 ms

www.crunchyroll.com

275 ms

cr-eec-5.1.0.js

23 ms

otSDKStub.js

33 ms

manifest.720aafc6b3f2ed4a94be.js

44 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 89% of them (42 requests) were addressed to the original Crunchyroll.com, 6% (3 requests) were made to Cdn.cookielaw.org and 2% (1 request) were made to Static.crunchyroll.com. The less responsive or slowest element that took the longest time to load (275 ms) belongs to the original domain Crunchyroll.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 16.0 kB (4%)

Content Size

391.6 kB

After Optimization

375.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Crunchyroll.com main page is 391.6 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 366.1 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 12.9 kB

  • Original 18.3 kB
  • After minification 18.3 kB
  • After compression 5.4 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 12.9 kB or 71% of the original size.

Image Optimization

-11%

Potential reduce by 816 B

  • Original 7.2 kB
  • After minification 6.4 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. Obviously, Crunchyroll needs image optimization as it can save up to 816 B or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 2.3 kB

  • Original 366.1 kB
  • After minification 366.1 kB
  • After compression 363.8 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 38 (84%)

Requests Now

45

After Optimization

7

  • AJAX
  • Images
  • JavaScript

The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Crunchyroll. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

crunchyroll.com

crunchyroll.com

20 ms

www.crunchyroll.com

www.crunchyroll.com

275 ms

cr-eec-5.1.0.js

cr-eec-5.1.0.js

23 ms

otSDKStub.js

otSDKStub.js

33 ms

manifest.720aafc6b3f2ed4a94be.js

manifest.720aafc6b3f2ed4a94be.js

44 ms

main.common-046cd43c.3166388694df332deb34.js

main.common-046cd43c.3166388694df332deb34.js

42 ms

main.common-0e3dda97.2530e7b3b1964dfc2547.js

main.common-0e3dda97.2530e7b3b1964dfc2547.js

43 ms

main.common-9f4db315.dd6dc2170fa74f5560e9.js

main.common-9f4db315.dd6dc2170fa74f5560e9.js

55 ms

main.common-a990ab61.20522cf9f89929060574.js

main.common-a990ab61.20522cf9f89929060574.js

54 ms

main.common-a6ec8c30.ee041f8842a9623c0148.js

main.common-a6ec8c30.ee041f8842a9623c0148.js

58 ms

main.common-77e563e4.0f0b8cb49c124c6979ca.js

main.common-77e563e4.0f0b8cb49c124c6979ca.js

56 ms

main.common-78657218.a584a251f72a6fd98f2d.js

main.common-78657218.a584a251f72a6fd98f2d.js

64 ms

main.common-5b55d025.968ae707bcbf48cb19a5.js

main.common-5b55d025.968ae707bcbf48cb19a5.js

64 ms

main.common-9745f741.4bc69bd38fcca3988544.js

main.common-9745f741.4bc69bd38fcca3988544.js

65 ms

main.common-1dfc713c.cce13ae147192b240c42.js

main.common-1dfc713c.cce13ae147192b240c42.js

80 ms

main.common-bc0214de.02fea6b48ce3a30f8bc7.js

main.common-bc0214de.02fea6b48ce3a30f8bc7.js

72 ms

main.common-b297df17.547bc9597ed69e31565f.js

main.common-b297df17.547bc9597ed69e31565f.js

77 ms

main.common-140d877e.9dd894dd253be3e0e287.js

main.common-140d877e.9dd894dd253be3e0e287.js

91 ms

main.common-8cae31a0.9de1416a56943005ef31.js

main.common-8cae31a0.9de1416a56943005ef31.js

78 ms

main.common-1d097e9f.24a71ac1cf4f2a453bb5.js

main.common-1d097e9f.24a71ac1cf4f2a453bb5.js

80 ms

main.common-182f79bf.5790bb5b2c2c2e0eecbd.js

main.common-182f79bf.5790bb5b2c2c2e0eecbd.js

94 ms

main.npm-640e94a9.ea6847cad3011b79feee.js

main.npm-640e94a9.ea6847cad3011b79feee.js

94 ms

main.npm-8edd4ba6.6cc3660aa40b3d76aa0d.js

main.npm-8edd4ba6.6cc3660aa40b3d76aa0d.js

98 ms

main.npm-49d0a293.061ec9ca6dd291492d76.js

main.npm-49d0a293.061ec9ca6dd291492d76.js

100 ms

main.npm-162c8979.8643cb78734bf25f266e.js

main.npm-162c8979.8643cb78734bf25f266e.js

98 ms

main.npm-c39f61f2.55303460a818569ef14d.js

main.npm-c39f61f2.55303460a818569ef14d.js

111 ms

main.npm-617767ba.195765de7f3ef4d30f97.js

main.npm-617767ba.195765de7f3ef4d30f97.js

116 ms

main.npm-62c54514.4c1e178fd5cb53bacf73.js

main.npm-62c54514.4c1e178fd5cb53bacf73.js

111 ms

main.npm-e0e099ba.8a53e999ebb297a60944.js

main.npm-e0e099ba.8a53e999ebb297a60944.js

124 ms

main.npm-95c3aee9.4b427f0c7e4c28e112bf.js

main.npm-95c3aee9.4b427f0c7e4c28e112bf.js

112 ms

main.npm-ab957e66.14534f10eb3d8f971cf7.js

main.npm-ab957e66.14534f10eb3d8f971cf7.js

124 ms

main.npm-536eaa00.4cc2fa2c02d51410ea15.js

main.npm-536eaa00.4cc2fa2c02d51410ea15.js

144 ms

main.npm-0bc0478e.63ae75a62409fc07d5f7.js

main.npm-0bc0478e.63ae75a62409fc07d5f7.js

145 ms

main.npm-27545368.62aa66b4dd84d2ba00cb.js

main.npm-27545368.62aa66b4dd84d2ba00cb.js

144 ms

main.npm-229eafb5.112ce02e7f05574febcc.js

main.npm-229eafb5.112ce02e7f05574febcc.js

145 ms

main.npm-c8a9238a.a48c12c06b2de59469e8.js

main.npm-c8a9238a.a48c12c06b2de59469e8.js

146 ms

main.77dfc0451ce75be7f8ee.js

main.77dfc0451ce75be7f8ee.js

147 ms

unsupported.34c446195fdf4d07fe99.js

unsupported.34c446195fdf4d07fe99.js

151 ms

9470b86f-5b87-4646-a4f7-2f2916b2a883.json

9470b86f-5b87-4646-a4f7-2f2916b2a883.json

26 ms

close-x.png

close-x.png

124 ms

chrome.png

chrome.png

106 ms

firefox.png

firefox.png

110 ms

safari.png

safari.png

117 ms

edge.png

edge.png

122 ms

location

location

45 ms

otBannerSdk.js

otBannerSdk.js

21 ms

main.js

main.js

21 ms

Accessibility Review

crunchyroll.com accessibility score

62

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

crunchyroll.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

crunchyroll.com SEO score

91

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Crunchyroll.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Crunchyroll.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.

Social Sharing Optimization

crunchyroll.com

Open Graph description is not detected on the main page of Crunchyroll. 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: