4.5 sec in total
273 ms
3.7 sec
501 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 273 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
wanly.co.nz performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value20.1 s
0/100
25%
Value15.7 s
0/100
10%
Value2,850 ms
3/100
30%
Value0.747
6/100
15%
Value20.9 s
1/100
10%
273 ms
2200 ms
37 ms
13 ms
21 ms
Our browser made a total of 180 requests to load all elements on the main page. We found that 88% of them (158 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.2 sec) belongs to the original domain Wanly.co.nz.
Page size can be reduced by 312.5 kB (9%)
3.5 MB
3.2 MB
In fact, the total size of Wanly.co.nz main page is 3.5 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. 85% 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. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 103.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 103.9 kB or 82% of the original size.
Potential reduce by 61.7 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 93.2 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 93.2 kB or 13% of the original size.
Potential reduce by 53.7 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 53.7 kB or 17% of the original size.
Number of requests can be reduced by 135 (85%)
159
24
The browser has sent 159 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 108 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
wanly.co.nz
273 ms
wanly.co.nz
2200 ms
fbevents.js
37 ms
listingstyle.css
13 ms
layerslider.css
21 ms
style.min.css
26 ms
mediaelementplayer-legacy.min.css
31 ms
wp-mediaelement.min.css
22 ms
style.css
34 ms
font-awesome.min.css
29 ms
style.min.css
32 ms
style.css
64 ms
dripicons.css
68 ms
kiko-all.css
33 ms
stylesheet.min.css
78 ms
print.css
66 ms
style_dynamic.css
68 ms
responsive.min.css
72 ms
style_dynamic_responsive.css
109 ms
js_composer.min.css
110 ms
css
68 ms
core-dashboard.min.css
127 ms
style.css
128 ms
greensock.js
130 ms
jquery.min.js
130 ms
jquery-migrate.min.js
130 ms
layerslider.kreaturamedia.jquery.js
135 ms
layerslider.transitions.js
136 ms
mej1wbd.css
240 ms
animate.min.css
136 ms
dashicons.min.css
134 ms
display-opinions-light.css
135 ms
font-awesome.min.css
134 ms
display-structure.css
141 ms
core.min.js
138 ms
accordion.min.js
221 ms
menu.min.js
137 ms
wp-polyfill-inert.min.js
135 ms
regenerator-runtime.min.js
136 ms
wp-polyfill.min.js
144 ms
dom-ready.min.js
137 ms
hooks.min.js
135 ms
i18n.min.js
124 ms
a11y.min.js
128 ms
autocomplete.min.js
118 ms
controlgroup.min.js
118 ms
checkboxradio.min.js
119 ms
button.min.js
119 ms
datepicker.min.js
118 ms
mouse.min.js
90 ms
resizable.min.js
158 ms
draggable.min.js
86 ms
dialog.min.js
85 ms
droppable.min.js
78 ms
progressbar.min.js
44 ms
selectable.min.js
47 ms
sortable.min.js
29 ms
slider.min.js
29 ms
style.css
29 ms
spinner.min.js
88 ms
tooltip.min.js
87 ms
tabs.min.js
86 ms
effect.min.js
88 ms
effect-blind.min.js
83 ms
effect-bounce.min.js
83 ms
effect-clip.min.js
85 ms
effect-drop.min.js
83 ms
effect-explode.min.js
88 ms
effect-fade.min.js
85 ms
effect-fold.min.js
85 ms
effect-highlight.min.js
93 ms
effect-pulsate.min.js
86 ms
effect-size.min.js
87 ms
effect-scale.min.js
86 ms
effect-shake.min.js
83 ms
effect-slide.min.js
88 ms
effect-transfer.min.js
86 ms
doubletaptogo.js
84 ms
modernizr.min.js
86 ms
jquery.appear.js
86 ms
hoverIntent.min.js
92 ms
counter.js
86 ms
easypiechart.js
85 ms
mixitup.js
87 ms
jquery.prettyPhoto.js
86 ms
jquery.fitvids.js
86 ms
jquery.flexslider-min.js
86 ms
mediaelement-and-player.min.js
88 ms
mediaelement-migrate.min.js
85 ms
wp-mediaelement.min.js
88 ms
infinitescroll.min.js
86 ms
jquery.waitforimages.js
29 ms
jquery.form.min.js
30 ms
waypoints.min.js
30 ms
jplayer.min.js
32 ms
bootstrap.carousel.js
28 ms
skrollr.js
28 ms
Chart.min.js
29 ms
jquery.easing.1.3.js
32 ms
abstractBaseClass.js
29 ms
jquery.countdown.js
29 ms
jquery.multiscroll.min.js
28 ms
jquery.justifiedGallery.min.js
30 ms
bigtext.js
29 ms
jquery.sticky-kit.min.js
30 ms
owl.carousel.min.js
28 ms
typed.js
28 ms
jquery.carouFredSel-6.2.1.min.js
35 ms
lemmon-slider.min.js
28 ms
jquery.fullPage.min.js
27 ms
jquery.mousewheel.min.js
28 ms
jquery.touchSwipe.min.js
26 ms
jquery.isotope.min.js
27 ms
packery-mode.pkgd.min.js
27 ms
jquery.stretch.js
26 ms
imagesloaded.js
26 ms
rangeslider.min.js
26 ms
jquery.event.move.js
25 ms
jquery.twentytwenty.js
26 ms
swiper.min.js
26 ms
TweenLite.min.js
26 ms
ScrollToPlugin.min.js
26 ms
smoothPageScroll.min.js
25 ms
p.css
37 ms
default_dynamic.js
26 ms
default.min.js
25 ms
js_composer_front.min.js
24 ms
qode-like.min.js
524 ms
pixel-cat.min.js
25 ms
video.js
22 ms
vc-waypoints.min.js
804 ms
underscore.min.js
22 ms
backbone.min.js
21 ms
front-end-deps.js
23 ms
front-end.js
22 ms
front-end.js
19 ms
front-end.js
20 ms
gtm.js
130 ms
WanlyTsang-Team_reversed.png
25 ms
Wanly_BG_Slider-04.jpg
24 ms
Wanly-Orange-Clearcut.png
47 ms
Wanly_BG_Slider-04-mobile.jpg
25 ms
Add-a-subheading-3-300x300.png
49 ms
Wanly-Awards-Reef-3-300x300.png
48 ms
Wanly-Awards-Reef-4-300x300.png
49 ms
BB-20201-300x300.png
51 ms
Add-a-subheading-4-300x300.png
49 ms
No.1-cc-2019-2020-300x300.png
483 ms
No.1-c-C-2018-2019-300x300.png
49 ms
Logo-1-300x300.png
51 ms
Wanly-Orange-Clearcut-340x340.png
51 ms
logo-edited-200x200.png
94 ms
Wanly-Blog-template-10-539x303.jpg
93 ms
Wanly-Blog-template-4-539x303.png
122 ms
Wanly-Blog-template-1-539x303.jpg
121 ms
Wanly-Blog-template-539x303.jpg
121 ms
WanlyTsang-Team_reversed-300x62.png
479 ms
harcourts-cc-white-stacked.png
124 ms
Boostique_logo_V2_white-footer.png
123 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf
97 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf
167 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf
455 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf
455 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf
458 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf
456 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf
458 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf
458 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf
456 ms
d
64 ms
d
450 ms
fontawesome-webfont.woff
96 ms
KauriApartmentsBrownsBay_5.jpg
444 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LDr0fJQ.ttf
382 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMDr0fJQ.ttf
383 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4TbMDr0fJQ.ttf
384 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjNDr0fJQ.ttf
384 ms
d
377 ms
d
384 ms
fontawesome-webfont.woff
532 ms
skin.css
69 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
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: