3.2 sec in total
519 ms
2.3 sec
329 ms
Visit nobullauto.ca now to see the best up-to-date No Bull Auto content and also check out these interesting facts you probably never knew about nobullauto.ca
No Bull Auto in Dartmouth has Used Cars and SUVs for sale. Call (902) 464-4668 for Dartmouth Used Cars Specials and Promotions.
Visit nobullauto.caWe analyzed Nobullauto.ca page load time and found that the first response time was 519 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
nobullauto.ca performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value6.7 s
7/100
25%
Value5.7 s
51/100
10%
Value220 ms
87/100
30%
Value0.211
59/100
15%
Value11.3 s
19/100
10%
519 ms
31 ms
48 ms
52 ms
48 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Nobullauto.ca, 64% (73 requests) were made to Static.dealer.com and 16% (18 requests) were made to Pictures.dealer.com. The less responsive or slowest element that took the longest time to load (963 ms) relates to the external source Pictures.dealer.com.
Page size can be reduced by 633.3 kB (49%)
1.3 MB
663.4 kB
In fact, the total size of Nobullauto.ca main page is 1.3 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 575.9 kB which makes up the majority of the site volume.
Potential reduce by 61.7 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 61.7 kB or 81% of the original size.
Potential reduce by 35.4 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. No Bull Auto images are well optimized though.
Potential reduce by 389.3 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 389.3 kB or 68% of the original size.
Potential reduce by 146.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. Nobullauto.ca needs all CSS files to be minified and compressed as it can save up to 146.9 kB or 84% of the original size.
Number of requests can be reduced by 40 (37%)
107
67
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of No Bull Auto. 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 8 to 1 for CSS and as a result speed up the page load time.
www.nobullauto.ca
519 ms
combo.css
31 ms
widget.css
48 ms
variation.css
52 ms
blue_white.css
48 ms
custom.css
11 ms
newrelic.js
47 ms
modernizr-2.6.2.min.js
46 ms
pxa.min.js
27 ms
pixall.min.js
24 ms
ddc.jquery.min.js
93 ms
ddc.min.js
75 ms
widget.min.js
76 ms
jquery.cycle2.min.js
76 ms
jquery.cycle2.swipe.min.js
74 ms
widget.min.js
77 ms
widget.min.js
81 ms
widget.min.js
80 ms
widget.min.js
81 ms
widget.min.js
82 ms
tracker.min.js
81 ms
widget.min.js
82 ms
widget.min.js
82 ms
widget.min.js
87 ms
data-layer-helper.min.js
85 ms
jquery-ui.css
39 ms
default.css
39 ms
iframe.php
207 ms
6bdb33b0a62df20962332e4c343401ccx.jpg
398 ms
blank.gif
207 ms
analytics.js
164 ms
gtm.js
175 ms
gtm.js
188 ms
clear.gif
258 ms
e85fa7170a0d02b701e1153aac2a714b.jpg
330 ms
e86670c20a0d02b701e1153aac931ecb.jpg
298 ms
389a43120a0e0acc2af68618822865b6.jpg
294 ms
db2d23600a0e0acc2e111af6ef768d60.jpg
323 ms
c395a2cbe791d85672b0747abe2fa829x.jpg
306 ms
site-bg.png
72 ms
main-top-bg.jpg
79 ms
117x80.png
71 ms
search-bg-right.png
75 ms
search-bg.png
72 ms
freeform-bg.png
76 ms
btn-xsmall.png
76 ms
btn-xsmall-right.png
79 ms
nav-bg-left.png
77 ms
nav-bg.png
80 ms
nav-divider.png
165 ms
dropdown-bottom.png
161 ms
dropdown-top.png
163 ms
dropdown-repeat.png
161 ms
page-top.png
162 ms
main-bottom-bg.png
163 ms
page-center.png
164 ms
widget-top-gradient.png
167 ms
widget-top-right-gradient.png
166 ms
btn-small.png
166 ms
btn-small-right.png
165 ms
prev-btn.png
171 ms
play-pause-btn.png
169 ms
next-btn.png
170 ms
faux-buttonblock.png
169 ms
custom-link-special.jpg
169 ms
custom-link-service.jpg
169 ms
custom-link-showroom.jpg
229 ms
custom-link-carfinder.jpg
228 ms
type-3-tl.png
227 ms
type-3-tr.png
227 ms
type-3-l.png
225 ms
type-3-r.png
225 ms
link-arrow.png
233 ms
type-3-bl.png
234 ms
type-3-br.png
231 ms
pixel
206 ms
pixel
233 ms
page-bottom.png
175 ms
footer-bg-repeat.png
174 ms
footer-bg.png
182 ms
footer-nav-divider.png
181 ms
dss-logo-black.gif
181 ms
collect
122 ms
collect
90 ms
jcarousel.min.js
77 ms
jquery.cycle.min.js
76 ms
ui.min.js
67 ms
validator.min.js
73 ms
jquery.unveil.min.js
65 ms
collect
21 ms
pixel
31 ms
collect
104 ms
pixel.php
103 ms
pixel
21 ms
print.css
23 ms
pixel.php
61 ms
9413c66e0a0e0acc2e111af69a359bd5.jpg
341 ms
9411bd210a0e0acc2e111af6389e5253.jpg
338 ms
944deed80a0e0acc2e111af6e9074de9.jpg
467 ms
9a19ed5d0a0e0acc2e111af61ac75b1b.jpg
368 ms
2376dbfd0a0e0acc2af68618c23f3116.jpg
565 ms
5245d8ae0a0e0acc2af68618f96efe4c.jpg
356 ms
237e89940a0e0acc2af686188519dd98.jpg
832 ms
5233d8cd0a0e0acc2af68618b80cc2cd.jpg
615 ms
9817ebfb0a0e0acc2af686183cc16863.jpg
636 ms
a2584fba0a0e0acc0800654526fa9fd7.jpg
804 ms
98164a5b0a0e0acc2af68618b726b4f9.jpg
730 ms
970d85b60a0e0acc2af68618d9990245.jpg
963 ms
ga-audiences
34 ms
carousel-prev-arrow.png
15 ms
fbdrop.php
41 ms
carousel-next-arrow.png
33 ms
nr-632.min.js
22 ms
slideshow-paging.png
15 ms
nobullauto.ca 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.
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
nobullauto.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
nobullauto.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 Nobullauto.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 Nobullauto.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.
nobullauto.ca
Open Graph description is not detected on the main page of No Bull Auto. 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: