Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

36ch.com

アニメ36ch

Page Load Speed

3.8 sec in total

First Response

1.2 sec

Resources Loaded

2.5 sec

Page Rendered

101 ms

36ch.com screenshot

About Website

Welcome to 36ch.com homepage info - get ready to check 36 Ch best content for Japan right away, or after learning these important things about 36ch.com

エヴァンゲリオンのセリフ・あらすじなどを掲載中。アニメ版第一話から最終話までのストーリーや新劇場版の全セリフ書き起こしを読むことができます。

Visit 36ch.com

Key Findings

We analyzed 36ch.com page load time and found that the first response time was 1.2 sec and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

36ch.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.8 s

68/100

10%

Network Requests Diagram

36ch.com

1196 ms

style.css

697 ms

jquery.js

856 ms

jquery.exflexfixed.js

882 ms

wp-embed.min.js

192 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 55% of them (6 requests) were addressed to the original 36ch.com, 18% (2 requests) were made to Apis.google.com and 18% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain 36ch.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 79.8 kB (69%)

Content Size

115.3 kB

After Optimization

35.4 kB

In fact, the total size of 36ch.com main page is 115.3 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. Only 5% of websites need less resources to load. Javascripts take 88.1 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 4.6 kB

  • Original 7.2 kB
  • After minification 6.8 kB
  • After compression 2.6 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 4.6 kB or 64% of the original size.

JavaScript Optimization

-67%

Potential reduce by 59.1 kB

  • Original 88.1 kB
  • After minification 88.1 kB
  • After compression 29.0 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.1 kB or 67% of the original size.

CSS Optimization

-81%

Potential reduce by 16.1 kB

  • Original 19.9 kB
  • After minification 14.7 kB
  • After compression 3.8 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. 36ch.com needs all CSS files to be minified and compressed as it can save up to 16.1 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (57%)

Requests Now

7

After Optimization

3

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

Accessibility Review

36ch.com accessibility score

65

Accessibility Issues

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

Form elements do not have associated labels

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

36ch.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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

36ch.com SEO score

98

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

High

Tap targets are not sized appropriately

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 36ch.com 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 36ch.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

Open Graph data is detected on the main page of 36 Ch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: