Tools & Wizards About Us
driving.unhaggle.com screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

driving.unhaggle.com

Best New Car Prices in Canada. Free Dealer Invoice Price. | Unhaggle

Page Load Speed

1.1 sec in total

First Response

107 ms

Resources Loaded

803 ms

Page Rendered

178 ms

driving.unhaggle.com screenshot

About Website

Welcome to driving.unhaggle.com homepage info - get ready to check Driving Unhaggle best content for Canada right away, or after learning these important things about driving.unhaggle.com

Unhaggle helps you buy new cars in Canada. We get car dealerships to compete, provide dealer invoice prices, and show you the best deals. No more haggling.

Visit driving.unhaggle.com

Key Findings

We analyzed Driving.unhaggle.com page load time and found that the first response time was 107 ms and then it took 981 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

driving.unhaggle.com performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value4.0 s

88/100

10%

Network Requests Diagram

driving.unhaggle.com

107 ms

unhaggle.com

177 ms

css

31 ms

output.33b76c2aab7b.css

16 ms

output.e27e6bf22775.css

55 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Driving.unhaggle.com, 72% (41 requests) were made to Unhaggle.com and 4% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (213 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 759 B (0%)

Content Size

376.0 kB

After Optimization

375.2 kB

  • Images
  • JavaScript
  • CSS

In fact, the total size of Driving.unhaggle.com main page is 376.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Javascripts take 192.6 kB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Image Optimization

-0%

Potential reduce by 1 B

  • Original 147.8 kB
  • After minification 147.8 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. Driving Unhaggle images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 699 B

  • Original 192.6 kB
  • After minification 192.6 kB
  • After compression 191.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 67 B

  • Original 35.6 kB
  • After minification 35.6 kB
  • After compression 35.5 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. Driving.unhaggle.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 44 (85%)

Requests Now

52

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Driving Unhaggle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

driving.unhaggle.com

driving.unhaggle.com

107 ms

unhaggle.com

unhaggle.com

177 ms

css

css

31 ms

output.33b76c2aab7b.css

output.33b76c2aab7b.css

16 ms

output.e27e6bf22775.css

output.e27e6bf22775.css

55 ms

output.ddede6c2405e.css

output.ddede6c2405e.css

38 ms

output.cb095e0b913f.css

output.cb095e0b913f.css

32 ms

output.c68a8a86bbed.css

output.c68a8a86bbed.css

35 ms

output.e4c5a5eaec62.css

output.e4c5a5eaec62.css

61 ms

output.10c45fe83bc4.css

output.10c45fe83bc4.css

36 ms

output.9870bdceef91.css

output.9870bdceef91.css

48 ms

output.3fedfb277101.css

output.3fedfb277101.css

58 ms

output.27ad1144a03a.css

output.27ad1144a03a.css

52 ms

output.2ee4c75c2c78.css

output.2ee4c75c2c78.css

53 ms

107 ms

output.dccb4e1f0898.js

output.dccb4e1f0898.js

68 ms

output.ac4947d5233e.js

output.ac4947d5233e.js

69 ms

output.61dccba475c8.js

output.61dccba475c8.js

70 ms

output.fbb909bf0e08.js

output.fbb909bf0e08.js

77 ms

output.ba7b357c9935.js

output.ba7b357c9935.js

88 ms

output.816ee50c330f.js

output.816ee50c330f.js

88 ms

output.b3d73eb7917b.js

output.b3d73eb7917b.js

97 ms

output.aeed7b31176d.js

output.aeed7b31176d.js

88 ms

output.3297e4b1f516.js

output.3297e4b1f516.js

94 ms

output.392ea3ac04a2.js

output.392ea3ac04a2.js

103 ms

output.aed90d3c454c.js

output.aed90d3c454c.js

121 ms

output.1b872bd5416c.js

output.1b872bd5416c.js

124 ms

output.56a82849f843.js

output.56a82849f843.js

123 ms

output.743eac801cf1.js

output.743eac801cf1.js

123 ms

output.d9a25126b70f.js

output.d9a25126b70f.js

125 ms

output.da93bc0be76a.js

output.da93bc0be76a.js

145 ms

lcm.js

lcm.js

126 ms

email-decode.min.js

email-decode.min.js

122 ms

output.dcd39b94d56d.js

output.dcd39b94d56d.js

171 ms

conversion.js

conversion.js

33 ms

104 ms

gtm.js

gtm.js

213 ms

dc.js

dc.js

105 ms

widgets.js

widgets.js

116 ms

css-window-fadeout-bkg.png

css-window-fadeout-bkg.png

87 ms

main-sprites.png

main-sprites.png

113 ms

bg-nav-divider.png

bg-nav-divider.png

88 ms

homepage-sprites.png

homepage-sprites.png

112 ms

bg-stats-divider.png

bg-stats-divider.png

87 ms

bg-brand-arrows.png

bg-brand-arrows.png

114 ms

3546.js

3546.js

158 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

132 ms

74 ms

all.js

all.js

45 ms

select2.png

select2.png

27 ms

unhaggle_modal.js

unhaggle_modal.js

26 ms

__utm.gif

__utm.gif

14 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

20 ms

54 ms

all.js

all.js

18 ms

settings

settings

81 ms

28 ms

Accessibility Review

driving.unhaggle.com accessibility score

88

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Links do not have a discernible name

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

driving.unhaggle.com SEO score

87

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Driving.unhaggle.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Driving.unhaggle.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.

Social Sharing Optimization

driving.unhaggle.com

Open Graph description is not detected on the main page of Driving Unhaggle. 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: