3.2 sec in total
756 ms
2.1 sec
272 ms
Visit auffenberg.com now to see the best up-to-date Auffenberg content for United States and also check out these interesting facts you probably never knew about auffenberg.com
Here at Auffenberg Dealer Group, you will discover satisfaction from our great inventory of cars, trucks, SUVs, and vans. When you shop, you are part of the family.
Visit auffenberg.comWe analyzed Auffenberg.com page load time and found that the first response time was 756 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.
auffenberg.com performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value44.5 s
0/100
25%
Value32.5 s
0/100
10%
Value63,400 ms
0/100
30%
Value0.444
21/100
15%
Value76.4 s
0/100
10%
756 ms
23 ms
13 ms
20 ms
28 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 9% of them (10 requests) were addressed to the original Auffenberg.com, 53% (61 requests) were made to Static.dealer.com and 8% (9 requests) were made to Pictures.dealer.com. The less responsive or slowest element that took the longest time to load (870 ms) belongs to the original domain Auffenberg.com.
Page size can be reduced by 1.0 MB (55%)
1.8 MB
822.4 kB
In fact, the total size of Auffenberg.com main page is 1.8 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 869.0 kB which makes up the majority of the site volume.
Potential reduce by 117.1 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 117.1 kB or 81% of the original size.
Potential reduce by 45.3 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. Auffenberg images are well optimized though.
Potential reduce by 576.2 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 576.2 kB or 66% of the original size.
Potential reduce by 281.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. Auffenberg.com needs all CSS files to be minified and compressed as it can save up to 281.8 kB or 87% of the original size.
Number of requests can be reduced by 70 (64%)
110
40
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Auffenberg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.auffenberg.com
756 ms
default.css
23 ms
widget.css
13 ms
widget.css
20 ms
variation.css
28 ms
blue_white.css
20 ms
widget.css
13 ms
widget.css
26 ms
custom.css
10 ms
newrelic.js
24 ms
modernizr-2.6.2.min.js
24 ms
pxa.min.js
53 ms
pixall.min.js
51 ms
conversion.js
92 ms
ddc.jquery.min.js
114 ms
ddc.min.js
90 ms
jquery.cycle2.min.js
48 ms
jquery.cycle2.swipe.min.js
87 ms
widget.min.js
88 ms
widget.min.js
88 ms
widget.min.js
89 ms
widget.min.js
90 ms
xregexp-all.min.js
110 ms
widget.min.js
102 ms
widget.min.js
102 ms
widget.min.js
103 ms
jquery.timeago.min.js
160 ms
widget.min.js
104 ms
widget.min.js
105 ms
widget.min.js
104 ms
jquery.tinyscrollbar.min.js
105 ms
widget.min.js
105 ms
tracker.min.js
106 ms
widget.min.js
106 ms
widget.min.js
106 ms
widget.min.js
109 ms
data-layer-helper.min.js
158 ms
body-bg-opt.jpg
213 ms
iframe.php
229 ms
56ee96e03bfb40978931e02425806928x.jpg
220 ms
newicon.png
275 ms
cookie-messaging.html
263 ms
analytics.js
202 ms
usedicon.png
261 ms
blank.gif
262 ms
4fb345909a6152f4faa035834df81240x.jpg
311 ms
a231ac9e9e66299f6cf4553393c4d511x.jpg
311 ms
9258e43126f45187e1d4bffa5e3a62a4x.jpg
336 ms
8c64794577f95f80b96b28d182301951x.jpg
336 ms
thumb_3a3883aec5d673e64e620d1a9abe429ex.jpg
259 ms
thumb_9859f1bc4f0c1b087021baed8d69aed2x.jpg
260 ms
thumb_4f39b6705dbd5e1b80ea64eb3107b9d4x.jpg
258 ms
thumb_3fe3c4dc6e9a2e744b1bc8341c92bc63x.jpg
258 ms
header-bg.png
198 ms
icons.png
199 ms
nav-bg.png
198 ms
nav-bg-right.png
198 ms
group-nav-bg.png
198 ms
line.jpg
197 ms
73x50.jpg
228 ms
73x50.jpg
228 ms
73x50.jpg
227 ms
73x50.jpg
226 ms
73x50.jpg
256 ms
logo-certified-carfax-one-owner-lrg.png
226 ms
logo-certified-autocheck.png
256 ms
logo-certified-carfax-free-lrg.png
254 ms
links-list-arrow.png
281 ms
ddclogo.png
252 ms
398 ms
gtm.js
245 ms
gtm.js
341 ms
profiles
202 ms
clear.gif
400 ms
loader_102023_1.js
218 ms
landing.htm
398 ms
socialheader.png
135 ms
mycars-icon-sprite-white.png
133 ms
webfont.woff
870 ms
pixel
228 ms
collect
88 ms
collect
132 ms
collect
107 ms
collect
131 ms
ui.min.js
83 ms
dialog.min.js
84 ms
validator.min.js
107 ms
jquery.unveil.min.js
80 ms
users
246 ms
collect
63 ms
collect
59 ms
collect
59 ms
collect
59 ms
print.css
58 ms
pcdi.js
284 ms
31 ms
264 ms
pixel
141 ms
ui-icons_222222_256x240.png
158 ms
pixel
198 ms
users
272 ms
fbdrop.php
197 ms
pixel.php
190 ms
nav-forward-tab.png
60 ms
nav-forward-bg.png
57 ms
nav-forward-dots.png
58 ms
pixel.php
85 ms
jquery.min.js
52 ms
track
180 ms
nr-632.min.js
49 ms
slide-btn.png
11 ms
number-changer.js
16 ms
82e1cf9367
44 ms
getnumdata.js
19 ms
pixel.gif
22 ms
pixel.gif
5 ms
auffenberg.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
auffenberg.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
auffenberg.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Auffenberg.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 Auffenberg.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.
auffenberg.com
Open Graph description is not detected on the main page of Auffenberg. 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: