3 sec in total
465 ms
2.4 sec
105 ms
Click here to check amazing Vwalhambra content. Otherwise, check out these important facts you probably never knew about vwalhambra.com
We are the #1 Volkswagen Dealership in Pasadena. We provide the best Volkswagen service for new and used vehicles in the area. Volkswagen Pasadena has the best inventory on all the most popular Volksw...
Visit vwalhambra.comWe analyzed Vwalhambra.com page load time and found that the first response time was 465 ms and then it took 2.5 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.
vwalhambra.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value30.7 s
0/100
25%
Value12.7 s
3/100
10%
Value9,520 ms
0/100
30%
Value0.169
70/100
15%
Value32.9 s
0/100
10%
465 ms
111 ms
362 ms
225 ms
151 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Vwalhambra.com, 3% (3 requests) were made to Pictures.dealer.com and 2% (2 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (769 ms) relates to the external source Volkswagenpasadena.com.
Page size can be reduced by 1.0 MB (51%)
2.0 MB
964.1 kB
In fact, the total size of Vwalhambra.com main page is 2.0 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. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 200.3 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 200.3 kB or 73% of the original size.
Potential reduce by 715 B
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. Vwalhambra images are well optimized though.
Potential reduce by 772.1 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 772.1 kB or 60% of the original size.
Potential reduce by 47.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. Vwalhambra.com needs all CSS files to be minified and compressed as it can save up to 47.8 kB or 29% of the original size.
Number of requests can be reduced by 74 (83%)
89
15
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vwalhambra. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 69 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.volkswagenpasadena.com
465 ms
aem.js
111 ms
dark-blue_white.css
362 ms
type.css
225 ms
dark-blue_white-widgets.css
151 ms
fod33-volkswagen.css
86 ms
dark-blue_white-mycars-desktop.css
157 ms
custom.css
59 ms
ldclient.min.js
76 ms
pix-ddc-fp.min.js
255 ms
blocker.js
84 ms
conversion.js
75 ms
js
80 ms
phone-swapping.min.js
123 ms
ddc.jquery.async.each.min.js
140 ms
ddc.min.js
246 ms
ddc-core-js-polyfills.min.js
218 ms
react.production.min.js
169 ms
react-dom.production.min.js
186 ms
prop-types.min.js
289 ms
react-bootstrap.min.js
235 ms
redux.min.js
234 ms
react-redux.min.js
259 ms
redux-thunk.min.js
399 ms
html-react-parser.min.js
259 ms
umd.js
267 ms
hysterics.js
274 ms
lib.js
274 ms
loader.js
281 ms
widget.min.js
436 ms
data-layer-helper.min.js
302 ms
widget.min.js
297 ms
widget.min.js
303 ms
widget.min.js
313 ms
bundle.e7783622f3c13f0875a2ba8dd40a35d0.js
316 ms
bundle.c07071d2364841eaacf76e4696ad22f8.js
315 ms
pubsub.min.js
328 ms
eo.min.js
330 ms
userProfileController.min.js
330 ms
widget.min.js
348 ms
jquery.cycle2.min.js
334 ms
jquery.cycle2.swipe.min.js
657 ms
widget.min.js
327 ms
widget.min.js
483 ms
bundle.e3f893e71af8c235fec68934a849c8f1.js
665 ms
widget.min.js
260 ms
bundle.7d344c330c1cba974d4cfe37756b2804.js
251 ms
jquery.inview.min.js
259 ms
widget.min.js
269 ms
component.min.js
404 ms
jquery.timeago.min.js
370 ms
widget-new.min.js
271 ms
widget-tracking.min.js
357 ms
widget.min.js
571 ms
dropdown.min.js
443 ms
widget.min.js
393 ms
widget.min.js
423 ms
widget.min.js
400 ms
addFormEventId.js
633 ms
variation.min.js
425 ms
variation.js
769 ms
web-vitals.min.js
436 ms
index.min.js
438 ms
ddc.jquery-ui.dialog.min.js
468 ms
component.min.js
435 ms
42F34-WHQN8-HU2C7-SR6YY-TT9RR
68 ms
dc4cdc3e38e3918fdaa095e2c73594a6x.jpg
170 ms
183x125.png
409 ms
ad-choices-logo-11x12.png
392 ms
4d396cfd1905caa762ed5ad965d965b5x.jpg
240 ms
75e62a900f58f941e0af6ac5279499f7x.jpg
700 ms
component.min.js
458 ms
cookie-messaging.html
192 ms
font.3b9be2f3c7ec2199a7e67f3c8f7a8042.woff
417 ms
ddc-white.png
645 ms
analytics.js
118 ms
loader.js
118 ms
122 ms
config.json
72 ms
call-tracking_7.js
4 ms
29 ms
component.css
160 ms
data.htm
156 ms
bootstrap.js
168 ms
activityi;src=8497484;type=conve0;cat=volks00k;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=$%7BGDPR%7D;gdpr_consent=$%7BGDPR_CONSENT_755%7D;ord=1;num=110401.2590367347
60 ms
bundle.5530a04f3af1841ae30de584b168d92e.js
42 ms
bundle.e52ba8c8c27c4383b9fd40b8e7166138.js
29 ms
validator.min.js
121 ms
src=8497484;type=conve0;cat=volks00k;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=$%7BGDPR%7D;gdpr_consent=$%7BGDPR_CONSENT_755%7D;ord=1;num=110401.2590367347
146 ms
bundle.9a5bb9b2cffad315c7496431165839e0.js
18 ms
bundle.b64200ac0622275e4988ea452c45ac9f.js
58 ms
vwalhambra.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
[role]s are not contained by their required parent element
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
Heading elements are not in a sequentially-descending order
vwalhambra.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
vwalhambra.com SEO score
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vwalhambra.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 Vwalhambra.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.
vwalhambra.com
Open Graph description is not detected on the main page of Vwalhambra. 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: