Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

gargantia.jp

「翠星のガルガンティア」アニメ公式サイト

Page Load Speed

1.9 sec in total

First Response

50 ms

Resources Loaded

1.8 sec

Page Rendered

98 ms

gargantia.jp screenshot

About Website

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

Key Findings

We analyzed Gargantia.jp page load time and found that the first response time was 50 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

gargantia.jp performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

gargantia.jp

50 ms

gargantia.jp

654 ms

common.css

26 ms

colorbox.css

419 ms

jquery.jqzoom.css

31 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 72% of them (38 requests) were addressed to the original Gargantia.jp, 9% (5 requests) were made to Platform.twitter.com and 6% (3 requests) were made to Syndication.twitter.com. The less responsive or slowest element that took the longest time to load (734 ms) belongs to the original domain Gargantia.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 26.4 kB (13%)

Content Size

203.8 kB

After Optimization

177.4 kB

In fact, the total size of Gargantia.jp main page is 203.8 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. 20% of websites need less resources to load. Javascripts take 96.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 13.3 kB

  • Original 17.3 kB
  • After minification 15.9 kB
  • After compression 4.0 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 13.3 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 988 B

  • Original 83.8 kB
  • After minification 82.8 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.

JavaScript Optimization

-12%

Potential reduce by 11.1 kB

  • Original 96.1 kB
  • After minification 96.1 kB
  • After compression 85.0 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 11.1 kB or 12% of the original size.

CSS Optimization

-16%

Potential reduce by 1.1 kB

  • Original 6.6 kB
  • After minification 6.6 kB
  • After compression 5.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. Gargantia.jp needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (67%)

Requests Now

49

After Optimization

16

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 22 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

gargantia.jp accessibility score

73

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

gargantia.jp best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

gargantia.jp SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document doesn't use 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 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.

Social Sharing Optimization

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: