Tools & Wizards About Us
ford-yokohama.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ford-yokohama.jp

東京・神奈川でフォード車をご愛用のみなさま メンテナンス・修理でお困りの方はサンオータスへ！

Page Load Speed

6.1 sec in total

First Response

401 ms

Resources Loaded

5.5 sec

Page Rendered

148 ms

ford-yokohama.jp screenshot

About Website

Welcome to ford-yokohama.jp homepage info - get ready to check Ford Yokohama best content for Japan right away, or after learning these important things about ford-yokohama.jp

フォード正規ディーラーとして35年の実績！専門整備士多数在籍！メンテナンス・修理はサンオータスへ！

Visit ford-yokohama.jp

Key Findings

We analyzed Ford-yokohama.jp page load time and found that the first response time was 401 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

ford-yokohama.jp performance score

0

Network Requests Diagram

ford-yokohama.jp

401 ms

704 ms

jquery-1.10.2.min.js

1587 ms

jquery.fancybox.js

1299 ms

ford.js

395 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Ford-yokohama.jp, 49% (36 requests) were made to Dealerweb.inspiration.co.jp and 16% (12 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Dealerweb.inspiration.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 818.8 kB (23%)

Content Size

3.6 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ford-yokohama.jp main page is 3.6 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. 50% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 14.5 kB

  • Original 18.2 kB
  • After minification 18.2 kB
  • After compression 3.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 14.5 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 218.3 kB

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

JavaScript Optimization

-68%

Potential reduce by 573.8 kB

  • Original 840.2 kB
  • After minification 822.6 kB
  • After compression 266.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 573.8 kB or 68% of the original size.

CSS Optimization

-78%

Potential reduce by 12.2 kB

  • Original 15.6 kB
  • After minification 11.8 kB
  • After compression 3.4 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. Ford-yokohama.jp needs all CSS files to be minified and compressed as it can save up to 12.2 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (50%)

Requests Now

66

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ford 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

ford-yokohama.jp

ford-yokohama.jp

401 ms

704 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

1587 ms

jquery.fancybox.js

jquery.fancybox.js

1299 ms

ford.js

ford.js

395 ms

jquery.fancybox.css

jquery.fancybox.css

887 ms

style.css

style.css

736 ms

419 ms

spacer

spacer

159 ms

13dc2f497be

13dc2f497be

342 ms

1437631c2f7

1437631c2f7

705 ms

embed

embed

126 ms

13dc304bb84

13dc304bb84

472 ms

13dc304dca7_0

13dc304dca7_0

495 ms

13dc304dca7

13dc304dca7

785 ms

1527c56c7c2

1527c56c7c2

2466 ms

1504a497ae5

1504a497ae5

2008 ms

14fac46c2dc

14fac46c2dc

2313 ms

14f683b8516

14f683b8516

1577 ms

14f16460712_0

14f16460712_0

2154 ms

148a707f067

148a707f067

941 ms

148a7198ea6

148a7198ea6

1096 ms

148a71c2c6c

148a71c2c6c

1251 ms

148a71deec4

148a71deec4

1407 ms

148a71f5c7d

148a71f5c7d

1562 ms

148a7204d7d

148a7204d7d

1718 ms

148a721b57e

148a721b57e

1731 ms

148a70b6232

148a70b6232

1873 ms

148a70973e9

148a70973e9

1885 ms

148a70b4b55

148a70b4b55

2029 ms

148a70af1ff

148a70af1ff

2043 ms

148a70973e4

148a70973e4

2179 ms

148a70ae8fa

148a70ae8fa

2184 ms

148a70b3698

148a70b3698

2198 ms

1525c778a15

1525c778a15

2485 ms

148a70973e0

148a70973e0

2349 ms

148a70973d6

148a70973d6

2339 ms

148a70973db

148a70973db

2352 ms

1502279e4e7_0

1502279e4e7_0

2815 ms

14fa5aac5c9

14fa5aac5c9

3262 ms

148a70973cc

148a70973cc

2520 ms

13dc2f57199

13dc2f57199

2506 ms

13dc2f5719a

13dc2f5719a

2627 ms

148a70973d2

148a70973d2

2649 ms

ga.js

ga.js

13 ms

__utm.gif

__utm.gif

23 ms

js

js

42 ms

init_embed.js

init_embed.js

27 ms

common.js

common.js

36 ms

map.js

map.js

35 ms

google4.png

google4.png

65 ms

overlay.js

overlay.js

7 ms

util.js

util.js

44 ms

onion.js

onion.js

61 ms

search_impl.js

search_impl.js

61 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

131 ms

stats.js

stats.js

52 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

36 ms

kh

kh

65 ms

transparent.png

transparent.png

19 ms

controls.js

controls.js

17 ms

vt

vt

103 ms

vt

vt

113 ms

vt

vt

116 ms

vt

vt

114 ms

vt

vt

115 ms

css

css

73 ms

mapcnt6.png

mapcnt6.png

34 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

30 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

35 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

43 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

45 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

21 ms

SEO Factors

ford-yokohama.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ford-yokohama.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 Ford-yokohama.jp main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

ford-yokohama.jp

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