Tools & Wizards About Us
jandsautohaus3.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

jandsautohaus3.com

J&S Autohaus III | Used Luxury Cars | Hamilton Township, NJ

Page Load Speed

3.3 sec in total

First Response

876 ms

Resources Loaded

2.1 sec

Page Rendered

294 ms

jandsautohaus3.com screenshot

About Website

Welcome to jandsautohaus3.com homepage info - get ready to check Jands Autohaus 3 best content right away, or after learning these important things about jandsautohaus3.com

Shop J&S Autohaus III for your next car, truck or luxury automobile. Need financing? We can assist in your finance needs. Stop by today!

Visit jandsautohaus3.com

Key Findings

We analyzed Jandsautohaus3.com page load time and found that the first response time was 876 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

jandsautohaus3.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

www.jandsautohaus3.com

876 ms

gray_white.css

21 ms

type.css

50 ms

gray_white-widgets.css

52 ms

ldclient.min.js

49 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 91% of them (62 requests) were addressed to the original Jandsautohaus3.com, 4% (3 requests) were made to Pictures.dealer.com and 1% (1 request) were made to S2.go-mpulse.net. The less responsive or slowest element that took the longest time to load (876 ms) belongs to the original domain Jandsautohaus3.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (55%)

Content Size

2.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 196.8 kB

  • Original 269.6 kB
  • After minification 265.8 kB
  • After compression 72.9 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 196.8 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 27 B

  • Original 421.2 kB
  • After minification 421.2 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. Jands Autohaus 3 images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 479.7 kB

  • Original 927.1 kB
  • After minification 927.1 kB
  • After compression 447.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 479.7 kB or 52% of the original size.

CSS Optimization

-85%

Potential reduce by 617.9 kB

  • Original 727.6 kB
  • After minification 727.6 kB
  • After compression 109.8 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. Jandsautohaus3.com needs all CSS files to be minified and compressed as it can save up to 617.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (77%)

Requests Now

66

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.jandsautohaus3.com

www.jandsautohaus3.com

876 ms

gray_white.css

gray_white.css

21 ms

type.css

type.css

50 ms

gray_white-widgets.css

gray_white-widgets.css

52 ms

ldclient.min.js

ldclient.min.js

49 ms

pix-ddc-fp.min.js

pix-ddc-fp.min.js

384 ms

phone-swapping.min.js

phone-swapping.min.js

104 ms

ddc.jquery.async.each.min.js

ddc.jquery.async.each.min.js

124 ms

ddc.min.js

ddc.min.js

102 ms

ddc-core-js-polyfills.min.js

ddc-core-js-polyfills.min.js

103 ms

react.production.min.js

react.production.min.js

103 ms

react-dom.production.min.js

react-dom.production.min.js

103 ms

prop-types.min.js

prop-types.min.js

148 ms

react-bootstrap.min.js

react-bootstrap.min.js

105 ms

redux.min.js

redux.min.js

105 ms

react-redux.min.js

react-redux.min.js

122 ms

redux-thunk.min.js

redux-thunk.min.js

308 ms

redux-toolkit.umd.min.js

redux-toolkit.umd.min.js

120 ms

html-react-parser.min.js

html-react-parser.min.js

179 ms

umd.js

umd.js

179 ms

hysterics.js

hysterics.js

203 ms

loader.js

loader.js

181 ms

widget.min.js

widget.min.js

315 ms

data-layer-helper.min.js

data-layer-helper.min.js

180 ms

widget.min.js

widget.min.js

197 ms

widget.min.js

widget.min.js

197 ms

widget.min.js

widget.min.js

213 ms

bundle.43949da70471501522f6392f9c48e6ad.js

bundle.43949da70471501522f6392f9c48e6ad.js

229 ms

bundle.b53f6740d5f00db15f7981c3d2d60d38.js

bundle.b53f6740d5f00db15f7981c3d2d60d38.js

215 ms

lib.js

lib.js

226 ms

pubsub.min.js

pubsub.min.js

229 ms

eo.min.js

eo.min.js

319 ms

userProfileController.min.js

userProfileController.min.js

315 ms

bundle.421e099d72c3ea25f5386bd7d2133b00.js

bundle.421e099d72c3ea25f5386bd7d2133b00.js

314 ms

bundle.1ddd2ce66f803a1c53402c14fa0b69ae.js

bundle.1ddd2ce66f803a1c53402c14fa0b69ae.js

374 ms

bundle.de647c6a44b1c3f4b7ddfe7f0aecb9ac.js

bundle.de647c6a44b1c3f4b7ddfe7f0aecb9ac.js

315 ms

bundle.4e90e6fea33cebd2744cef9d5a66d3c3.js

bundle.4e90e6fea33cebd2744cef9d5a66d3c3.js

314 ms

bundle.555cd164d80bfdc372ac1a3cba743134.js

bundle.555cd164d80bfdc372ac1a3cba743134.js

280 ms

bundle.e3b0a3eca8344d337272bdb317895260.js

bundle.e3b0a3eca8344d337272bdb317895260.js

279 ms

K45LW-Y4N35-TCFUH-PEHHU-3VD8X

K45LW-Y4N35-TCFUH-PEHHU-3VD8X

290 ms

2798167a0c9b75199a0666b952299d5dx.jpg

2798167a0c9b75199a0666b952299d5dx.jpg

263 ms

analytics.js

analytics.js

33 ms

jquery.inview.min.js

jquery.inview.min.js

230 ms

0e0eb36964475139e62eb4ceccc86eb8x.jpg

0e0eb36964475139e62eb4ceccc86eb8x.jpg

86 ms

91f1a680dfb6cf04e0954764f1b3bb8bx.jpg

91f1a680dfb6cf04e0954764f1b3bb8bx.jpg

263 ms

widget.min.js

widget.min.js

223 ms

dropdown.min.js

dropdown.min.js

223 ms

widget.min.js

widget.min.js

229 ms

bundle.32dd910a990328f07de6cc8674681a5c.js

bundle.32dd910a990328f07de6cc8674681a5c.js

228 ms

widget-tracking.min.js

widget-tracking.min.js

230 ms

widget.min.js

widget.min.js

228 ms

widget.min.js

widget.min.js

238 ms

widget.min.js

widget.min.js

238 ms

variation.min.js

variation.min.js

215 ms

web-vitals.attribution.min.js

web-vitals.attribution.min.js

214 ms

index.min.js

index.min.js

210 ms

index.min.js

index.min.js

176 ms

ddc.jquery-ui.dialog.min.js

ddc.jquery-ui.dialog.min.js

179 ms

component.min.js

component.min.js

197 ms

parts.jpg

parts.jpg

334 ms

blank.gif

blank.gif

644 ms

specials.jpg

specials.jpg

179 ms

cars-on-lot.jpg

cars-on-lot.jpg

179 ms

blank.gif

blank.gif

181 ms

ddc-logo-black.png

ddc-logo-black.png

214 ms

ad-choices-logo-11x12.png

ad-choices-logo-11x12.png

172 ms

font.10140253ad16935a49ec56c73df3dd33.woff

font.10140253ad16935a49ec56c73df3dd33.woff

113 ms

config.json

config.json

53 ms

Accessibility Review

jandsautohaus3.com accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best Practices

jandsautohaus3.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

High

Page has valid source maps

SEO Factors

jandsautohaus3.com SEO score

99

Search Engine Optimization Advices

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 Jandsautohaus3.com 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 Jandsautohaus3.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

jandsautohaus3.com

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