Tools & Wizards About Us
geass.jp screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

geass.jp

コードギアスシリーズ公式サイト

Page Load Speed

10.6 sec in total

First Response

518 ms

Resources Loaded

9.2 sec

Page Rendered

901 ms

geass.jp screenshot

About Website

Welcome to geass.jp homepage info - get ready to check Geass best content for Japan right away, or after learning these important things about geass.jp

「コードギアス」シリーズ公式サイト。コードギアスシリーズの最新情報を随時公開。

Visit geass.jp

Key Findings

We analyzed Geass.jp page load time and found that the first response time was 518 ms and then it took 10.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

geass.jp performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value16.9 s

0/100

25%

SI (Speed Index)

Value22.0 s

0/100

10%

TBT (Total Blocking Time)

Value6,250 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.163

72/100

15%

TTI (Time to Interactive)

Value33.2 s

0/100

10%

Network Requests Diagram

geass.jp

518 ms

geass.jp

1406 ms

style.css

511 ms

style.css

865 ms

jquery-3.6.0.min.js

871 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 60% of them (67 requests) were addressed to the original Geass.jp, 10% (11 requests) were made to Platform.twitter.com and 5% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain Geass.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 302.4 kB (11%)

Content Size

2.7 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Geass.jp main page is 2.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 26.2 kB

  • Original 34.7 kB
  • After minification 30.6 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 4.1 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 26.2 kB or 76% of the original size.

Image Optimization

-5%

Potential reduce by 102.1 kB

  • Original 2.2 MB
  • After minification 2.1 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. Geass images are well optimized though.

JavaScript Optimization

-38%

Potential reduce by 165.0 kB

  • Original 436.9 kB
  • After minification 436.7 kB
  • After compression 271.9 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 165.0 kB or 38% of the original size.

CSS Optimization

-13%

Potential reduce by 9.1 kB

  • Original 70.6 kB
  • After minification 67.1 kB
  • After compression 61.5 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. Geass.jp needs all CSS files to be minified and compressed as it can save up to 9.1 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (30%)

Requests Now

103

After Optimization

72

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

geass.jp

geass.jp

518 ms

geass.jp

geass.jp

1406 ms

style.css

style.css

511 ms

style.css

style.css

865 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

871 ms

news_list.js

news_list.js

510 ms

js

js

40 ms

jquery.cookie.min.js

jquery.cookie.min.js

356 ms

fancybox.umd.js

fancybox.umd.js

1015 ms

js

js

84 ms

widgets.js

widgets.js

93 ms

geass.js

geass.js

337 ms

news_list.js

news_list.js

673 ms

webryblog.biglobe.ne.jp

webryblog.biglobe.ne.jp

677 ms

td.min.js

td.min.js

124 ms

segment

segment

418 ms

analytics.js

analytics.js

173 ms

bg02.jpg

bg02.jpg

1226 ms

title_portal_01.png

title_portal_01.png

235 ms

title_portal_02.png

title_portal_02.png

275 ms

title_portal_01_sp.png

title_portal_01_sp.png

234 ms

title_portal_02_sp.png

title_portal_02_sp.png

275 ms

ban_top14.png

ban_top14.png

837 ms

ban_top14_sp.png

ban_top14_sp.png

838 ms

light01.png

light01.png

839 ms

line_bg_01.png

line_bg_01.png

415 ms

title_news.svg

title_news.svg

835 ms

X%E6%8A%95%E7%A8%BF%E7%94%BB%E5%83%8F_%E7%AC%AC1%E5%B9%95%E4%B8%8A%E6%98%A0%E8%A8%98%E5%BF%B5%E8%88%9E%E5%8F%B0%E6%8C%A8%E6%8B%B6.jpg

X%E6%8A%95%E7%A8%BF%E7%94%BB%E5%83%8F_%E7%AC%AC1%E5%B9%95%E4%B8%8A%E6%98%A0%E8%A8%98%E5%BF%B5%E8%88%9E%E5%8F%B0%E6%8C%A8%E6%8B%B6.jpg

5337 ms

20240424cg01_pop_img.jpg

20240424cg01_pop_img.jpg

5752 ms

key_Lelouch-%E3%82%B3%E3%83%94%E3%83%BC-scaled.jpg

key_Lelouch-%E3%82%B3%E3%83%94%E3%83%BC-scaled.jpg

1141 ms

codegeass_182x257.jpg

codegeass_182x257.jpg

2809 ms

Codegeass-_youtube_logo_basic.png

Codegeass-_youtube_logo_basic.png

1327 ms

Roze_ED_JK_H1-2.jpg

Roze_ED_JK_H1-2.jpg

1297 ms

MYV_Running-in-My-Head_H1_240327_1-3.jpg

MYV_Running-in-My-Head_H1_240327_1-3.jpg

1396 ms

Roze-1_KV-wLogo.jpg

Roze-1_KV-wLogo.jpg

1470 ms

%E7%94%BB%E5%83%8F1.jpg

%E7%94%BB%E5%83%8F1.jpg

1504 ms

youtube02.png

youtube02.png

1573 ms

youtube01.svg

youtube01.svg

1642 ms

top_btn_first_on.jpg

top_btn_first_on.jpg

1681 ms

top_btn_first_off.jpg

top_btn_first_off.jpg

1749 ms

top_btn_r2_on.jpg

top_btn_r2_on.jpg

1813 ms

top_btn_r2_off.jpg

top_btn_r2_off.jpg

1859 ms

top_btn_akito_on.jpg

top_btn_akito_on.jpg

1925 ms

top_btn_akito_off.jpg

top_btn_akito_off.jpg

1983 ms

top_btn_sanbu_on.jpg

top_btn_sanbu_on.jpg

2034 ms

top_btn_sanbu_off.jpg

top_btn_sanbu_off.jpg

2102 ms

top_btn_rgeass_on.jpg

top_btn_rgeass_on.jpg

2153 ms

top_btn_rgeass_off.jpg

top_btn_rgeass_off.jpg

2211 ms

top_btn_roze_on.jpg

top_btn_roze_on.jpg

2278 ms

top_btn_roze_off.jpg

top_btn_roze_off.jpg

2324 ms

top_btn_hobby_on.jpg

top_btn_hobby_on.jpg

2387 ms

top_btn_hobby_off.jpg

top_btn_hobby_off.jpg

2454 ms

top_btn_gaiden_on.jpg

top_btn_gaiden_on.jpg

2494 ms

349 ms

ga.js

ga.js

128 ms

uwt.js

uwt.js

90 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

106 ms

collect

collect

18 ms

adsct

adsct

173 ms

adsct

adsct

110 ms

top_btn_gaiden_off.jpg

top_btn_gaiden_off.jpg

2337 ms

top_btn_geassgr_on.jpg

top_btn_geassgr_on.jpg

2404 ms

settings

settings

107 ms

__utm.gif

__utm.gif

12 ms

top_btn_geassgr_off.jpg

top_btn_geassgr_off.jpg

2397 ms

card_renya_on.jpg

card_renya_on.jpg

2472 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

23 ms

GEASSPROJECT

GEASSPROJECT

818 ms

geass_www_access

geass_www_access

786 ms

card_renya_off.jpg

card_renya_off.jpg

2399 ms

www-player.css

www-player.css

19 ms

www-embed-player.js

www-embed-player.js

42 ms

base.js

base.js

70 ms

ad_status.js

ad_status.js

191 ms

71suEs83z0XiqH0n_P_GdL05qLj4eQk8ZwtXjY02tX0.js

71suEs83z0XiqH0n_P_GdL05qLj4eQk8ZwtXjY02tX0.js

132 ms

embed.js

embed.js

55 ms

card_nunnally_on.jpg

card_nunnally_on.jpg

2006 ms

card_nunnally_off.jpg

card_nunnally_off.jpg

2088 ms

card_la_on.jpg

card_la_on.jpg

2144 ms

Unm7wJKoMnEZ7KVnDCV-5YvtIpCOq02yGMfTxSq2GV20ndw2-d__0UJUNMlTudWb_yomMa9NMg=s68-c-k-c0x00ffffff-no-rj

Unm7wJKoMnEZ7KVnDCV-5YvtIpCOq02yGMfTxSq2GV20ndw2-d__0UJUNMlTudWb_yomMa9NMg=s68-c-k-c0x00ffffff-no-rj

179 ms

card_la_off.jpg

card_la_off.jpg

2127 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

36 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

41 ms

id

id

22 ms

Create

Create

139 ms

card_hobby_on.jpg

card_hobby_on.jpg

1871 ms

GenerateIT

GenerateIT

16 ms

pixel

pixel

32 ms

polyfills-3b821eda8863adcc4a4b.js

polyfills-3b821eda8863adcc4a4b.js

24 ms

runtime-a697c5a1ae32bd7e4d42.js

runtime-a697c5a1ae32bd7e4d42.js

49 ms

modules.20f98d7498a59035a762.js

modules.20f98d7498a59035a762.js

92 ms

main-fd9ef5eb169057cda26d.js

main-fd9ef5eb169057cda26d.js

84 ms

_app-88bf420a57d49e33be53.js

_app-88bf420a57d49e33be53.js

89 ms

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

90 ms

_buildManifest.js

_buildManifest.js

92 ms

_ssgManifest.js

_ssgManifest.js

90 ms

card_hobby_off.jpg

card_hobby_off.jpg

1880 ms

pixel

pixel

13 ms

sync

sync

13 ms

top_btn_wave_on.jpg

top_btn_wave_on.jpg

1857 ms

top_btn_wave_off.jpg

top_btn_wave_off.jpg

1839 ms

card_pachinko_re_on.jpg

card_pachinko_re_on.jpg

1788 ms

card_pachinko_re_off.jpg

card_pachinko_re_off.jpg

1806 ms

card_p7_on.jpg

card_p7_on.jpg

1819 ms

card_p7_off.jpg

card_p7_off.jpg

1769 ms

card_appli_on.jpg

card_appli_on.jpg

1711 ms

card_appli_off.jpg

card_appli_off.jpg

1771 ms

top_btn_realize_on.jpg

top_btn_realize_on.jpg

1745 ms

top_btn_realize_off.jpg

top_btn_realize_off.jpg

1705 ms

top_btn_loststories_on.jpg

top_btn_loststories_on.jpg

1665 ms

top_btn_loststories_off.jpg

top_btn_loststories_off.jpg

1702 ms

log_event

log_event

15 ms

Accessibility Review

geass.jp accessibility score

95

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.

Best Practices

geass.jp best practices score

75

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

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

geass.jp 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 Geass.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 Geass.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.

Social Sharing Optimization

geass.jp

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