3.1 sec in total
701 ms
2.1 sec
296 ms
Visit drivehg.ca now to see the best up-to-date Drivehg content and also check out these interesting facts you probably never knew about drivehg.ca
The Humberview Group offers more than 5,000 new and pre-owned vehicles at our 20 stores, representing 18 automotive brands with 1 simple promise: Serving you better, each and every day. Don’t settle f...
Visit drivehg.caWe analyzed Drivehg.ca page load time and found that the first response time was 701 ms and then it took 2.4 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.
drivehg.ca performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value9.4 s
0/100
25%
Value5.9 s
48/100
10%
Value1,470 ms
14/100
30%
Value0.726
6/100
15%
Value12.3 s
15/100
10%
701 ms
17 ms
27 ms
27 ms
33 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Drivehg.ca, 24% (28 requests) were made to Pictures.dealer.com and 5% (6 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (737 ms) relates to the external source Tradercreative.ca.
Page size can be reduced by 909.9 kB (49%)
1.9 MB
943.4 kB
In fact, the total size of Drivehg.ca main page is 1.9 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. 60% of websites need less resources to load. Javascripts take 767.4 kB which makes up the majority of the site volume.
Potential reduce by 107.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. 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 107.8 kB or 82% of the original size.
Potential reduce by 7.6 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. Drivehg images are well optimized though.
Potential reduce by 520.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 520.7 kB or 68% of the original size.
Potential reduce by 273.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. Drivehg.ca needs all CSS files to be minified and compressed as it can save up to 273.9 kB or 87% of the original size.
Number of requests can be reduced by 55 (50%)
110
55
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Drivehg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.humberviewgroup.com
701 ms
default.css
17 ms
widget.css
27 ms
widget.css
27 ms
variation.css
33 ms
green_white.css
26 ms
print.css
6 ms
ontario.css
5 ms
custom.css
414 ms
newrelic.js
6 ms
modernizr-2.6.2.min.js
5 ms
pxa.min.js
10 ms
pixall.min.js
11 ms
conversion.js
15 ms
ddc.jquery.min.js
39 ms
ddc.min.js
13 ms
jquery.cycle2.min.js
83 ms
jquery.cycle2.swipe.min.js
10 ms
widget.min.js
10 ms
widget.min.js
13 ms
widget.min.js
13 ms
widget.min.js
12 ms
widget.min.js
20 ms
widget.min.js
15 ms
widget.min.js
12 ms
widget.min.js
13 ms
tracker.min.js
14 ms
widget.min.js
27 ms
widget.min.js
16 ms
widget.min.js
27 ms
data-layer-helper.min.js
19 ms
jQueryUi.js
737 ms
backgroundPos.js
286 ms
iframe.php
105 ms
183x125.png
29 ms
e562a1967e45ec2a836263cd3bb5a93cx.jpg
121 ms
d6a6b149d5c67a72e67eb2904fdc3831x.jpg
97 ms
4d243b176910ff1243a6f19af8d99a26x.jpg
96 ms
75a7cae74b6d0e5881464b8d5fe0b3d0x.jpg
97 ms
1d52ac85d6730d12dc480c8a60b73234x.jpg
96 ms
df6b41908f9d139bbbe16389eaba1852x.jpg
106 ms
69a3b509a7c8981ea0fdc616246c6c75x.jpg
125 ms
678bda3aa6ed0d77474bce9042190e53x.jpg
119 ms
d4323a60003f5957133c1567d5eb5bb2x.jpg
118 ms
7dadc74f573f2bab50b52045b8bc5916x.jpg
106 ms
de2846300909413d1653a92a9b510c6ex.jpg
178 ms
1d381ffcfed17a9ea04328000defbe9fx.jpg
125 ms
c777663298b1c1c24078dcec98df103cx.jpg
179 ms
113132566880c619eb8248682fe9bb68x.jpg
178 ms
1a66a379e32f2b62e4b53ae77950e0c9x.jpg
176 ms
e9c41e141b2cd623f5b884d73b16ade3x.jpg
178 ms
06266cf7512903bf4df6d990cac758f8x.jpg
200 ms
183x125.png
94 ms
183x125.png
94 ms
183x125.png
92 ms
183x125.png
93 ms
183x125.png
93 ms
183x125.png
94 ms
183x125.png
121 ms
183x125.png
182 ms
183x125.png
274 ms
183x125.png
97 ms
183x125.png
102 ms
183x125.png
102 ms
183x125.png
112 ms
183x125.png
120 ms
183x125.png
121 ms
183x125.png
274 ms
183x125.png
226 ms
183x125.png
179 ms
183x125.png
180 ms
183x125.png
224 ms
183x125.png
226 ms
183x125.png
224 ms
gtm.js
116 ms
79336a3bf49b11d2eea56641d2325061x.jpg
178 ms
b15f60ac2e4322efd4bfa643d6c3e790x.jpg
208 ms
5d868839cd077a9cc35db09512744a78x.jpg
244 ms
d4f6e56f6ba0862cdf50091f8e8e15aax.jpg
207 ms
0231e11286b7f21f3403d1c1cfa939dex.jpg
242 ms
7ebabdf96681d33f6921b53f4f62f77cx.jpg
243 ms
8ab7c9db02ff23a32f17f143f0d61c8dx.jpg
254 ms
a6b7113725778e12499a0b94ae06660fx.jpg
253 ms
noise-repeat.png
241 ms
dss-logo-black.gif
241 ms
analytics.js
66 ms
156 ms
gtm.js
140 ms
gtm.js
154 ms
pixel
224 ms
collect
71 ms
collect
175 ms
collect
73 ms
collect
73 ms
collect
179 ms
collect
180 ms
122 ms
collect
78 ms
pixel
16 ms
apn.php
65 ms
pixel.php
63 ms
fbdrop.php
56 ms
pixel.php
75 ms
ga-audiences
16 ms
collect
32 ms
clear.gif
163 ms
d304f0328839d08356470f94e8db6853x.jpg
8 ms
b67c51eeb0d9c246e086e4f79ad37ab7x.jpg
8 ms
collect
12 ms
jquery.cycle.min.js
45 ms
ui.min.js
5 ms
validator.min.js
9 ms
nr-632.min.js
19 ms
e48c803b91dcfa88a39200867f3c722ex.jpg
8 ms
82e1cf9367
45 ms
drivehg.ca accessibility score
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
Links do not have a discernible name
drivehg.ca 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
drivehg.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Drivehg.ca 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 Drivehg.ca 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.
drivehg.ca
Open Graph description is not detected on the main page of Drivehg. 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: