Tools & Wizards About Us
fafner.jp screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    86% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

fafner.jp

蒼穹のファフナー

Page Load Speed

3.5 sec in total

First Response

488 ms

Resources Loaded

2.8 sec

Page Rendered

255 ms

fafner.jp screenshot

About Website

Click here to check amazing Fafner content for United States. Otherwise, check out these important facts you probably never knew about fafner.jp

「蒼穹のファフナー」公式サイト

Visit fafner.jp

Key Findings

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

Performance Metrics

fafner.jp performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value3.2 s

91/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

fafner.jp

488 ms

inport.css

310 ms

rollover.js

361 ms

urchin.js

656 ms

common.css

324 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 93% of them (14 requests) were addressed to the original Fafner.jp, 7% (1 request) were made to Starchild.co.jp. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Fafner.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.3 kB (7%)

Content Size

892.9 kB

After Optimization

833.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fafner.jp main page is 892.9 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. 15% of websites need less resources to load. Images take 863.3 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 1.9 kB

  • Original 3.1 kB
  • After minification 3.0 kB
  • After compression 1.2 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 1.9 kB or 61% of the original size.

Image Optimization

-4%

Potential reduce by 37.6 kB

  • Original 863.3 kB
  • After minification 825.7 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. Fafner images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 17.1 kB

  • Original 23.0 kB
  • After minification 19.3 kB
  • After compression 5.9 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 17.1 kB or 74% of the original size.

CSS Optimization

-77%

Potential reduce by 2.7 kB

  • Original 3.5 kB
  • After minification 1.9 kB
  • After compression 818 B

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. Fafner.jp needs all CSS files to be minified and compressed as it can save up to 2.7 kB or 77% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

14

After Optimization

14

  • Images
  • JavaScript
  • CSS

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fafner. According to our analytics all requests are already optimized.

Network Requests Diagram

fafner.jp

fafner.jp

488 ms

inport.css

inport.css

310 ms

rollover.js

rollover.js

361 ms

urchin.js

urchin.js

656 ms

common.css

common.css

324 ms

layout.css

layout.css

361 ms

bg.jpg

bg.jpg

817 ms

__utm.gif

__utm.gif

319 ms

logo.png

logo.png

807 ms

btn_exodus_off.png

btn_exodus_off.png

1244 ms

btn_tv_off.png

btn_tv_off.png

1065 ms

btn_movie_off.png

btn_movie_off.png

1067 ms

btn_english_off.png

btn_english_off.png

626 ms

btn_stage2_off.png

btn_stage2_off.png

1592 ms

copy.png

copy.png

1109 ms

Accessibility Review

fafner.jp accessibility score

100

Accessibility Issues

Best Practices

fafner.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

fafner.jp SEO score

69

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fafner.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Fafner.jp main page’s claimed encoding is euc-jp. 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

fafner.jp

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