9 sec in total
1.1 sec
7.7 sec
196 ms
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.jpWe analyzed Geass.jp page load time and found that the first response time was 1.1 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
geass.jp performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value16.9 s
0/100
25%
Value9.2 s
13/100
10%
Value1,790 ms
10/100
30%
Value0.162
72/100
15%
Value10.8 s
22/100
10%
1136 ms
322 ms
1254 ms
526 ms
352 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 83% of them (40 requests) were addressed to the original Geass.jp, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain Geass.jp.
Page size can be reduced by 245.9 kB (11%)
2.2 MB
2.0 MB
In fact, the total size of Geass.jp main page is 2.2 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. 20% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 51.5 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 51.5 kB or 84% of the original size.
Potential reduce by 76.3 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. Geass images are well optimized though.
Potential reduce by 82.3 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 82.3 kB or 51% of the original size.
Potential reduce by 35.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. Geass.jp needs all CSS files to be minified and compressed as it can save up to 35.8 kB or 83% of the original size.
Number of requests can be reduced by 7 (16%)
45
38
The browser has sent 45 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 8 to 1 for JavaScripts and as a result speed up the page load time.
geass.jp
1136 ms
style.css
322 ms
jquery-1.7.1.min.js
1254 ms
news_list.js
526 ms
smart-crossfade.js
352 ms
jquery.crossFadeRollOver.js
766 ms
jquery.fancybox-1.3.1.pack.js
768 ms
fancybox1.3.1.css
652 ms
geass.js
166 ms
conversion.js
14 ms
bg.jpg
1760 ms
title_portal.png
641 ms
ban_stop01.gif
494 ms
ban_top05.gif
530 ms
bg_main.jpg
921 ms
card_akito_off.png
1348 ms
card_r1_off.png
1667 ms
card_r2_off.png
1938 ms
card_oz_off.png
1758 ms
card_nunnally_off.jpg
1595 ms
card_renya_off.jpg
1876 ms
card_pachinko_off.jpg
2075 ms
card_p7_off.jpg
2173 ms
card_la_off.jpg
2261 ms
codeblack_bnr_campaign01.jpg
2443 ms
campaign_modal.jpg
4367 ms
campaign_modal_btn01.png
2291 ms
campaign_modal_btn02.png
2717 ms
bg_info.jpg
2698 ms
mtitle_whatsnew.png
2614 ms
btn_twitter.png
2612 ms
mtitle_blog.png
2796 ms
copy.png
2934 ms
ga.js
39 ms
59 ms
51 ms
__utm.gif
28 ms
47 ms
64 ms
card_akito_on.png
1150 ms
card_r1_on.png
988 ms
card_r2_on.png
1148 ms
card_oz_on.png
1187 ms
card_nunnally_on.jpg
535 ms
card_renya_on.jpg
577 ms
card_pachinko_on.jpg
1062 ms
card_p7_on.jpg
1077 ms
card_la_on.jpg
1567 ms
geass.jp 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.
geass.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
geass.jp 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 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.
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: