6.9 sec in total
490 ms
4 sec
2.4 sec
Visit geass.info now to see the best up-to-date Geass content for Japan and also check out these interesting facts you probably never knew about geass.info
コードギアスのサーチです。サイト検索、交流、情報などコードギアス総合ポータルサイトです。
Visit geass.infoWe analyzed Geass.info page load time and found that the first response time was 490 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
geass.info performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value5.4 s
21/100
25%
Value7.1 s
31/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value4.2 s
85/100
10%
490 ms
681 ms
333 ms
515 ms
641 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 31% of them (42 requests) were addressed to the original Geass.info, 11% (15 requests) were made to Ecx.images-amazon.com and 5% (7 requests) were made to Gundam-seed.jp. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Gameha.com.
Page size can be reduced by 89.0 kB (23%)
388.0 kB
299.0 kB
In fact, the total size of Geass.info main page is 388.0 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. 45% of websites need less resources to load. Images take 313.3 kB which makes up the majority of the site volume.
Potential reduce by 58.3 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 21.1 kB, which is 32% 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 58.3 kB or 89% of the original size.
Potential reduce by 24.0 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 3.2 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 3.2 kB or 70% of the original size.
Potential reduce by 3.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.info needs all CSS files to be minified and compressed as it can save up to 3.5 kB or 73% of the original size.
Number of requests can be reduced by 36 (28%)
130
94
The browser has sent 130 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 4 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
geass.info
490 ms
www.geass.info
681 ms
design.css
333 ms
0.htm
515 ms
geass.cgi
641 ms
rss.gif
491 ms
sp.gif
321 ms
title.jpg
826 ms
category_event.gif
368 ms
arrow_blue.gif
371 ms
new_win.gif
508 ms
category_bbs.gif
658 ms
arrow_red.gif
673 ms
category_chat.gif
673 ms
arrow_green.gif
723 ms
category_game.gif
844 ms
arrow_orange.gif
998 ms
category_amusement.gif
1015 ms
arrow_purple.gif
1016 ms
ZERO_REQUIEM.gif
1616 ms
center_message.gif
1368 ms
center_information.gif
1390 ms
arrow_pink.gif
1324 ms
center_menu.gif
1348 ms
arrow_green2.gif
1368 ms
newimg.cgi
822 ms
100_getCanv.srv
415 ms
center_bbschat.gif
1479 ms
banner.gif
566 ms
617L10es43L._AA115_.jpg
33 ms
ws_banner88_06.jpg
528 ms
banner88_10.gif
424 ms
banner88_04.gif
499 ms
banner88_01.gif
449 ms
88_1.gif
459 ms
banner88_01.jpg
507 ms
88.gif
507 ms
00.gif
505 ms
88.gif
501 ms
88.gif
491 ms
banner88.gif
518 ms
sp_l3.gif
1008 ms
gameha.gif
2482 ms
gss1.gif
480 ms
count.fcg
500 ms
newimg.cgi
668 ms
51awUBquJYL._AA115_.jpg
27 ms
61VvoltcHeL._AA115_.jpg
27 ms
banner88_08.gif
358 ms
88.gif
509 ms
design.css
1343 ms
w_shadow_r.gif
1338 ms
head_line.gif
1375 ms
sp2.gif
1367 ms
center_search.gif
1649 ms
center_webcm.gif
1656 ms
center_event.gif
1647 ms
category_geass.gif
1677 ms
20120727.jpg
2202 ms
sp3.gif
1747 ms
88.gif
1965 ms
Leloch_NAVI.jpg
1977 ms
copyright.gif
2344 ms
seed.css
309 ms
sp.gif
315 ms
0icon_info.gif
332 ms
0icon_information.gif
358 ms
pr_board.cgi
709 ms
widgets.js
7 ms
geass-22
426 ms
footer_line.gif
1774 ms
w_shadow_l.gif
1874 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
31 ms
syndication
86 ms
517692951435034624
150 ms
88_1.gif
422 ms
seed.css
319 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
5 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
8 ms
vYRuQYe1_normal.png
87 ms
niftyCorners-1._V45728744_.css
8 ms
nifty-1._V45728692_.js
9 ms
btn_cart2._V158153839_.png
66 ms
51m4nwbyxWL._SL125_.jpg
64 ms
go-orange-trans._V192555739_.gif
59 ms
powered-by-amazon-b._V158154128_.png
58 ms
51-pX-P8ScL._SL125_.jpg
62 ms
51cP8VR%2Bt9L._SL125_.jpg
60 ms
413EqTxYWCL._SL125_.jpg
60 ms
51luxeoHNIL._SL125_.jpg
59 ms
41WMT2GbN4L._SL125_.jpg
65 ms
51iyGd2rIeL._SL125_.jpg
61 ms
41wOcxxTvbL._SL125_.jpg
61 ms
31uNtGzCeXL._SL125_.jpg
61 ms
61JAH0yaRHL._SL75_.jpg
62 ms
41OrH9%2BZd5L._SL75_.jpg
61 ms
61usg1xIpQL._SL75_.jpg
62 ms
200.gif
1727 ms
niftyPrint-1._V45727998_.css
23 ms
pr_board.css
321 ms
00.jpg
743 ms
banner.png
499 ms
banner.jpg
178 ms
tokoshie2.gif
669 ms
banner.gif
627 ms
banner01.gif
539 ms
banner.gif
275 ms
banner_gif.jpg
27 ms
banner.gif
552 ms
banner.jpg
518 ms
banner01.gif
692 ms
banner.jpg
496 ms
12.jpg
776 ms
banner.jpg
262 ms
bannar1.gif
695 ms
banner.gif
1269 ms
img20091128103150.jpg
1522 ms
img20151008235354.gif
1749 ms
no_banner.gif
490 ms
enter.gif
492 ms
jot
21 ms
banner.jpg
344 ms
banner.jpg
340 ms
banner.jpg
332 ms
banner.jpg
342 ms
bn1.gif
495 ms
banner.gif
338 ms
banner.gif
510 ms
banner.gif
332 ms
hina-bnr.jpg
540 ms
banner.gif
566 ms
img20091011164450.jpg
1681 ms
www.surpara.com
405 ms
pr_board.css
171 ms
geass.info 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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
geass.info best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
geass.info SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geass.info 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.info main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
geass.info
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: