Tools & Wizards About Us
play-ff11.com screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    79% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 77

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

play-ff11.com

FF11攻略wiki - PLAY FINAL FANTASY XI

Page Load Speed

3.7 sec in total

First Response

1.1 sec

Resources Loaded

2.4 sec

Page Rendered

195 ms

play-ff11.com screenshot

About Website

Visit play-ff11.com now to see the best up-to-date PLAY Ff11 content for Japan and also check out these interesting facts you probably never knew about play-ff11.com

FF11の攻略wiki。クエスト、ミッション、追加シナリオなどの情報や武器防具、素材、狩場、合成などのデータを掲載。

Visit play-ff11.com

Key Findings

We analyzed Play-ff11.com page load time and found that the first response time was 1.1 sec and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

play-ff11.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

98/100

25%

SI (Speed Index)

Value10.2 s

9/100

10%

TBT (Total Blocking Time)

Value860 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

play-ff11.com

1099 ms

main.css

713 ms

favicon.css

371 ms

smooth-src-comments.js

539 ms

highslide.js

757 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Play-ff11.com, 47% (18 requests) were made to Playshinra2.sakura.ne.jp and 13% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Play-ff11.com.

Page Optimization Overview & Recommendations

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

Content Size

191.0 kB

After Optimization

165.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Play-ff11.com main page is 191.0 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. 35% of websites need less resources to load. Images take 103.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 18.6 kB

  • Original 24.1 kB
  • After minification 23.6 kB
  • After compression 5.6 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 18.6 kB or 77% of the original size.

Image Optimization

-6%

Potential reduce by 6.4 kB

  • Original 103.1 kB
  • After minification 96.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. PLAY Ff11 images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 465 B

  • Original 63.3 kB
  • After minification 63.2 kB
  • After compression 62.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. This website has mostly compressed JavaScripts.

CSS Optimization

-29%

Potential reduce by 108 B

  • Original 371 B
  • After minification 310 B
  • After compression 263 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. Play-ff11.com needs all CSS files to be minified and compressed as it can save up to 108 B or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (53%)

Requests Now

36

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

play-ff11.com

play-ff11.com

1099 ms

main.css

main.css

713 ms

favicon.css

favicon.css

371 ms

smooth-src-comments.js

smooth-src-comments.js

539 ms

highslide.js

highslide.js

757 ms

adsbygoogle.js

adsbygoogle.js

6 ms

cursor.gif

cursor.gif

192 ms

favicon.hatena.ne.jp

favicon.hatena.ne.jp

531 ms

back.png

back.png

199 ms

top.gif

top.gif

189 ms

navi1.png

navi1.png

187 ms

h5.png

h5.png

351 ms

list1.gif

list1.gif

379 ms

banner.jpg

banner.jpg

381 ms

mini-banner.jpg

mini-banner.jpg

382 ms

ca-pub-1342753992033220.js

ca-pub-1342753992033220.js

55 ms

zrt_lookup.html

zrt_lookup.html

42 ms

show_ads_impl.js

show_ads_impl.js

59 ms

h2.png

h2.png

367 ms

list2.png

list2.png

369 ms

h3.png

h3.png

484 ms

h4.png

h4.png

507 ms

bottom2.png

bottom2.png

492 ms

ads

ads

263 ms

osd.js

osd.js

10 ms

ads

ads

235 ms

163035407530238160

163035407530238160

94 ms

abg.js

abg.js

43 ms

m_js_controller.js

m_js_controller.js

38 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

86 ms

15282391856278954408

15282391856278954408

71 ms

s

s

43 ms

x_button_blue2.png

x_button_blue2.png

14 ms

7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js

7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js

5 ms

rounded-white.png

rounded-white.png

200 ms

zoomout.cur

zoomout.cur

187 ms

loader.gif

loader.gif

184 ms

ui

ui

27 ms

Accessibility Review

play-ff11.com accessibility score

62

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

Form elements do not have associated labels

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

play-ff11.com best practices score

77

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

play-ff11.com SEO score

62

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Play-ff11.com 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 Play-ff11.com 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

play-ff11.com

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