Tools & Wizards About Us
myfuzzy.jp screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

myfuzzy.jp

経営コンサルティング/自動車教習所|ファジー・マネジメント創研

Page Load Speed

5 sec in total

First Response

792 ms

Resources Loaded

4.1 sec

Page Rendered

142 ms

myfuzzy.jp screenshot

About Website

Click here to check amazing Myfuzzy content. Otherwise, check out these important facts you probably never knew about myfuzzy.jp

経営,コンサルティング,自動車教習所,ショッピングモール,私立学校

Visit myfuzzy.jp

Key Findings

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

Performance Metrics

myfuzzy.jp performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

myfuzzy.jp

792 ms

common.css

963 ms

content.css

777 ms

jsapi

8 ms

jquery.plugins.js

973 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 93% of them (78 requests) were addressed to the original Myfuzzy.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Myfuzzy.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 74.3 kB (14%)

Content Size

526.3 kB

After Optimization

452.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 15.4 kB

  • Original 19.4 kB
  • After minification 19.3 kB
  • After compression 4.0 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 15.4 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 396 B

  • Original 357.3 kB
  • After minification 356.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. Myfuzzy images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 38.7 kB

  • Original 125.9 kB
  • After minification 119.8 kB
  • After compression 87.2 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 38.7 kB or 31% of the original size.

CSS Optimization

-83%

Potential reduce by 19.7 kB

  • Original 23.7 kB
  • After minification 18.8 kB
  • After compression 4.0 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. Myfuzzy.jp needs all CSS files to be minified and compressed as it can save up to 19.7 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

81

After Optimization

58

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

myfuzzy.jp

myfuzzy.jp

792 ms

common.css

common.css

963 ms

content.css

content.css

777 ms

jsapi

jsapi

8 ms

jquery.plugins.js

jquery.plugins.js

973 ms

jquery.command.js

jquery.command.js

777 ms

jquery.page-scroller-308.js

jquery.page-scroller-308.js

778 ms

rollover.js

rollover.js

793 ms

loader.js

loader.js

19 ms

jquery.min.js

jquery.min.js

73 ms

bg.jpg

bg.jpg

233 ms

logo.jpg

logo.jpg

231 ms

tel.gif

tel.gif

232 ms

tel2.gif

tel2.gif

230 ms

hnav01_rollout.jpg

hnav01_rollout.jpg

231 ms

hnav02_rollout.jpg

hnav02_rollout.jpg

232 ms

hnav03_rollout.jpg

hnav03_rollout.jpg

375 ms

hnav04_rollout.jpg

hnav04_rollout.jpg

375 ms

nav-bg.gif

nav-bg.gif

422 ms

nav01_rollout.jpg

nav01_rollout.jpg

380 ms

nav02_rollout.jpg

nav02_rollout.jpg

377 ms

nav03_rollout.jpg

nav03_rollout.jpg

394 ms

nav04_rollout.jpg

nav04_rollout.jpg

561 ms

nav05_rollout.jpg

nav05_rollout.jpg

561 ms

main-img.jpg

main-img.jpg

939 ms

main-img-sub_rollout.jpg

main-img-sub_rollout.jpg

568 ms

con-box02.jpg

con-box02.jpg

589 ms

con-box01.jpg

con-box01.jpg

612 ms

top01.gif

top01.gif

748 ms

bn01.jpg

bn01.jpg

748 ms

bn02.jpg

bn02.jpg

756 ms

bn03.jpg

bn03.jpg

978 ms

bn04.jpg

bn04.jpg

799 ms

bn05.jpg

bn05.jpg

1120 ms

bn06.jpg

bn06.jpg

936 ms

con-box03.jpg

con-box03.jpg

946 ms

top02.gif

top02.gif

988 ms

top04_rollout.gif

top04_rollout.gif

1123 ms

top05.gif

top05.gif

1127 ms

top06.gif

top06.gif

1133 ms

top08.gif

top08.gif

1174 ms

line.gif

line.gif

1176 ms

top04.gif

top04.gif

1307 ms

top07.gif

top07.gif

1309 ms

top03.gif

top03.gif

1314 ms

analytics.js

analytics.js

14 ms

sub13.gif

sub13.gif

1267 ms

collect

collect

24 ms

js

js

61 ms

sub02.jpg

sub02.jpg

1143 ms

sub01.jpg

sub01.jpg

1137 ms

sub03_rollout.jpg

sub03_rollout.jpg

1268 ms

sub04.jpg

sub04.jpg

1270 ms

sub05.jpg

sub05.jpg

1274 ms

sub07.jpg

sub07.jpg

1279 ms

sub08_rollout.gif

sub08_rollout.gif

1182 ms

sub09_rollout.gif

sub09_rollout.gif

1193 ms

sub10_rollout.gif

sub10_rollout.gif

1310 ms

sub11_rollout.gif

sub11_rollout.gif

1310 ms

sub12.jpg

sub12.jpg

1302 ms

sub06.jpg

sub06.jpg

1281 ms

kigyou_b1.png

kigyou_b1.png

1184 ms

sub13.jpg

sub13.jpg

1202 ms

page-top.gif

page-top.gif

1306 ms

footer01.gif

footer01.gif

1287 ms

footer03.gif

footer03.gif

1272 ms

footer02.gif

footer02.gif

1143 ms

footer04.gif

footer04.gif

1184 ms

hnav01_rollover.jpg

hnav01_rollover.jpg

196 ms

hnav02_rollover.jpg

hnav02_rollover.jpg

189 ms

hnav03_rollover.jpg

hnav03_rollover.jpg

190 ms

hnav04_rollover.jpg

hnav04_rollover.jpg

188 ms

nav01_rollover.jpg

nav01_rollover.jpg

189 ms

nav02_rollover.jpg

nav02_rollover.jpg

190 ms

nav03_rollover.jpg

nav03_rollover.jpg

375 ms

nav04_rollover.jpg

nav04_rollover.jpg

376 ms

nav05_rollover.jpg

nav05_rollover.jpg

377 ms

main-img-sub_rollover.jpg

main-img-sub_rollover.jpg

379 ms

top04_rollover.gif

top04_rollover.gif

378 ms

sub03_rollover.jpg

sub03_rollover.jpg

390 ms

sub08_rollover.gif

sub08_rollover.gif

562 ms

sub09_rollover.gif

sub09_rollover.gif

562 ms

sub10_rollover.gif

sub10_rollover.gif

565 ms

sub11_rollover.gif

sub11_rollover.gif

565 ms

Accessibility Review

myfuzzy.jp accessibility score

73

Accessibility Issues

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

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

Best Practices

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

myfuzzy.jp SEO score

62

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

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 Myfuzzy.jp 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 Myfuzzy.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

myfuzzy.jp

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