5.1 sec in total
257 ms
4.2 sec
646 ms
Click here to check amazing Alexandria Vw content for United States. Otherwise, check out these important facts you probably never knew about alexandriavw.com
Family owned and operated, Alexandria Volkswagen has been serving high-quality vehicles for the past 40 years. Visit us today from Washingon, D.C., Springfield, or Arlington!
Visit alexandriavw.comWe analyzed Alexandriavw.com page load time and found that the first response time was 257 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.
alexandriavw.com performance score
name
value
score
weighting
Value2.5 s
69/100
10%
Value14.3 s
0/100
25%
Value20.3 s
0/100
10%
Value8,220 ms
0/100
30%
Value0.647
9/100
15%
Value44.2 s
0/100
10%
257 ms
596 ms
40 ms
34 ms
105 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 10% of them (14 requests) were addressed to the original Alexandriavw.com, 37% (54 requests) were made to Assets.cobaltnitra.com and 17% (25 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source I.ytimg.com.
Page size can be reduced by 1.3 MB (51%)
2.5 MB
1.2 MB
In fact, the total size of Alexandriavw.com main page is 2.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 939.6 kB which makes up the majority of the site volume.
Potential reduce by 223.8 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 33.3 kB, which is 13% 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 223.8 kB or 85% of the original size.
Potential reduce by 91.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. Alexandria Vw images are well optimized though.
Potential reduce by 627.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 627.2 kB or 67% of the original size.
Potential reduce by 326.9 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. Alexandriavw.com needs all CSS files to be minified and compressed as it can save up to 326.9 kB or 83% of the original size.
Number of requests can be reduced by 68 (51%)
133
65
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Alexandria Vw. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
alexandriavw.com
257 ms
www.alexandriavw.com
596 ms
bundle.css
40 ms
bundle.js
34 ms
mobilePromo_seo.js
105 ms
422fbc807d1f10058e8310145edef087.js
26 ms
422c13007d1f10058aa820145edef087.css
26 ms
4229ec387d1f10058e8310145edef087.js
24 ms
422fb0c87d1f10058ec320145efa6b30.css
23 ms
none.gen.css
30 ms
legacy.gen.css
30 ms
none.gen.css
30 ms
vw.gen.css
32 ms
none.gen.css
34 ms
VWheadlineot.gen.css
34 ms
none.gen.css
80 ms
PopIn.js
236 ms
vcu.js
91 ms
07349c.js
176 ms
promotion.js
176 ms
flexPixelTagProvider_Cobalt.js
177 ms
player_api
90 ms
EventController.js
102 ms
bundle.js
86 ms
pixeltag.js
87 ms
7384f8b874e11005803510145edef087.js
69 ms
74789fb874e11005803510145edef087.js
155 ms
73c5787074e11005803510145edef087.js
160 ms
ga.js
74 ms
getagentstatusimage.aspx
72 ms
35x35_socialIcon2.png
523 ms
35x35_socialIcon3.png
534 ms
35x35_socialIcon1.png
534 ms
loading.gif
88 ms
d6127f8873dc10058b8e20145efa6b30.png
88 ms
loading.gif
89 ms
widget_loader.gif
88 ms
d5bde74873dc10058b8e20145efa6b30.png
737 ms
__utm.gif
21 ms
vwheadlineot-book-webfont.woff
35 ms
fontawesome-webfont.woff
13 ms
fontawesome-webfont.woff
449 ms
vwheadlineot-semibold-webfont.woff
14 ms
PopInGenerator.aspx
378 ms
session.js
365 ms
JavascriptInsert.js
366 ms
www-widgetapi.js
350 ms
sd.js
336 ms
11496464176x250.jpg
269 ms
searchInventory.do
262 ms
getSignedUrl.do
273 ms
edw-partner-edcc9821.js
192 ms
noTout.png
134 ms
940x502_aboutUs.jpg
334 ms
12150532059x250.jpg
133 ms
10793_cc0640_032_8E8Ex250.jpg
116 ms
12069424014x250.jpg
110 ms
12467275262x250.jpg
117 ms
10599_cc0640_032_Z2Z2x250.jpg
117 ms
10818_cc0640_032_2T2Tx250.jpg
106 ms
12153665246x250.jpg
131 ms
12742893260x250.jpg
131 ms
12150533591x250.jpg
118 ms
e962c198877c10058ca9005056924175.png
117 ms
e402930038201005804e00146efa6b30.png
100 ms
loading.gif
102 ms
dbf7aac07d9d100587d020145edef087.jpg
98 ms
dbf9e5107d9d1005887910145efa6b30.jpg
104 ms
dbfac3b87d9d1005887910145efa6b30.jpg
100 ms
dbfaa4787d9d100587d020145edef087.jpg
102 ms
d9b098687d241005853d10145efa6b30.png
101 ms
45ce3ee07a4d10058ea300146edef087.jpg
104 ms
c0e593e8867910058ca9005056924175.jpg
173 ms
cpo.jpg
104 ms
sx.jpg
106 ms
service.jpg
105 ms
cfm.jpg
127 ms
cpo2.jpg
105 ms
service2.jpg
110 ms
cpo3.jpg
110 ms
service3.jpg
110 ms
label.gif
116 ms
BlackInstantMessageButton.gif
116 ms
fontawesome-webfont.ttf
168 ms
8282374b-166d-44f4-a62e-c57625815ef7.rolloveragent365775.jpg
89 ms
button3.jpg
88 ms
8282374b-166d-44f4-a62e-c57625815ef7.rolloveragent365775.jpg
172 ms
edw_partner.cgi
65 ms
fontawesome-webfont.svg
308 ms
websites.gif
255 ms
none.gen.css
173 ms
searchInventory.do
310 ms
all.js
179 ms
videos
215 ms
site.xml
339 ms
f78068b07aee1005815e10145edef087x1300.jpg
72 ms
10fa4cc0893b1005896600505692530ex1300.jpg
73 ms
facebook.png
60 ms
twitter.png
60 ms
youtube.png
58 ms
instagram.png
58 ms
1x1.gif
433 ms
1x1.gif
403 ms
1x1.gif
427 ms
w.gif
432 ms
activityi;src=2617051;type=tieri875;cat=hmpge;u1=409416;ord=1;num=2322990929242.2236
111 ms
activity;src=1033942;type=vlkswgn;cat=tieriii;ord=1;num=899796964
314 ms
activityi;src=1033942;type=vw2013;cat=t2vwdpv;ord=9549721234943.717
313 ms
431 ms
xd_arbiter.php
315 ms
xd_arbiter.php
473 ms
mq0.jpg
1339 ms
mqdefault.jpg
308 ms
like_box.php
269 ms
3B0ArDU4qFI.css
231 ms
WEFvPNv7jzx.css
273 ms
SjGvcmqWmCE.css
296 ms
1r99AxojE5d.css
374 ms
_Je2P04Pffa.css
361 ms
XCdv7aD40Gm.js
404 ms
lnwXDK64af8.js
429 ms
mn6tHWuLI-Y.js
318 ms
x8BMxYCqTb9.js
318 ms
QKy94bWvcbp.js
395 ms
5paioeCYCa7.js
393 ms
wRXOQ26LQ1k.js
456 ms
UMeIUxuSxxa.js
537 ms
50Trs1RKgUY.js
453 ms
530978_10150769142465605_2110403779_n.jpg
199 ms
safe_image.php
218 ms
1233608_10151838521315605_1955224770_n.jpg
244 ms
12809732_10153912068735605_6533070906331298459_n.jpg
303 ms
12734033_10153820780930605_7026354279759293908_n.jpg
396 ms
12494977_10153765631150605_8348557970653076148_n.jpg
354 ms
wL6VQj7Ab77.png
109 ms
s7jcwEQH7Sx.png
109 ms
mbF8ssTVP_5.png
107 ms
Fe6g47SXw-8.png
107 ms
L5AOQ9vzKfo.png
107 ms
oULnqcel5Nm.png
106 ms
q2ibvFgTxmh.png
116 ms
A2JLtDOGyCJ.png
113 ms
Db1xvLoJ2np.png
115 ms
Fy3hs8lKW0M.png
112 ms
VXcANLwwL5J.js
44 ms
alexandriavw.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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
alexandriavw.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
Registers an unload listener
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
alexandriavw.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
EN
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alexandriavw.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 Alexandriavw.com main page’s claimed encoding is . 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.
alexandriavw.com
Open Graph description is not detected on the main page of Alexandria Vw. 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: