8.1 sec in total
801 ms
6.8 sec
451 ms
Click here to check amazing Hey Motors content. Otherwise, check out these important facts you probably never knew about heymotors.co.nz
Looking for high quality used cars? Hey Motors has a wide range of vehicles perfect for your needs. Browse our range online today.
Visit heymotors.co.nzWe analyzed Heymotors.co.nz page load time and found that the first response time was 801 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
heymotors.co.nz performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value25.1 s
0/100
25%
Value11.5 s
5/100
10%
Value560 ms
53/100
30%
Value0.062
97/100
15%
Value17.0 s
4/100
10%
801 ms
1045 ms
100 ms
58 ms
396 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 72% of them (41 requests) were addressed to the original Heymotors.co.nz, 9% (5 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Cdn.motorcentral.co.nz. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Heymotors.co.nz.
Page size can be reduced by 638.8 kB (23%)
2.8 MB
2.2 MB
In fact, the total size of Heymotors.co.nz main page is 2.8 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. 45% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 87.2 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 23.3 kB, which is 23% 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 87.2 kB or 85% of the original size.
Potential reduce by 547.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. Obviously, Hey Motors needs image optimization as it can save up to 547.4 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 3.1 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.
Potential reduce by 1.1 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. Heymotors.co.nz needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 22% of the original size.
Number of requests can be reduced by 18 (38%)
48
30
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hey Motors. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
heymotors.co.nz
801 ms
www.heymotors.co.nz
1045 ms
gtm.js
100 ms
css
58 ms
foundationCss
396 ms
assetsstyles
598 ms
sitestyles
999 ms
foundation-icons.css
53 ms
style.css
44 ms
ci-style.css
815 ms
headjs
830 ms
jquery.min.js
43 ms
foundationJs
1022 ms
assetsjs
1234 ms
jquery-ui.min.js
48 ms
motorcentraljs
1021 ms
WebResource.axd
832 ms
pageend
846 ms
api.js
30 ms
ai.0.js
19 ms
logo3.png
200 ms
search.png
207 ms
HEY-c0f3f55b-b828-4f86-beb6-859a26c1923b-1-1.jpg
208 ms
more-info.png
206 ms
HEY-b3d84c07-ad4f-49d5-8404-458ec35361e6-1-1.jpg
217 ms
HEY-df25cb3e-802a-4c7d-9f8e-571771874ec2-1-1.jpg
402 ms
HEY-ebcefaca-8145-4021-adec-4cc0199aba80-1-1.jpg
410 ms
HEY-7ab11789-ea50-4458-ba7c-12dd95f23826-1-1.jpg
410 ms
logo-invert2.png
603 ms
buying_focused.svg
534 ms
buying_confidence.svg
535 ms
buying_haggling.svg
599 ms
selling_car.svg
611 ms
selling_quick%20appraisals.svg
608 ms
selling_offers.svg
618 ms
partners.png
622 ms
pay-with.jpg
798 ms
ic_phone.svg
568 ms
ic_location.svg
572 ms
covid-banner.jpg
2148 ms
banner-2.jpg
978 ms
banner-4.jpg
786 ms
S6uyw4BMUTPHjx4wWw.ttf
48 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
49 ms
S6u8w4BMUTPHh30AXC-v.ttf
101 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
102 ms
S6u9w4BMUTPHh50XSwiPHA.ttf
102 ms
icomoon.ttf
1184 ms
icons-custom.ttf
690 ms
ic_man.svg
678 ms
ic_hours.svg
686 ms
ic_pin.svg
870 ms
recaptcha__en.js
136 ms
getmodels
930 ms
GetFavouriteVehicles
684 ms
style.css
203 ms
track
28 ms
heymotors.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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
heymotors.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
heymotors.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Heymotors.co.nz 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 Heymotors.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.
heymotors.co.nz
Open Graph description is not detected on the main page of Hey Motors. 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: