976 ms in total
13 ms
770 ms
193 ms
Visit imperialhighline.com now to see the best up-to-date Imperial Highline content and also check out these interesting facts you probably never knew about imperialhighline.com
Serving DC Maryland & Virginia, Virginia (VA), Imperial Highline is the place to purchase your next vehicle. View photos and details of our entire new and used inventory.
Visit imperialhighline.comWe analyzed Imperialhighline.com page load time and found that the first response time was 13 ms and then it took 963 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
imperialhighline.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value10.0 s
0/100
25%
Value7.1 s
30/100
10%
Value2,960 ms
3/100
30%
Value0.979
2/100
15%
Value18.4 s
3/100
10%
13 ms
180 ms
87 ms
113 ms
118 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Imperialhighline.com, 70% (45 requests) were made to Images.ebizautos.media and 6% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (345 ms) relates to the external source Images.ebizautos.media.
Page size can be reduced by 172.6 kB (10%)
1.7 MB
1.6 MB
In fact, the total size of Imperialhighline.com main page is 1.7 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. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 76.2 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 12.4 kB, which is 14% 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 76.2 kB or 83% of the original size.
Potential reduce by 0 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. Imperial Highline images are well optimized though.
Potential reduce by 93.7 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 93.7 kB or 26% of the original size.
Potential reduce by 2.7 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. Imperialhighline.com has all CSS files already compressed.
Number of requests can be reduced by 29 (55%)
53
24
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Imperial Highline. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
imperialhighline.com
13 ms
www.imperialhighline.com
180 ms
foundation.css
87 ms
font-icons.css
113 ms
fonts.css
118 ms
foundation-theme.css
132 ms
responsive.css
127 ms
custom.css
127 ms
jquery.min.js
122 ms
jquery.cookie.min.js
143 ms
global.js
143 ms
gallery.js
160 ms
115108.js
202 ms
887171.js
60 ms
js
80 ms
vehicles_info_manager.js
160 ms
mapbox-gl.js
36 ms
mapbox-gl.css
34 ms
functions-mapbox.js
157 ms
iframeResizer.min.js
195 ms
plugins-main.js
345 ms
functions-main.js
226 ms
jquery.validate.js
226 ms
jquery-cycle2.js
227 ms
owl-plugins.js
344 ms
functions-home-owl-carousel.js
344 ms
css
28 ms
analytics.js
237 ms
logo.png
228 ms
logo@2x.png
228 ms
logo@2x-mobile.png
228 ms
64445_12074.jpg
229 ms
63816_12074.jpg
228 ms
63817_12074.jpg
227 ms
64444_12074.jpg
247 ms
64443_12074.jpg
247 ms
64442_12074.jpg
242 ms
63815_12074.jpg
241 ms
63814_12074.jpg
241 ms
63813_12074.jpg
247 ms
63818_12074.jpg
268 ms
99572_12074.jpg
270 ms
99571_12074.jpg
268 ms
99570_12074.jpg
272 ms
99569_12074.jpg
279 ms
99568_12074.jpg
273 ms
99567_12074.jpg
290 ms
sp.gif
317 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
222 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
235 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
254 ms
c8cf4211-2949-4685-9745-465509fe49e7
165 ms
gtm.js
53 ms
eas.js
164 ms
x-twitter.woff
114 ms
font-icons-4.woff
81 ms
font-icons-3.woff
86 ms
font-icons-2.woff
114 ms
font-icons.woff
115 ms
lined-icons.woff
115 ms
collect
47 ms
collect
52 ms
js
51 ms
js
46 ms
imperialhighline.com accessibility score
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
imperialhighline.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
Missing source maps for large first-party JavaScript
imperialhighline.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Imperialhighline.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 Imperialhighline.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.
imperialhighline.com
Open Graph description is not detected on the main page of Imperial Highline. 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: