6.7 sec in total
774 ms
5.7 sec
200 ms
Click here to check amazing Genesis Horizon content for Japan. Otherwise, check out these important facts you probably never knew about genesis-horizon.net
TVアニメ「境界線上のホライゾンII」2012年7月放送開始!公式Twitter[@__horizon__]原作:川上稔(電撃文庫/アスキー・メディアワークス刊)、キャラクターデザイン原案:さとやす(TENKY)、監督:小野学、シリーズ構成:浦畑達彦、アニメーション制作:サンライズ CAST:福山潤、茅原実里 他
Visit genesis-horizon.netWe analyzed Genesis-horizon.net page load time and found that the first response time was 774 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
genesis-horizon.net performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value8.6 s
1/100
25%
Value9.2 s
13/100
10%
Value460 ms
61/100
30%
Value0.001
100/100
15%
Value16.8 s
5/100
10%
774 ms
180 ms
359 ms
360 ms
367 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 67% of them (72 requests) were addressed to the original Genesis-horizon.net, 23% (25 requests) were made to Pbs.twimg.com and 6% (7 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Genesis-horizon.net.
Page size can be reduced by 403.1 kB (13%)
3.2 MB
2.8 MB
In fact, the total size of Genesis-horizon.net main page is 3.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. 75% 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.9 MB which makes up the majority of the site volume.
Potential reduce by 10.8 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 3.4 kB, which is 24% 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 10.8 kB or 77% of the original size.
Potential reduce by 179.6 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. Genesis Horizon images are well optimized though.
Potential reduce by 163.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 163.8 kB or 68% of the original size.
Potential reduce by 48.9 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. Genesis-horizon.net needs all CSS files to be minified and compressed as it can save up to 48.9 kB or 84% of the original size.
Number of requests can be reduced by 36 (34%)
107
71
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Genesis Horizon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
genesis-horizon.net
774 ms
import.css
180 ms
thickbox.css
359 ms
top2015.css
360 ms
common.js
367 ms
jquery.js
950 ms
jquery.easing.js
383 ms
jquery.slideshow.js
613 ms
jquery.thickbox.js
538 ms
widget.js
56 ms
top.js
538 ms
common.css
371 ms
font_style.css
395 ms
base.css
893 ms
smp.css
538 ms
bg_body_ver2.jpg
1428 ms
hotnews.php
415 ms
header_bg2.png
184 ms
header_logo2.png
587 ms
bg_news.png
207 ms
blank.gif
185 ms
nav_schedule2.png
526 ms
btn_story1.png
526 ms
btn_story2.png
527 ms
btn_character.png
528 ms
btn_cast.png
699 ms
bg_movie.png
928 ms
btn_bc.jpg
703 ms
btn_nico.jpg
720 ms
btn_yt.jpg
760 ms
icon_stage.png
878 ms
icon_stage_pc_on.png
885 ms
icon_stage_iphone_on.png
910 ms
icon_stage_andloid_on.png
952 ms
bg_movie_thumb.png
1057 ms
btn_movie_prev.png
1067 ms
bg_thumb_box.png
1100 ms
btn_movie_next.png
1132 ms
bg_twitter.png
1142 ms
btn_twitter_official.jpg
1237 ms
btn_twitter_hash.jpg
1250 ms
widgets.js
8 ms
btn_tweet.png
1286 ms
bg_banner.png
1536 ms
banner_delivery_2nd.png
1327 ms
banner_bd_all.png
1411 ms
banner_book3.png
1609 ms
banner_cd.png
1476 ms
banner_game.png
1519 ms
banner_goods.png
1590 ms
banner_bd2_vol07_bookread.png
1593 ms
banner_bd2_vol07_bookletread.png
1668 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
28 ms
syndication
84 ms
308594128424407040
174 ms
308596731526914048
445 ms
banner_special_bnn.png
1535 ms
banner_event.png
1548 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
2 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
5 ms
29PW29Ca_normal.jpg
258 ms
icon_horizon_normal.jpg
261 ms
so01_normal.gif
262 ms
T7_A5cdT_normal.jpeg
261 ms
CNVvCUcUEAAnQ4X.jpg:small
264 ms
CNVSdn2VEAEDdIu.jpg:small
263 ms
CMMrgyiUcAAUF4i.png:small
278 ms
CMMqwUDUkAAWRmc.png:small
276 ms
CMMpeYUUAAAxGp4.png:small
272 ms
CMMoQCtUYAAB_dK.png:small
271 ms
CMMnXhBUkAED3wF.png:small
276 ms
CMMmqrwVAAELuBE.png:small
283 ms
CNUjVypUkAEmTth.png:small
285 ms
CNUjVtFUAAAJwm8.png:small
286 ms
CNUjVddUkAAloLn.png:small
287 ms
CNUjVuyVAAAznBC.png:small
289 ms
CMRle3CUEAAVg2x.png:small
289 ms
CMRleySVAAALRwq.png:small
286 ms
CMRledlU8AAWAuf.png:small
281 ms
CMRlezmVEAAhD3q.png:small
282 ms
CMRmxzlUEAApPdW.png:small
276 ms
CMRmx0SUAAAUHEf.png:small
278 ms
hotnews.css
1366 ms
jquery.jscrollpane.css
1259 ms
jquery.js
1819 ms
jquery.mousewheel.js
1341 ms
jquery.jscrollpane.min.js
1382 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
13 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
15 ms
27e2bcc1f2b24f2aa8c522737c779762_normal.jpeg
24 ms
nanasaki_normal.gif
25 ms
6mk6zjvscmrxvbg0v1y2_normal.jpeg
25 ms
banner_bd_amenity.png
1327 ms
banner_movie.png
1259 ms
bg_banner2.png
1262 ms
banner_120707.png
1338 ms
banner_kkt_end.png
1340 ms
img_copyright.png
1259 ms
banner_kkt_end.png
2542 ms
jot.html
2 ms
loadingAnimation.gif
1234 ms
bar_slice02.png
181 ms
icon_arw03.png
192 ms
nav_schedule2_ov.png
363 ms
btn_story1_ov.png
192 ms
btn_story2_ov.png
186 ms
btn_character_ov.png
381 ms
btn_cast_ov.png
207 ms
genesis-horizon.net accessibility score
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
Links do not have a discernible name
genesis-horizon.net 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
Detected JavaScript libraries
Browser errors were logged to the console
genesis-horizon.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Genesis-horizon.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Genesis-horizon.net 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.
genesis-horizon.net
Open Graph description is not detected on the main page of Genesis Horizon. 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: