8 sec in total
618 ms
6.3 sec
1.1 sec
Visit driven.co.nz now to see the best up-to-date Driven content for New Zealand and also check out these interesting facts you probably never knew about driven.co.nz
Get in-depth vehicle reviews, latest motoring news, car comparisons, and ask an expert. Find your next car.
Visit driven.co.nzWe analyzed Driven.co.nz page load time and found that the first response time was 618 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
driven.co.nz performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value16.2 s
0/100
25%
Value14.5 s
1/100
10%
Value6,760 ms
0/100
30%
Value0.078
95/100
15%
Value27.7 s
0/100
10%
618 ms
1825 ms
1612 ms
29 ms
585 ms
Our browser made a total of 152 requests to load all elements on the main page. We found that 51% of them (77 requests) were addressed to the original Driven.co.nz, 8% (12 requests) were made to S0.2mdn.net and 5% (8 requests) were made to Images.outbrain.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Driven.co.nz.
Page size can be reduced by 929.6 kB (50%)
1.9 MB
932.9 kB
In fact, the total size of Driven.co.nz 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. 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. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 230.1 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 230.1 kB or 78% of the original size.
Potential reduce by 15.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. Driven images are well optimized though.
Potential reduce by 683.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 683.9 kB or 51% of the original size.
Number of requests can be reduced by 46 (32%)
145
99
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Driven. 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 as a result speed up the page load time.
driven.co.nz
618 ms
www.driven.co.nz
1825 ms
drivenstyles
1612 ms
webfont.js
29 ms
modernizr-2.8.3.min.js
585 ms
addthis_widget.js
19 ms
jquery.min.js
46 ms
aimatch_ad_server.js
383 ms
banners.js
392 ms
outbrain.js
58 ms
584 ms
vendor
1560 ms
driven
1358 ms
articles
227 ms
conversion.js
14 ms
bg-pattern-diagonal.png
208 ms
gtm.js
52 ms
logo-driven@2x.png
202 ms
logo-driven-rev.png
198 ms
drivenedm_300x50.gif
256 ms
listenLiveButton.jpg
257 ms
icon-body-convertible.png
354 ms
icon-body-coupe.png
366 ms
icon-body-hatchback.png
381 ms
icon-body-sedan.png
428 ms
icon-body-stationwagon.png
469 ms
icon-body-4wdsuv.png
788 ms
icon-body-ute.png
790 ms
icon-body-van.png
803 ms
f1516_highlight_lg_limited.jpg
803 ms
gymkhana-8-pov.jpg
804 ms
gymkhana-8-pov.jpg
799 ms
2902splporsche918andgt470.jpg
800 ms
2902splporsche918andgt470.jpg
800 ms
conor-mcgregor-lambo-driven.jpg
1070 ms
conor-mcgregor-lambo-driven.jpg
1071 ms
2902splslcover.jpg
1063 ms
2902splslcover.jpg
1071 ms
2202spljaguaretype10.jpg
1069 ms
2202spljaguaretype10.jpg
1174 ms
2402spldom.jpg
1174 ms
2402spldom.jpg
1179 ms
hrv-news_2.jpg
1175 ms
hrv-news_2.jpg
1204 ms
low-res-peugeot-308-gt-and-gti-by-peugeot-sport-260.jpg
1206 ms
low-res-peugeot-308-gt-and-gti-by-peugeot-sport-260.jpg
1449 ms
mb-trophy-715x230.gif
1450 ms
mb-trophy-715x230.gif
1449 ms
imagestream.jpg
1449 ms
imagestream.jpg
1448 ms
icomoon.ttf
1369 ms
analytics.js
54 ms
v60.js
139 ms
cc_af.js
137 ms
fbevents.js
140 ms
collect
47 ms
collect
94 ms
porsche-festival-record-of-402-porsche-cars-on-track-hampton-downs-nz-b-1.jpg
1396 ms
porsche-festival-record-of-402-porsche-cars-on-track-hampton-downs-nz-b-1.jpg
1388 ms
558c2a6e20c56.jpg
1393 ms
62 ms
storageframe.html
42 ms
558c2a6e20c56.jpg
1353 ms
ga-audiences
37 ms
m
24 ms
suzuki.jpg
1290 ms
suzuki.jpg
1468 ms
cx-9-production.jpg
1455 ms
cx-9-production.jpg
1410 ms
ja_uar_svr_news_device-desktop_940x500_tcm76-239323_desktop_940x500.jpg
1372 ms
239 ms
260 ms
300lo.json
41 ms
ja_uar_svr_news_device-desktop_940x500_tcm76-239323_desktop_940x500.jpg
1058 ms
bugatti.jpg
1239 ms
get
165 ms
bugatti.jpg
1237 ms
sh.7c7179124ea24ac6ba46caac.html
51 ms
viewid=69065936725
281 ms
aprxgh1.jpg
1232 ms
aprxgh1.jpg
1238 ms
zoom-2.jpg
1238 ms
zoom-2.jpg
1414 ms
2016_ds_e-tense_concept_01.jpg
1415 ms
viewid=69065936725
283 ms
2016_ds_e-tense_concept_01.jpg
1415 ms
42 ms
layers.648fb6c882fbeb98be27.js
34 ms
x80aF-f8A-158x110.jpg
116 ms
ob_logo_67x12.png
97 ms
pixel
39 ms
1Lg7ND-f8A-158x110.jpg
204 ms
15CqU1-f8A-158x110.jpg
388 ms
1AtcYU-f8A-158x110.jpg
366 ms
1L4cTu-f8A-158x110.jpg
426 ms
1KfDW0-f8A-158x110.jpg
367 ms
1Dn4wU-f8A-158x110.jpg
364 ms
1KArvh-f8A-158x110.jpg
438 ms
a_030216nzhtbdrive11.jpg
1152 ms
a_030216nzhtbdrive11.jpg
1162 ms
2302splmechanic.jpg
1163 ms
2302splmechanic.jpg
1338 ms
apaudia416c.jpg
1335 ms
300x250-Jan-2016.html
197 ms
callback=ccauds
24 ms
viewid=69065936725
353 ms
relocate=;ord=1901733752
69 ms
viewid=69065936725
350 ms
comScore.htm
21 ms
tags=
469 ms
beacon.js
11 ms
html_inpage_rendering_lib_200_121.js
31 ms
pixel
14 ms
apaudia416c.jpg
1235 ms
a_sup250815naghilux.jpg
1236 ms
a_sup250815naghilux.jpg
1247 ms
giltrap_300x250.jpg
1248 ms
runtime.js
132 ms
Finance.jpg
1392 ms
logo-driven-footer@2x.png
1331 ms
lidar.js
32 ms
MDL0225_970x250_GO_BOOK_01.html
19 ms
Enabler_01_103.js
12 ms
edge.6.0.0.min.js
194 ms
activeview
114 ms
widgetGlobalEvent
149 ms
skew-overlay-left.svg
1150 ms
skew-overlay-right.svg
1152 ms
bbClose.png
1168 ms
MDL0225_970x250_GO_BOOK_01_edge.js
5 ms
MDL0225_970x250_GO_BOOK_01_edge.js
3 ms
jquery-2.0.3.min.js
14 ms
jquery-2.0.3.min.js
5 ms
bg.png
16 ms
copy1.png
9 ms
CTA.png
11 ms
copy2.png
18 ms
copy2a.png
17 ms
nr-885.min.js
144 ms
rt=ifr
14 ms
g.json
7 ms
tpc=na_id
17 ms
px
5 ms
3 ms
universalpixel.js
40 ms
362738.gif
7 ms
universalpixel.js
29 ms
universalpixel.js
25 ms
1ef10d8f33
50 ms
UPug
18 ms
pixel.js
20 ms
dpsync.html
25 ms
driven.co.nz accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
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
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
driven.co.nz 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
driven.co.nz 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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Driven.co.nz 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 Driven.co.nz 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.
driven.co.nz
Open Graph data is detected on the main page of Driven. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: