Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

ffo.jp

FF11/FFXI攻略情報サイト〜ウィンダスの仲間たち

Page Load Speed

1.4 sec in total

First Response

315 ms

Resources Loaded

916 ms

Page Rendered

129 ms

ffo.jp screenshot

About Website

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

ウィンダスの仲間達はファイナルファンタジーXIの攻略情報を提供しています

Visit ffo.jp

Key Findings

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

Performance Metrics

ffo.jp performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

ffo.jp

315 ms

style.css

293 ms

rtcounter_ff11top.html

346 ms

urchin.js

174 ms

bullet.gif

292 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that 50% of them (3 requests) were addressed to the original Ffo.jp, 33% (2 requests) were made to Google-analytics.com and 17% (1 request) were made to Nornir.jp. The less responsive or slowest element that took the longest time to load (346 ms) relates to the external source Nornir.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 13.4 kB (49%)

Content Size

27.4 kB

After Optimization

14.0 kB

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

HTML Optimization

-63%

Potential reduce by 8.1 kB

  • Original 12.9 kB
  • After minification 12.2 kB
  • After compression 4.8 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 8.1 kB or 63% of the original size.

JavaScript Optimization

-36%

Potential reduce by 5.1 kB

  • Original 14.0 kB
  • After minification 14.0 kB
  • After compression 8.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 5.1 kB or 36% of the original size.

CSS Optimization

-50%

Potential reduce by 202 B

  • Original 408 B
  • After minification 389 B
  • After compression 206 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. Ffo.jp needs all CSS files to be minified and compressed as it can save up to 202 B or 50% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

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

Accessibility Review

ffo.jp accessibility score

64

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

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

High

Form elements do not have associated labels

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

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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

ffo.jp SEO score

73

Search Engine Optimization Advices

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 Ffo.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 Ffo.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 Ffo. 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: