Tools & Wizards About Us

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

imperialhighline.com

Imperial Highline - Serving DC Maryland & Virginia, VA

Page Load Speed

976 ms in total

First Response

13 ms

Resources Loaded

770 ms

Page Rendered

193 ms

About Website

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

Key Findings

We 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.

Performance Metrics

imperialhighline.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value7.1 s

30/100

10%

TBT (Total Blocking Time)

Value2,960 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.979

2/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

imperialhighline.com

13 ms

www.imperialhighline.com

180 ms

foundation.css

87 ms

font-icons.css

113 ms

fonts.css

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 Optimization Overview & Recommendations

Page size can be reduced by 172.6 kB (10%)

Content Size

1.7 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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.

HTML Optimization

-83%

Potential reduce by 76.2 kB

  • Original 91.5 kB
  • After minification 79.1 kB
  • After compression 15.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. 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.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.2 MB
  • After minification 1.2 MB

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.

JavaScript Optimization

-26%

Potential reduce by 93.7 kB

  • Original 355.6 kB
  • After minification 355.6 kB
  • After compression 262.0 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.

CSS Optimization

-3%

Potential reduce by 2.7 kB

  • Original 81.4 kB
  • After minification 81.4 kB
  • After compression 78.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.

Requests Breakdown

Number of requests can be reduced by 29 (55%)

Requests Now

53

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

Accessibility Review

imperialhighline.com accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best Practices

imperialhighline.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

imperialhighline.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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

Social Sharing Optimization

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: