3.6 sec in total
410 ms
3.1 sec
114 ms
Visit gargantia.jp now to see the best up-to-date Gargantia content for Japan and also check out these interesting facts you probably never knew about gargantia.jp
新番組「翠星のガルガンティア」アニメ公式サイト。監督 村田和也、脚本 虚淵玄、キャラクター原案 鳴子ハナハル。2013年春よりテレビ放送開始!宇宙で育ち戦うことしか知らなかった少年兵レドの、海に覆われた地球に浮かぶ巨大船団「ガルガンティア」での驚きに満ちた日々を描いたSF冒険活劇。
Visit gargantia.jpWe analyzed Gargantia.jp page load time and found that the first response time was 410 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
gargantia.jp performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value9.9 s
0/100
25%
Value10.5 s
7/100
10%
Value450 ms
63/100
30%
Value0.022
100/100
15%
Value9.4 s
31/100
10%
410 ms
362 ms
369 ms
382 ms
378 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 78% of them (39 requests) were addressed to the original Gargantia.jp, 10% (5 requests) were made to Platform.twitter.com and 6% (3 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Gargantia.jp.
Page size can be reduced by 403.4 kB (61%)
661.6 kB
258.2 kB
In fact, the total size of Gargantia.jp main page is 661.6 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. Javascripts take 496.9 kB which makes up the majority of the site volume.
Potential reduce by 11.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 11.6 kB or 75% of the original size.
Potential reduce by 4.4 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. Gargantia images are well optimized though.
Potential reduce by 362.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 362.2 kB or 73% of the original size.
Potential reduce by 25.1 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. Gargantia.jp needs all CSS files to be minified and compressed as it can save up to 25.1 kB or 82% of the original size.
Number of requests can be reduced by 31 (63%)
49
18
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gargantia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
gargantia.jp
410 ms
common.css
362 ms
colorbox.css
369 ms
jquery.jqzoom.css
382 ms
jquery.smartModalWindow.css
378 ms
jquery-1.8.3.min.js
377 ms
jquery.xdomainajax.js
354 ms
jquery.colorbox-min.js
716 ms
jquery.jqzoom-core-pack.js
721 ms
jquery.color.js
725 ms
timeline.js
751 ms
jquery.easing.1.3.js
752 ms
jquery.rotate.js
733 ms
jquery.ba-hashchange.min.js
1079 ms
jquery.imagesloaded.min.js
1102 ms
jquery.backstretch.js
1078 ms
jquery.cookie.js
1107 ms
audio.min.js
1110 ms
jquery.smartModalWindow.js
1112 ms
function.js
1439 ms
variable.js
1450 ms
pageFunction.js
1472 ms
init.js
1506 ms
logo.png
407 ms
sq.png
354 ms
bannerlogoblog.png
406 ms
bannerwebgame.png
405 ms
topbannerdmm3.png
403 ms
spacer.gif
405 ms
ga.js
35 ms
dotted_mask2.png
702 ms
menu_bg2.png
734 ms
submenu_bg2.png
737 ms
footerbg2.png
742 ms
icon_twitter.png
751 ms
snsbg.png
765 ms
widgets.js
17 ms
information.json
1063 ms
icon_facebook.png
1093 ms
icon_player.png
1048 ms
snsbg_l.png
1068 ms
__utm.gif
15 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
40 ms
like.php
73 ms
follow_button.6a78875565a912489e9aef879c881358.ja.html
19 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
27 ms
vpc6VNjRPXV.js
139 ms
LVx-xkvaJ0b.png
156 ms
vpc6VNjRPXV.js
51 ms
jot.html
3 ms
gargantia.jp 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
Image elements do not have [alt] attributes
Links do not have a discernible name
gargantia.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
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
gargantia.jp 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
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 doesn't use legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gargantia.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 Gargantia.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.
gargantia.jp
Open Graph data is detected on the main page of Gargantia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: