Tools & Wizards About Us
faq.yamaha.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

faq.yamaha.com

FAQ Location Selector

Page Load Speed

6 sec in total

First Response

996 ms

Resources Loaded

4.9 sec

Page Rendered

87 ms

faq.yamaha.com screenshot

About Website

Welcome to faq.yamaha.com homepage info - get ready to check FAQ Yamaha best content for Japan right away, or after learning these important things about faq.yamaha.com

Visit faq.yamaha.com

Key Findings

We analyzed Faq.yamaha.com page load time and found that the first response time was 996 ms and then it took 5 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

faq.yamaha.com performance score

0

Network Requests Diagram

category

996 ms

screen.css

441 ms

category.css

431 ms

setwindow.js

430 ms

swfobject.js

435 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 37% of them (37 requests) were addressed to the original Faq.yamaha.com, 15% (15 requests) were made to Yamaha.com and 10% (10 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (996 ms) belongs to the original domain Faq.yamaha.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 848.0 kB (81%)

Content Size

1.0 MB

After Optimization

198.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Faq.yamaha.com main page is 1.0 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. Javascripts take 594.8 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 1.5 kB

  • Original 2.2 kB
  • After minification 2.2 kB
  • After compression 784 B

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 1.5 kB or 65% of the original size.

Image Optimization

-18%

Potential reduce by 1.1 kB

  • Original 6.1 kB
  • After minification 5.0 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. Obviously, FAQ Yamaha needs image optimization as it can save up to 1.1 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 441.4 kB

  • Original 594.8 kB
  • After minification 461.5 kB
  • After compression 153.4 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 441.4 kB or 74% of the original size.

CSS Optimization

-91%

Potential reduce by 404.0 kB

  • Original 443.7 kB
  • After minification 388.0 kB
  • After compression 39.6 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. Faq.yamaha.com needs all CSS files to be minified and compressed as it can save up to 404.0 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 74 (88%)

Requests Now

84

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

category

category

996 ms

screen.css

screen.css

441 ms

category.css

category.css

431 ms

setwindow.js

setwindow.js

430 ms

swfobject.js

swfobject.js

435 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

471 ms

jquery.droppy.js

jquery.droppy.js

428 ms

thickbox.js

thickbox.js

664 ms

jquery.jcarousel.js

jquery.jcarousel.js

659 ms

jquery.address-1.2.js

jquery.address-1.2.js

650 ms

jquery.scrollTo-1.4.2-min.js

jquery.scrollTo-1.4.2-min.js

672 ms

jquery-columnnav-1.0-min.js

jquery-columnnav-1.0-min.js

677 ms

sdb.js

sdb.js

700 ms

extend.js

extend.js

896 ms

category.js

category.js

878 ms

sctrack.js

sctrack.js

208 ms

base.css

base.css

442 ms

headerarea.css

headerarea.css

458 ms

footerarea.css

footerarea.css

482 ms

layout.css

layout.css

485 ms

pagetitle.css

pagetitle.css

675 ms

mainarea.css

mainarea.css

679 ms

localarea.css

localarea.css

690 ms

thickbox.css

thickbox.css

688 ms

ie6.css

ie6.css

702 ms

ie7.css

ie7.css

719 ms

jquery.jcarousel.css

jquery.jcarousel.css

890 ms

jquery.jcarousel.custom.css

jquery.jcarousel.custom.css

984 ms

extend.css

extend.css

915 ms

logo_yamaha.gif

logo_yamaha.gif

51 ms

bg_body.png

bg_body.png

229 ms

icon_new_window.gif

icon_new_window.gif

227 ms

wait.gif

wait.gif

222 ms

arrow_left.gif

arrow_left.gif

237 ms

arrow_right.gif

arrow_right.gif

234 ms

arrow_top.gif

arrow_top.gif

296 ms

btn_gnavi_products.gif

btn_gnavi_products.gif

46 ms

btn_gnavi_news_events.gif

btn_gnavi_news_events.gif

57 ms

btn_gnavi_support.gif

btn_gnavi_support.gif

47 ms

btn_gnavi_dealers.gif

btn_gnavi_dealers.gif

79 ms

btn_gnavi_music_education.gif

btn_gnavi_music_education.gif

47 ms

btn_gnavi_about_yamaha.gif

btn_gnavi_about_yamaha.gif

58 ms

gtm.js

gtm.js

34 ms

bg_pipeline.gif

bg_pipeline.gif

425 ms

ecomm-usa.css

ecomm-usa.css

163 ms

cycle.js

cycle.js

84 ms

s_code.js

s_code.js

87 ms

style_lightbox.css

style_lightbox.css

146 ms

7383542a-c0c5-436c-90e2-e83f946b216b.css

7383542a-c0c5-436c-90e2-e83f946b216b.css

139 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

85 ms

jquery.fancybox-1.3.4.js

jquery.fancybox-1.3.4.js

84 ms

slideshow.css

slideshow.css

227 ms

paragon-ui.js

paragon-ui.js

189 ms

paragon-ui.css

paragon-ui.css

190 ms

site-intercept.js

site-intercept.js

190 ms

jquery.formatCurrency-1.4.0.js

jquery.formatCurrency-1.4.0.js

226 ms

analytics.js

analytics.js

13 ms

conversion_async.js

conversion_async.js

25 ms

conversion.js

conversion.js

26 ms

aquant.js

aquant.js

13 ms

ecommerce.js

ecommerce.js

17 ms

pixel;r=1363625116;a=p-_Rsxmmer5YkRL;ezt=1;orderid=;revenue=;labels=_fp.event.FAQ;fpan=1;fpa=P0-2098150951-1458283160883;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458283160882;tzo=-180;ref=;url=http%3A%2F%2Ffaq.yamaha.com%2Fus%2Fen%2Fcategory;ogl=

pixel;r=1363625116;a=p-_Rsxmmer5YkRL;ezt=1;orderid=;revenue=;labels=_fp.event.FAQ;fpan=1;fpa=P0-2098150951-1458283160883;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458283160882;tzo=-180;ref=;url=http%3A%2F%2Ffaq.yamaha.com%2Fus%2Fen%2Fcategory;ogl=

11 ms

collect

collect

14 ms

collect

collect

12 ms

collect

collect

13 ms

collect

collect

54 ms

ga-audiences

ga-audiences

45 ms

43 ms

getcartsummary.html

getcartsummary.html

311 ms

loadingAnimation.gif

loadingAnimation.gif

670 ms

user.png

user.png

106 ms

19 ms

shopping_cart.png

shopping_cart.png

86 ms

print.css

print.css

235 ms

roundtrip.js

roundtrip.js

12 ms

QOTCFSX62BFBPO7XOEKYBJ.js

QOTCFSX62BFBPO7XOEKYBJ.js

36 ms

fbevents.hashing.js

fbevents.hashing.js

7 ms

out

out

7 ms

out

out

9 ms

out

out

9 ms

out

out

8 ms

out

out

11 ms

out

out

12 ms

out

out

12 ms

out

out

13 ms

out

out

13 ms

55 ms

u.php

u.php

90 ms

sync

sync

44 ms

adsct

adsct

93 ms

pixel

pixel

68 ms

s6147157474420

s6147157474420

47 ms

36 ms

sd

sd

19 ms

377928.gif

377928.gif

12 ms

u.php

u.php

80 ms

bounce

bounce

15 ms

tap.php

tap.php

5 ms

in

in

3 ms

SEO Factors

faq.yamaha.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faq.yamaha.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Faq.yamaha.com 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

faq.yamaha.com

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