Tools & Wizards About Us
ft86.me screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

ft86.me

FT86.me 掲示板 - 日本最大級のFT86(トヨタ86、スバルBRZ)専門サイト！ - SPEC

Page Load Speed

9.1 sec in total

First Response

570 ms

Resources Loaded

6 sec

Page Rendered

2.5 sec

ft86.me screenshot

About Website

Visit ft86.me now to see the best up-to-date FT86 content for Japan and also check out these interesting facts you probably never knew about ft86.me

- トップ - FT86.meは、FT86(トヨタ86、スバルBRZ)で走りを楽しむ人のためのサイトです。

Visit ft86.me

Key Findings

We analyzed Ft86.me page load time and found that the first response time was 570 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

ft86.me performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value1,130 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.096

90/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

ft86.me

570 ms

ft86.me

1042 ms

style.css

638 ms

ft86_banner.jpg

984 ms

1342573662-1.jpg

1543 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 35% of them (15 requests) were addressed to the original Ft86.me, 21% (9 requests) were made to Pagead2.googlesyndication.com and 16% (7 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Ft86.me.

Page Optimization Overview & Recommendations

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

Content Size

4.9 MB

After Optimization

4.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ft86.me main page is 4.9 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. 45% of websites need less resources to load. Images take 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 58.7 kB

  • Original 85.1 kB
  • After minification 84.4 kB
  • After compression 26.3 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 58.7 kB or 69% of the original size.

Image Optimization

-3%

Potential reduce by 103.2 kB

  • Original 4.1 MB
  • After minification 4.0 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. FT86 images are well optimized though.

JavaScript Optimization

-38%

Potential reduce by 277.1 kB

  • Original 729.0 kB
  • After minification 729.0 kB
  • After compression 452.0 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 277.1 kB or 38% of the original size.

CSS Optimization

-84%

Potential reduce by 4.2 kB

  • Original 5.0 kB
  • After minification 3.7 kB
  • After compression 785 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. Ft86.me needs all CSS files to be minified and compressed as it can save up to 4.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (42%)

Requests Now

38

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ft86.me

ft86.me

570 ms

ft86.me

ft86.me

1042 ms

style.css

style.css

638 ms

ft86_banner.jpg

ft86_banner.jpg

984 ms

1342573662-1.jpg

1342573662-1.jpg

1543 ms

1343767661-1.jpg

1343767661-1.jpg

635 ms

1343767661-2.jpg

1343767661-2.jpg

959 ms

1487995642-1.jpg

1487995642-1.jpg

2573 ms

1489277340-1.jpg

1489277340-1.jpg

3430 ms

1489277712-1.jpg

1489277712-1.jpg

4597 ms

1449199995-1.jpg

1449199995-1.jpg

1926 ms

1463203584-1.jpg

1463203584-1.jpg

1546 ms

adsbygoogle.js

adsbygoogle.js

109 ms

1436225063-1.jpg

1436225063-1.jpg

2149 ms

1423619055-1.jpg

1423619055-1.jpg

1935 ms

pen.gif

pen.gif

1948 ms

show_ads_impl.js

show_ads_impl.js

371 ms

zrt_lookup.html

zrt_lookup.html

58 ms

ads

ads

493 ms

ads

ads

209 ms

reactive_library.js

reactive_library.js

135 ms

ads

ads

333 ms

ads

ads

326 ms

gen_204

gen_204

68 ms

pixel

pixel

234 ms

6094436044053429679

6094436044053429679

51 ms

abg_lite.js

abg_lite.js

48 ms

omrhp.js

omrhp.js

47 ms

Q12zgMmT.js

Q12zgMmT.js

48 ms

window_focus.js

window_focus.js

56 ms

qs_click_protection.js

qs_click_protection.js

55 ms

ufs_web_display.js

ufs_web_display.js

55 ms

icon.png

icon.png

37 ms

62bHydCX.html

62bHydCX.html

164 ms

activeview

activeview

72 ms

pixel

pixel

67 ms

pixel

pixel

80 ms

VKtwqYIMw_jEtcsYEdk2t0uWx1X5nCbHNvrRSJpikmk.js

VKtwqYIMw_jEtcsYEdk2t0uWx1X5nCbHNvrRSJpikmk.js

22 ms

setuid

setuid

55 ms

rum

rum

27 ms

pixel

pixel

25 ms

rum

rum

26 ms

pixel

pixel

23 ms

Accessibility Review

ft86.me accessibility score

74

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

ft86.me 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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Page has valid source maps

SEO Factors

ft86.me SEO score

58

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ft86.me 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 Ft86.me main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

ft86.me

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