Tools & Wizards About Us
yokohama.com.au screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

yokohama.com.au

Yokohama Tyre Range, Sizes And Where To Buy | YOKOHAMA

Page Load Speed

7.2 sec in total

First Response

914 ms

Resources Loaded

5.9 sec

Page Rendered

356 ms

yokohama.com.au screenshot

About Website

Visit yokohama.com.au now to see the best up-to-date Yokohama content for United States and also check out these interesting facts you probably never knew about yokohama.com.au

Yokohama Tyres

Visit yokohama.com.au

Key Findings

We analyzed Yokohama.com.au page load time and found that the first response time was 914 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

yokohama.com.au performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value20.0 s

0/100

25%

SI (Speed Index)

Value15.8 s

0/100

10%

TBT (Total Blocking Time)

Value620 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.419

23/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

yokohama.com.au

914 ms

www.yokohama.com.au

1519 ms

yokohama.css

1088 ms

jquery.fancybox.css

446 ms

jsapi

20 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 65% of them (55 requests) were addressed to the original Yokohama.com.au, 5% (4 requests) were made to F.vimeocdn.com and 5% (4 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Yokohama.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 622.0 kB (25%)

Content Size

2.5 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yokohama.com.au main page is 2.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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 32.6 kB

  • Original 44.3 kB
  • After minification 42.2 kB
  • After compression 11.7 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 32.6 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 54.9 kB

  • Original 1.7 MB
  • After minification 1.6 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. Yokohama images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 356.0 kB

  • Original 560.4 kB
  • After minification 556.0 kB
  • After compression 204.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 356.0 kB or 64% of the original size.

CSS Optimization

-86%

Potential reduce by 178.5 kB

  • Original 207.4 kB
  • After minification 202.0 kB
  • After compression 28.9 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. Yokohama.com.au needs all CSS files to be minified and compressed as it can save up to 178.5 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

77

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yokohama. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

yokohama.com.au

yokohama.com.au

914 ms

www.yokohama.com.au

www.yokohama.com.au

1519 ms

yokohama.css

yokohama.css

1088 ms

jquery.fancybox.css

jquery.fancybox.css

446 ms

jsapi

jsapi

20 ms

VisitorIdentification.aspx

VisitorIdentification.aspx

458 ms

conversion.js

conversion.js

16 ms

jquery.inputhints.js

jquery.inputhints.js

237 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

447 ms

jquery.carousel.min.js

jquery.carousel.min.js

228 ms

bootstrap-button.js

bootstrap-button.js

451 ms

common.js

common.js

454 ms

jquery.min.js

jquery.min.js

32 ms

swfobject.js

swfobject.js

54 ms

js

js

52 ms

bg-blue-earth.jpg

bg-blue-earth.jpg

1404 ms

logo.png

logo.png

223 ms

FA_YOKO-0185_YOKO_WebBanner_01.ashx

FA_YOKO-0185_YOKO_WebBanner_01.ashx

891 ms

FA_YOKO-0185_YOKO_WebBanner_02.ashx

FA_YOKO-0185_YOKO_WebBanner_02.ashx

676 ms

FA_YOKO-0185_YOKO_WebBanner_03.ashx

FA_YOKO-0185_YOKO_WebBanner_03.ashx

925 ms

FA_YOKO-0185_YOKO_WebBanner_04.ashx

FA_YOKO-0185_YOKO_WebBanner_04.ashx

904 ms

FA_YOKO-0157_YOKO_Safer1.ashx

FA_YOKO-0157_YOKO_Safer1.ashx

868 ms

FA_YOKO-0157_YOKO_Safer2.ashx

FA_YOKO-0157_YOKO_Safer2.ashx

902 ms

FA_YOKO-0157_YOKO_Safer3.ashx

FA_YOKO-0157_YOKO_Safer3.ashx

1087 ms

FA_YOKO-0157_YOKO_Safer4.ashx

FA_YOKO-0157_YOKO_Safer4.ashx

1114 ms

FA_YOKO-0157_YOKO_LongLasting_1.ashx

FA_YOKO-0157_YOKO_LongLasting_1.ashx

1353 ms

FA_YOKO-0157_YOKO_LongLasting_2.ashx

FA_YOKO-0157_YOKO_LongLasting_2.ashx

1132 ms

FA_YOKO-0157_YOKO_LongLasting_3.ashx

FA_YOKO-0157_YOKO_LongLasting_3.ashx

1157 ms

FA_YOKO-0157_YOKO_LongLasting_4.ashx

FA_YOKO-0157_YOKO_LongLasting_4.ashx

1305 ms

FA_YOKO-0157_YOKO_Home_Precision_01.ashx

FA_YOKO-0157_YOKO_Home_Precision_01.ashx

1338 ms

FA_YOKO-0165_YOKO_Home_02.ashx

FA_YOKO-0165_YOKO_Home_02.ashx

1358 ms

FA_YOKO-0157_YOKO_Home_Precision_03.ashx

FA_YOKO-0157_YOKO_Home_Precision_03.ashx

1389 ms

FA_YOKO-0165_YOKO_Home_04.ashx

FA_YOKO-0165_YOKO_Home_04.ashx

1522 ms

FA_YOKO-0157_YOKO_Home_Tough_1.ashx

FA_YOKO-0157_YOKO_Home_Tough_1.ashx

1563 ms

FA_YOKO-0157_YOKO_Home_Tough_2.ashx

FA_YOKO-0157_YOKO_Home_Tough_2.ashx

1578 ms

FA_YOKO-0157_YOKO_Home_Tough_3.ashx

FA_YOKO-0157_YOKO_Home_Tough_3.ashx

1584 ms

FA_YOKO-0157_YOKO_Home_Tough_4.ashx

FA_YOKO-0157_YOKO_Home_Tough_4.ashx

1626 ms

01_YOKO-0196_YOKO_Home_01.ashx

01_YOKO-0196_YOKO_Home_01.ashx

1629 ms

01_YOKO-0196_YOKO_Home_02.ashx

01_YOKO-0196_YOKO_Home_02.ashx

1954 ms

01_YOKO-0196_YOKO_Home_03.ashx

01_YOKO-0196_YOKO_Home_03.ashx

2006 ms

01_YOKO-0196_YOKO_Home_04.ashx

01_YOKO-0196_YOKO_Home_04.ashx

2027 ms

02_YOKO-0152_YOKO_WebBanner_01.ashx

02_YOKO-0152_YOKO_WebBanner_01.ashx

2034 ms

02_YOKO-0152_YOKO_WebBanner_02.ashx

02_YOKO-0152_YOKO_WebBanner_02.ashx

2091 ms

02_YOKO-0152_YOKO_WebBanner_03.ashx

02_YOKO-0152_YOKO_WebBanner_03.ashx

1865 ms

02_YOKO-0152_YOKO_WebBanner_04.ashx

02_YOKO-0152_YOKO_WebBanner_04.ashx

2102 ms

tile-heading.png

tile-heading.png

2169 ms

BJ%20TM2%20tile.ashx

BJ%20TM2%20tile.ashx

2230 ms

ADVAN%20Neova%20AD08%20Hero%20Gallery%20Image.ashx

ADVAN%20Neova%20AD08%20Hero%20Gallery%20Image.ashx

2277 ms

FEB%20Blog%20Header%20Image%20for%20Orange%20Oil%20Tyres.ashx

FEB%20Blog%20Header%20Image%20for%20Orange%20Oil%20Tyres.ashx

2288 ms

ADVAN%20Sport%20V105%20Winner%20Tile.ashx

ADVAN%20Sport%20V105%20Winner%20Tile.ashx

2324 ms

TSA-sticker-member2x.png

TSA-sticker-member2x.png

2336 ms

analytics.js

analytics.js

62 ms

75 ms

155611850

155611850

124 ms

54345921

54345921

77 ms

143549709

143549709

132 ms

collect

collect

27 ms

33 ms

collect

collect

130 ms

player.js

player.js

134 ms

player.css

player.css

124 ms

ga.js

ga.js

85 ms

vuid.min.js

vuid.min.js

122 ms

73 ms

karbon-medium-webfont.woff

karbon-medium-webfont.woff

2170 ms

__utm.gif

__utm.gif

100 ms

__utm.gif

__utm.gif

84 ms

__utm.gif

__utm.gif

86 ms

ga-audiences

ga-audiences

83 ms

proxy.html

proxy.html

80 ms

390542109.webp

390542109.webp

96 ms

5351019_60x60.jpg

5351019_60x60.jpg

61 ms

541159882.webp

541159882.webp

26 ms

556415788.webp

556415788.webp

28 ms

nr-885.min.js

nr-885.min.js

93 ms

689d5b4562

689d5b4562

115 ms

break.png

break.png

1785 ms

features.png

features.png

1640 ms

link-more.png

link-more.png

1630 ms

footer-panels.png

footer-panels.png

1659 ms

facebook.png

facebook.png

1674 ms

twitter.png

twitter.png

1682 ms

youtube.png

youtube.png

1594 ms

tbone.png

tbone.png

1619 ms

Accessibility Review

yokohama.com.au accessibility score

64

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

yokohama.com.au best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

yokohama.com.au SEO score

82

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yokohama.com.au can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Yokohama.com.au 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

yokohama.com.au

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