Tools & Wizards About Us
oyama.fgaj-dealer.jp screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

oyama.fgaj-dealer.jp

Page Load Speed

5.2 sec in total

First Response

380 ms

Resources Loaded

4.7 sec

Page Rendered

204 ms

oyama.fgaj-dealer.jp screenshot

About Website

Visit oyama.fgaj-dealer.jp now to see the best up-to-date Oyama Fgaj Dealer content for Japan and also check out these interesting facts you probably never knew about oyama.fgaj-dealer.jp

FIAT公式ディーラー フィアット小山です。店舗所在地、取り扱い展示車・試乗車、キャンペーン情報のお知らせ、フィアット中古車情報の検索をご案内。フィアット小山店へのお問い合わせもこちらから。

Visit oyama.fgaj-dealer.jp

Key Findings

We analyzed Oyama.fgaj-dealer.jp page load time and found that the first response time was 380 ms and then it took 4.9 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

oyama.fgaj-dealer.jp performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value4.6 s

70/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.076

95/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

oyama.fgaj-dealer.jp

380 ms

633 ms

theme.css.xhtml

534 ms

jquery.fancybox.css.xhtml

361 ms

jquery-1.10.2.min.js.xhtml

908 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 49% of them (44 requests) were addressed to the original Oyama.fgaj-dealer.jp, 17% (15 requests) were made to Ods.fiatchrysler.jp and 13% (12 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Ods.fiatchrysler.jp.

Page Optimization Overview & Recommendations

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

Content Size

3.6 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oyama.fgaj-dealer.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. 55% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 23.6 kB

  • Original 28.0 kB
  • After minification 19.5 kB
  • After compression 4.4 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 8.5 kB, which is 30% 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 23.6 kB or 84% of the original size.

Image Optimization

-9%

Potential reduce by 236.1 kB

  • Original 2.6 MB
  • After minification 2.4 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. Oyama Fgaj Dealer images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 601.5 kB

  • Original 877.0 kB
  • After minification 848.8 kB
  • After compression 275.5 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 601.5 kB or 69% of the original size.

CSS Optimization

-87%

Potential reduce by 60.3 kB

  • Original 69.3 kB
  • After minification 59.6 kB
  • After compression 9.1 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. Oyama.fgaj-dealer.jp needs all CSS files to be minified and compressed as it can save up to 60.3 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

82

After Optimization

61

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oyama.fgaj-dealer.jp

oyama.fgaj-dealer.jp

380 ms

633 ms

theme.css.xhtml

theme.css.xhtml

534 ms

jquery.fancybox.css.xhtml

jquery.fancybox.css.xhtml

361 ms

jquery-1.10.2.min.js.xhtml

jquery-1.10.2.min.js.xhtml

908 ms

jquery.corner.js.xhtml

jquery.corner.js.xhtml

364 ms

fiat.js.xhtml

fiat.js.xhtml

367 ms

jquery-youtubelayer.js.xhtml

jquery-youtubelayer.js.xhtml

381 ms

jquery.fancybox.js.xhtml

jquery.fancybox.js.xhtml

898 ms

style.css.xhtml

style.css.xhtml

766 ms

ga.js

ga.js

53 ms

etbhth6on.jpg

etbhth6on.jpg

358 ms

maps

maps

50 ms

bg.jpg.xhtml

bg.jpg.xhtml

184 ms

bg_dot_line.gif.xhtml

bg_dot_line.gif.xhtml

182 ms

logo.jpg.xhtml

logo.jpg.xhtml

188 ms

dot_line.jpg.xhtml

dot_line.jpg.xhtml

192 ms

left_topmenu1.jpg.xhtml

left_topmenu1.jpg.xhtml

188 ms

left_topmenu2.jpg.xhtml

left_topmenu2.jpg.xhtml

178 ms

left_topmenu3.jpg.xhtml

left_topmenu3.jpg.xhtml

355 ms

businesshours_title.jpg.xhtml

businesshours_title.jpg.xhtml

366 ms

businesshours.jpg.xhtml

businesshours.jpg.xhtml

369 ms

holiday.jpg.xhtml

holiday.jpg.xhtml

370 ms

tel.jpg.xhtml

tel.jpg.xhtml

372 ms

store_mail.jpg.xhtml

store_mail.jpg.xhtml

385 ms

address.jpg.xhtml

address.jpg.xhtml

530 ms

toggle.png.xhtml

toggle.png.xhtml

580 ms

menu1.jpg.xhtml

menu1.jpg.xhtml

580 ms

menu2.jpg.xhtml

menu2.jpg.xhtml

581 ms

menu3.jpg.xhtml

menu3.jpg.xhtml

582 ms

menu4.jpg.xhtml

menu4.jpg.xhtml

583 ms

menu5.jpg.xhtml

menu5.jpg.xhtml

706 ms

menu6.jpg.xhtml

menu6.jpg.xhtml

735 ms

slidebullets.png.xhtml

slidebullets.png.xhtml

741 ms

topic_bg.jpg.xhtml

topic_bg.jpg.xhtml

741 ms

benvenuto.png.xhtml

benvenuto.png.xhtml

742 ms

topmenu_td1.png.xhtml

topmenu_td1.png.xhtml

772 ms

topmenu_td2.png.xhtml

topmenu_td2.png.xhtml

881 ms

blank.gif.xhtml

blank.gif.xhtml

916 ms

topmenu_td1b.png.xhtml

topmenu_td1b.png.xhtml

928 ms

topmenu_td2b.png.xhtml

topmenu_td2b.png.xhtml

926 ms

topcars_title.png.xhtml

topcars_title.png.xhtml

929 ms

carsmore.png.xhtml

carsmore.png.xhtml

965 ms

bodycolor.jpg.xhtml

bodycolor.jpg.xhtml

1057 ms

interiorcolor.jpg.xhtml

interiorcolor.jpg.xhtml

1099 ms

copyright.png.xhtml

copyright.png.xhtml

1111 ms

hn3s7y7w4.jpg

hn3s7y7w4.jpg

1036 ms

ighnts7w3.jpg

ighnts7w3.jpg

1282 ms

llgkr47w1.jpg

llgkr47w1.jpg

1100 ms

n99ve27u9.jpg

n99ve27u9.jpg

987 ms

rspu1y7ux.jpg

rspu1y7ux.jpg

1141 ms

h9aa537u9.jpg

h9aa537u9.jpg

1720 ms

xvq1v47r6.jpg

xvq1v47r6.jpg

1366 ms

ey46ek7qy.jpg

ey46ek7qy.jpg

1553 ms

q023lx7wy.JPG

q023lx7wy.JPG

2219 ms

dnshdr7u2.JPG

dnshdr7u2.JPG

2863 ms

m6ledy7sk.jpg

m6ledy7sk.jpg

1460 ms

g9vkx57sm.jpg

g9vkx57sm.jpg

1557 ms

qau3yd7v9.jpg

qau3yd7v9.jpg

1638 ms

qlgqje7we.jpg

qlgqje7we.jpg

1726 ms

topmenu_td_bg.png.xhtml

topmenu_td_bg.png.xhtml

1069 ms

embed

embed

269 ms

inpage_linkid.js

inpage_linkid.js

21 ms

__utm.gif

__utm.gif

19 ms

__utm.gif

__utm.gif

15 ms

js

js

90 ms

init_embed.js

init_embed.js

48 ms

common.js

common.js

58 ms

map.js

map.js

79 ms

google4.png

google4.png

27 ms

overlay.js

overlay.js

25 ms

util.js

util.js

70 ms

onion.js

onion.js

72 ms

search_impl.js

search_impl.js

68 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

105 ms

stats.js

stats.js

28 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

35 ms

transparent.png

transparent.png

29 ms

kh

kh

85 ms

controls.js

controls.js

23 ms

vt

vt

93 ms

vt

vt

47 ms

css

css

54 ms

mapcnt6.png

mapcnt6.png

17 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

24 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

27 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

34 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

33 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

23 ms

Accessibility Review

oyama.fgaj-dealer.jp accessibility score

78

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

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

oyama.fgaj-dealer.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

oyama.fgaj-dealer.jp SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

    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 Oyama.fgaj-dealer.jp 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 Oyama.fgaj-dealer.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

oyama.fgaj-dealer.jp

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