Tools & Wizards About Us
fuzzycontrol.jp screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

fuzzycontrol.jp

Fuzzy Control Official Web Site

Page Load Speed

4.2 sec in total

First Response

666 ms

Resources Loaded

3.2 sec

Page Rendered

248 ms

fuzzycontrol.jp screenshot

About Website

Welcome to fuzzycontrol.jp homepage info - get ready to check Fuzzy Control best content right away, or after learning these important things about fuzzycontrol.jp

ファジーコントロール・オフィシャルウェブサイト

Visit fuzzycontrol.jp

Key Findings

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

Performance Metrics

fuzzycontrol.jp performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value33.8 s

0/100

10%

TBT (Total Blocking Time)

Value79,260 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.187

65/100

15%

TTI (Time to Interactive)

Value95.5 s

0/100

10%

Network Requests Diagram

fuzzycontrol.jp

666 ms

base.css

326 ms

style.css

645 ms

mmenu.css

489 ms

jquery-1.7.2.min.js

983 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 54% of them (43 requests) were addressed to the original Fuzzycontrol.jp, 13% (10 requests) were made to Static.xx.fbcdn.net and 10% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Fuzzycontrol.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 518.1 kB (35%)

Content Size

1.5 MB

After Optimization

961.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 19.0 kB

  • Original 25.1 kB
  • After minification 22.0 kB
  • After compression 6.1 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 3.1 kB, which is 12% 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 19.0 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 27.1 kB

  • Original 820.3 kB
  • After minification 793.2 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. Fuzzy Control images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 234.8 kB

  • Original 349.9 kB
  • After minification 336.5 kB
  • After compression 115.1 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 234.8 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 237.1 kB

  • Original 284.6 kB
  • After minification 275.3 kB
  • After compression 47.5 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. Fuzzycontrol.jp needs all CSS files to be minified and compressed as it can save up to 237.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (28%)

Requests Now

75

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fuzzycontrol.jp

fuzzycontrol.jp

666 ms

base.css

base.css

326 ms

style.css

style.css

645 ms

mmenu.css

mmenu.css

489 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

983 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

511 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

699 ms

jquery.mmenu.min.js

jquery.mmenu.min.js

487 ms

sound.js

sound.js

650 ms

ini.js

ini.js

649 ms

jquery.bxslider.css

jquery.bxslider.css

681 ms

slideimg23.jpg

slideimg23.jpg

818 ms

slideimg24.jpg

slideimg24.jpg

1196 ms

slideimg02.jpg

slideimg02.jpg

351 ms

bnr_solo_juon.jpg

bnr_solo_juon.jpg

201 ms

bnr_solo_satoko.jpg

bnr_solo_satoko.jpg

323 ms

bnr_solo_joe.jpg

bnr_solo_joe.jpg

326 ms

all.js

all.js

49 ms

logo.png

logo.png

289 ms

gnav01.png

gnav01.png

441 ms

gnav02.png

gnav02.png

446 ms

gnav03.png

gnav03.png

452 ms

gnav04.png

gnav04.png

483 ms

gnav05.png

gnav05.png

601 ms

gnav06.png

gnav06.png

608 ms

gnav07.png

gnav07.png

616 ms

gnav08.png

gnav08.png

658 ms

gnav09.png

gnav09.png

762 ms

head_sns_joe.png

head_sns_joe.png

770 ms

head_sns_satoko.png

head_sns_satoko.png

780 ms

head_sns_fb.png

head_sns_fb.png

834 ms

head_sns_yt.png

head_sns_yt.png

922 ms

head_sns_itunes.png

head_sns_itunes.png

932 ms

head_sns_tw.png

head_sns_tw.png

935 ms

head_btn_message.png

head_btn_message.png

941 ms

ttl_news.png

ttl_news.png

1008 ms

ico_square01.png

ico_square01.png

1083 ms

ttl_media.png

ttl_media.png

1094 ms

ttl_blog.png

ttl_blog.png

1097 ms

side_ttl_youtube.png

side_ttl_youtube.png

1104 ms

side_ttl_fb.png

side_ttl_fb.png

1183 ms

bx_loader.gif

bx_loader.gif

1243 ms

btn_visual_l.png

btn_visual_l.png

1256 ms

btn_visual_r.png

btn_visual_r.png

1260 ms

qtEhgRGu9L4

qtEhgRGu9L4

93 ms

eriMOU92_7Q

eriMOU92_7Q

68 ms

qPCMUo5u1sY

qPCMUo5u1sY

77 ms

174 ms

xd_arbiter.php

xd_arbiter.php

19 ms

xd_arbiter.php

xd_arbiter.php

32 ms

www-embed-player-vfl8xM8me.css

www-embed-player-vfl8xM8me.css

24 ms

www-embed-player.js

www-embed-player.js

60 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

124 ms

ad_status.js

ad_status.js

27 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

27 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

28 ms

ping

ping

45 ms

qtEhgRGu9L4

qtEhgRGu9L4

51 ms

eriMOU92_7Q

eriMOU92_7Q

61 ms

qPCMUo5u1sY

qPCMUo5u1sY

70 ms

like_box.php

like_box.php

102 ms

SwWqNEM2GQB.css

SwWqNEM2GQB.css

24 ms

w2xn7THaeRm.css

w2xn7THaeRm.css

25 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

31 ms

ehA1CqzHyzE.js

ehA1CqzHyzE.js

31 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

30 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

30 ms

11709691_649064331859966_4762928501500967199_n.jpg

11709691_649064331859966_4762928501500967199_n.jpg

50 ms

11050854_649063691860030_7504548082696258691_n.png

11050854_649063691860030_7504548082696258691_n.png

13 ms

550999_246544018800625_730327639_n.jpg

550999_246544018800625_730327639_n.jpg

14 ms

12744060_151575105225993_4353841303713986965_n.jpg

12744060_151575105225993_4353841303713986965_n.jpg

31 ms

559050_256000487854809_1325488849_n.jpg

559050_256000487854809_1325488849_n.jpg

81 ms

11959985_888233371256871_8522718017271525935_n.jpg

11959985_888233371256871_8522718017271525935_n.jpg

15 ms

10455254_474748842659361_123059743049447859_n.jpg

10455254_474748842659361_123059743049447859_n.jpg

13 ms

12510508_735390786595729_8005873867206545507_n.jpg

12510508_735390786595729_8005873867206545507_n.jpg

31 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

10 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

10 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

9 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

2 ms

Accessibility Review

fuzzycontrol.jp accessibility score

84

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

Links do not have a discernible name

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

fuzzycontrol.jp best practices score

58

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

High

Browser errors were logged to the console

SEO Factors

fuzzycontrol.jp SEO score

85

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

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

fuzzycontrol.jp

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