5.3 sec in total
401 ms
4.5 sec
412 ms
Visit wanly.co.nz now to see the best up-to-date Wanly content and also check out these interesting facts you probably never knew about wanly.co.nz
Wanly Tsang is an enthusiastic and top performing Real Estate state professional with over 10 years experience selling properties on the North Shore.
Visit wanly.co.nzWe analyzed Wanly.co.nz page load time and found that the first response time was 401 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
wanly.co.nz performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value19.9 s
0/100
25%
Value14.2 s
1/100
10%
Value1,050 ms
25/100
30%
Value0.747
6/100
15%
Value20.3 s
2/100
10%
401 ms
2043 ms
35 ms
10 ms
16 ms
Our browser made a total of 181 requests to load all elements on the main page. We found that 88% of them (159 requests) were addressed to the original Wanly.co.nz, 7% (13 requests) were made to Fonts.gstatic.com and 3% (5 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Wanly.co.nz.
Page size can be reduced by 693.2 kB (18%)
3.9 MB
3.2 MB
In fact, the total size of Wanly.co.nz main page is 3.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. Only a small number of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 110.9 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 110.9 kB or 82% of the original size.
Potential reduce by 62.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. Wanly images are well optimized though.
Potential reduce by 346.5 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 346.5 kB or 37% of the original size.
Potential reduce by 173.8 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. Wanly.co.nz needs all CSS files to be minified and compressed as it can save up to 173.8 kB or 39% of the original size.
Number of requests can be reduced by 133 (83%)
160
27
The browser has sent 160 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wanly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 106 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
wanly.co.nz
401 ms
wanly.co.nz
2043 ms
fbevents.js
35 ms
layerslider.css
10 ms
style.min.css
16 ms
style.css
29 ms
mediaelementplayer-legacy.min.css
27 ms
wp-mediaelement.min.css
28 ms
style.css
76 ms
font-awesome.min.css
73 ms
style.min.css
75 ms
style.css
71 ms
dripicons.css
71 ms
kiko-all.css
70 ms
stylesheet.min.css
123 ms
print.css
81 ms
style_dynamic.css
77 ms
responsive.min.css
82 ms
style_dynamic_responsive.css
80 ms
js_composer.min.css
95 ms
css
121 ms
core-dashboard.min.css
118 ms
style.css
94 ms
greensock.js
120 ms
jquery.min.js
173 ms
jquery-migrate.min.js
306 ms
layerslider.kreaturamedia.jquery.js
173 ms
layerslider.transitions.js
169 ms
script.js
170 ms
mej1wbd.css
229 ms
animate.min.css
171 ms
dashicons.min.css
173 ms
display-opinions-light.css
173 ms
font-awesome.min.css
179 ms
display-structure.css
174 ms
core.min.js
175 ms
accordion.min.js
176 ms
menu.min.js
178 ms
dom-ready.min.js
177 ms
hooks.min.js
177 ms
i18n.min.js
177 ms
a11y.min.js
181 ms
autocomplete.min.js
166 ms
controlgroup.min.js
158 ms
checkboxradio.min.js
157 ms
button.min.js
158 ms
datepicker.min.js
116 ms
mouse.min.js
115 ms
resizable.min.js
114 ms
draggable.min.js
154 ms
dialog.min.js
113 ms
droppable.min.js
108 ms
progressbar.min.js
110 ms
selectable.min.js
110 ms
sortable.min.js
103 ms
slider.min.js
102 ms
style.css
99 ms
spinner.min.js
73 ms
tooltip.min.js
106 ms
tabs.min.js
106 ms
effect.min.js
63 ms
effect-blind.min.js
58 ms
effect-bounce.min.js
57 ms
effect-clip.min.js
58 ms
effect-drop.min.js
57 ms
effect-explode.min.js
57 ms
effect-fade.min.js
56 ms
effect-fold.min.js
56 ms
effect-highlight.min.js
56 ms
effect-pulsate.min.js
56 ms
effect-size.min.js
55 ms
effect-scale.min.js
57 ms
effect-shake.min.js
55 ms
effect-slide.min.js
55 ms
effect-transfer.min.js
56 ms
doubletaptogo.js
56 ms
modernizr.min.js
55 ms
jquery.appear.js
56 ms
hoverIntent.min.js
55 ms
counter.js
56 ms
easypiechart.js
56 ms
mixitup.js
57 ms
jquery.prettyPhoto.js
54 ms
jquery.fitvids.js
55 ms
jquery.flexslider-min.js
55 ms
mediaelement-and-player.min.js
58 ms
mediaelement-migrate.min.js
55 ms
wp-mediaelement.min.js
242 ms
infinitescroll.min.js
55 ms
jquery.waitforimages.js
55 ms
jquery.form.min.js
23 ms
waypoints.min.js
23 ms
jplayer.min.js
24 ms
bootstrap.carousel.js
22 ms
skrollr.js
22 ms
Chart.min.js
24 ms
jquery.easing.1.3.js
22 ms
abstractBaseClass.js
23 ms
jquery.countdown.js
22 ms
jquery.multiscroll.min.js
22 ms
jquery.justifiedGallery.min.js
22 ms
bigtext.js
22 ms
jquery.sticky-kit.min.js
23 ms
owl.carousel.min.js
21 ms
typed.js
21 ms
jquery.carouFredSel-6.2.1.min.js
22 ms
lemmon-slider.min.js
22 ms
jquery.fullPage.min.js
21 ms
jquery.mousewheel.min.js
21 ms
jquery.touchSwipe.min.js
21 ms
jquery.isotope.min.js
21 ms
packery-mode.pkgd.min.js
20 ms
jquery.stretch.js
20 ms
imagesloaded.js
21 ms
rangeslider.min.js
19 ms
jquery.event.move.js
20 ms
jquery.twentytwenty.js
19 ms
swiper.min.js
19 ms
TweenLite.min.js
21 ms
ScrollToPlugin.min.js
20 ms
smoothPageScroll.min.js
19 ms
default_dynamic.js
21 ms
default.min.js
21 ms
js_composer_front.min.js
19 ms
qode-like.min.js
17 ms
pixel-cat.min.js
431 ms
video.js
18 ms
vc-waypoints.min.js
18 ms
underscore.min.js
16 ms
backbone.min.js
18 ms
front-end-deps.js
18 ms
front-end.js
16 ms
front-end.js
18 ms
front-end.js
16 ms
p.css
23 ms
gtm.js
87 ms
WanlyTsang-Team_reversed.png
20 ms
Wanly_BG_Slider-04.jpg
472 ms
Wanly-Orange-Clearcut.png
634 ms
Wanly_BG_Slider-04-mobile.jpg
20 ms
Add-a-subheading-3-300x300.png
329 ms
Wanly-Awards-Reef-3-300x300.png
37 ms
Wanly-Awards-Reef-4-300x300.png
36 ms
BB-20201-300x300.png
329 ms
Add-a-subheading-4-300x300.png
328 ms
No.1-cc-2019-2020-300x300.png
504 ms
No.1-c-C-2018-2019-300x300.png
333 ms
Logo-1-300x300.png
511 ms
Wanly-Orange-Clearcut-340x340.png
334 ms
logo-edited-200x200.png
338 ms
Wanly-Blog-template-10-539x303.jpg
336 ms
Wanly-Blog-template-4-539x303.png
338 ms
Wanly-Blog-template-1-539x303.jpg
337 ms
Wanly-Blog-template-539x303.jpg
338 ms
WanlyTsang-Team_reversed-300x62.png
340 ms
harcourts-cc-white-stacked.png
338 ms
Boostique_logo_V2_white-footer.png
339 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf
60 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf
304 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf
308 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf
313 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf
312 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf
310 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf
310 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf
308 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf
310 ms
d
15 ms
d
58 ms
fontawesome-webfont.woff
1665 ms
KauriApartmentsBrownsBay_5.jpg
343 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LDr0fJQ.ttf
267 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMDr0fJQ.ttf
268 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4TbMDr0fJQ.ttf
267 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjNDr0fJQ.ttf
269 ms
d
256 ms
d
259 ms
fontawesome-webfont.woff
132 ms
skin.css
69 ms
icon-muted-white.png
11 ms
icon-unmuted-white.png
220 ms
Wanly_BG_Slider-04-mobile.jpg
12 ms
wanly.co.nz 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
wanly.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
wanly.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
Image elements do not have [alt] attributes
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 Wanly.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 Wanly.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.
wanly.co.nz
Open Graph data is detected on the main page of Wanly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: