5.8 sec in total
599 ms
5 sec
195 ms
Click here to check amazing Wises content for New Zealand. Otherwise, check out these important facts you probably never knew about wises.co.nz
Yellow® are on a mission to help New Zealand Business thrive by developing Marketing Solutions to help them grow. Learn about our multi-channel solutions.
Visit wises.co.nzWe analyzed Wises.co.nz page load time and found that the first response time was 599 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
wises.co.nz performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value6.3 s
10/100
25%
Value13.8 s
1/100
10%
Value7,570 ms
0/100
30%
Value0.369
29/100
15%
Value25.6 s
0/100
10%
599 ms
816 ms
196 ms
769 ms
584 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 38% of them (42 requests) were addressed to the original Wises.co.nz, 39% (43 requests) were made to Maps.googleapis.com and 6% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Two.finda.co.nz.
Page size can be reduced by 851.5 kB (63%)
1.3 MB
496.3 kB
In fact, the total size of Wises.co.nz 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. 50% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 77.0 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 12.9 kB, which is 14% 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 77.0 kB or 84% of the original size.
Potential reduce by 3.1 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. Wises images are well optimized though.
Potential reduce by 714.4 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 714.4 kB or 71% of the original size.
Potential reduce by 57.0 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. Wises.co.nz needs all CSS files to be minified and compressed as it can save up to 57.0 kB or 83% of the original size.
Number of requests can be reduced by 71 (69%)
103
32
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wises. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and as a result speed up the page load time.
wises.co.nz
599 ms
www.wises.co.nz
816 ms
wises.css
196 ms
utilities.js
769 ms
autocomplete-min.js
584 ms
datasource-beta-min.js
417 ms
jsapi
19 ms
js
43 ms
wises.js
398 ms
swfobject.js
448 ms
ad_serverV2.js
452 ms
advertbanner.js
592 ms
json-min.js
608 ms
markermanager.js
894 ms
map.js
901 ms
gmap.js
794 ms
googlemap_marker_tools.js
795 ms
urchin.js
21 ms
spcjs.php
1007 ms
274 ms
bg-top.gif
194 ms
logo.gif
196 ms
printer.png
193 ms
spinner.gif
227 ms
save.png
197 ms
email.png
228 ms
help.png
376 ms
icon-accomm-holidayaccomm.gif
384 ms
icon-leisure-cinemas.gif
390 ms
icon-dining-restaurant.gif
390 ms
icon-travel-airport.gif
450 ms
icon-accomm-backpackers.gif
452 ms
bg_loading.png
569 ms
openhand.bmp
574 ms
logo-map.png
583 ms
button_larger.png
584 ms
bg_key.png
673 ms
smith.png
677 ms
Liquor_King.jpg
762 ms
button_go.gif
767 ms
swap.png
777 ms
map_icon.gif
771 ms
finda_logo-sm.gif
892 ms
location_background-full.jpg
898 ms
business_background.jpg
948 ms
ga.js
13 ms
;page=;sz=300x250;ord=7507071790751070
38 ms
__utm.gif
11 ms
6428233386538084386
30 ms
v60a.js
72 ms
__utm.gif
22 ms
location_background.jpg
845 ms
business_icon.gif
858 ms
storageframe.html
25 ms
m
25 ms
nr-686.min.js
81 ms
common.js
20 ms
map.js
40 ms
overlay.js
39 ms
util.js
47 ms
onion.js
22 ms
ViewportInfoService.GetViewportInfo
62 ms
stats.js
22 ms
controls.js
29 ms
4649912473
78 ms
infowindow.js
21 ms
transparent.png
47 ms
css
44 ms
marker.js
29 ms
google4.png
40 ms
mapcnt6.png
40 ms
vt
22 ms
vt
32 ms
vt
32 ms
vt
56 ms
vt
33 ms
vt
42 ms
vt
34 ms
vt
52 ms
vt
38 ms
vt
60 ms
vt
55 ms
vt
76 ms
vt
56 ms
vt
76 ms
vt
62 ms
vt
74 ms
vt
73 ms
vt
82 ms
vt
76 ms
vt
88 ms
vt
89 ms
vt
90 ms
vt
91 ms
vt
85 ms
vt
96 ms
vt
103 ms
vt
113 ms
vt
107 ms
vt
105 ms
vt
108 ms
tmapctrl.png
14 ms
cb_scout5.png
31 ms
tmapctrl4.png
24 ms
imgs8.png
24 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
30 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
41 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
56 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
60 ms
AuthenticationService.Authenticate
238 ms
usage.js
12 ms
wises.co.nz 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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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>).
wises.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
wises.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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wises.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 Wises.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.
wises.co.nz
Open Graph description is not detected on the main page of Wises. 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: