Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

ff12.jp

FF13-2攻略|極限攻略データベース

Page Load Speed

2.6 sec in total

First Response

744 ms

Resources Loaded

1.7 sec

Page Rendered

131 ms

ff12.jp screenshot

About Website

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

FF13-2の最強攻略サイト。攻略チャート、マルチエンディング、ボス攻略、マップ、仲間モンスター、フラグメント一覧など攻略情報多数掲載。FF攻略といえば極限!

Visit ff12.jp

Key Findings

We analyzed Ff12.jp page load time and found that the first response time was 744 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

ff12.jp performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value2,550 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.073

96/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

ff12.jp

744 ms

plusone.js

65 ms

ff13_index.css

316 ms

show_ads.js

34 ms

cb=gapi.loaded_0

5 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original Ff12.jp, 23% (7 requests) were made to Apis.google.com and 13% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (853 ms) relates to the external source I.yimg.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.4 kB (36%)

Content Size

83.4 kB

After Optimization

53.0 kB

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

HTML Optimization

-74%

Potential reduce by 20.3 kB

  • Original 27.5 kB
  • After minification 22.8 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 4.8 kB, which is 17% 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 20.3 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 8.9 kB
  • After minification 8.9 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. Ff 12 images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 6.2 kB

  • Original 41.7 kB
  • After minification 41.2 kB
  • After compression 35.5 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 6.2 kB or 15% of the original size.

CSS Optimization

-74%

Potential reduce by 3.9 kB

  • Original 5.2 kB
  • After minification 4.3 kB
  • After compression 1.4 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. Ff12.jp needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (54%)

Requests Now

26

After Optimization

12

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ff 12. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

ff12.jp accessibility score

69

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

ff12.jp SEO score

86

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

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 uses legible font sizes

High

Tap targets are not sized appropriately

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

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