Tools & Wizards About Us
ginei.jp screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

ginei.jp

銀河英雄伝説 ON THE WEB

Page Load Speed

3.8 sec in total

First Response

341 ms

Resources Loaded

3.2 sec

Page Rendered

201 ms

ginei.jp screenshot

About Website

Welcome to ginei.jp homepage info - get ready to check Ginei best content for Japan right away, or after learning these important things about ginei.jp

アニメシリーズ『銀河英雄伝説』の公式ページ。本伝のあらすじ、キャラクター紹介、商品情報など。正確かつ最新の情報はこちらをチェック！スタッフへの過去のインタビュー抜粋記事は、毎週火曜更新です。

Visit ginei.jp

Key Findings

We analyzed Ginei.jp page load time and found that the first response time was 341 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

ginei.jp performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.327

35/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

ginei.jp

341 ms

ginei.jp

687 ms

index.php

177 ms

common.js

168 ms

cookieconsent.min.css

29 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 79% of them (26 requests) were addressed to the original Ginei.jp, 6% (2 requests) were made to Cdn.jsdelivr.net and 6% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Ginei.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 141.7 kB (9%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ginei.jp main page is 1.6 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. 35% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 11.0 kB

  • Original 15.4 kB
  • After minification 14.3 kB
  • After compression 4.4 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.0 kB or 71% of the original size.

Image Optimization

-6%

Potential reduce by 90.0 kB

  • Original 1.5 MB
  • After minification 1.4 MB

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. Ginei images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 39.0 kB

  • Original 108.6 kB
  • After minification 108.6 kB
  • After compression 69.6 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 39.0 kB or 36% of the original size.

CSS Optimization

-29%

Potential reduce by 1.8 kB

  • Original 6.0 kB
  • After minification 6.0 kB
  • After compression 4.2 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. Ginei.jp needs all CSS files to be minified and compressed as it can save up to 1.8 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (23%)

Requests Now

30

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ginei. 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.

Network Requests Diagram

ginei.jp

ginei.jp

341 ms

ginei.jp

ginei.jp

687 ms

index.php

index.php

177 ms

common.js

common.js

168 ms

cookieconsent.min.css

cookieconsent.min.css

29 ms

cssref.css

cssref.css

335 ms

jquery.bxslider.css

jquery.bxslider.css

498 ms

function.js

function.js

500 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

666 ms

jquery.bxslider.js

jquery.bxslider.js

682 ms

cookieconsent.min.js

cookieconsent.min.js

35 ms

js

js

65 ms

logo_ginei_j.gif

logo_ginei_j.gif

188 ms

logo_ginei_d.gif

logo_ginei_d.gif

186 ms

key_remaster.png

key_remaster.png

1334 ms

btn_4kremaster.png

btn_4kremaster.png

186 ms

ginei4k_gekijo1.png

ginei4k_gekijo1.png

496 ms

ginei4k_gekijo2.png

ginei4k_gekijo2.png

333 ms

ginei_1_640-408_0629.png

ginei_1_640-408_0629.png

1165 ms

alba_banner.jpg

alba_banner.jpg

498 ms

portalGoods_banner.jpg

portalGoods_banner.jpg

1002 ms

banner_IserlohnCD.png

banner_IserlohnCD.png

995 ms

bluray_banner_400_100.png

bluray_banner_400_100.png

661 ms

banner_neue400_100.png

banner_neue400_100.png

664 ms

portal_banner_400_100.jpg

portal_banner_400_100.jpg

827 ms

list_top.png

list_top.png

814 ms

controls.png

controls.png

976 ms

bx_loader.gif

bx_loader.gif

951 ms

list_bottom.png

list_bottom.png

1112 ms

js

js

47 ms

analytics.js

analytics.js

19 ms

collect

collect

63 ms

collect

collect

32 ms

Accessibility Review

ginei.jp accessibility score

97

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

ginei.jp best practices score

75

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

SEO Factors

ginei.jp SEO score

58

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ginei.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ginei.jp 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.

Social Sharing Optimization

ginei.jp

Open Graph description is not detected on the main page of Ginei. 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: