8.1 sec in total
994 ms
6.6 sec
572 ms
Visit proppy.co.nz now to see the best up-to-date Proppy content for New Zealand and also check out these interesting facts you probably never knew about proppy.co.nz
Proppy is a smarter way to buy and sell real estate in NZ! View houses for sale in New Zealand, participate in online real estate auctions & negotiations.
Visit proppy.co.nzWe analyzed Proppy.co.nz page load time and found that the first response time was 994 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
proppy.co.nz performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value12.4 s
0/100
25%
Value22.1 s
0/100
10%
Value28,550 ms
0/100
30%
Value0.272
45/100
15%
Value38.1 s
0/100
10%
994 ms
89 ms
80 ms
142 ms
147 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 28% of them (29 requests) were addressed to the original Proppy.co.nz, 13% (13 requests) were made to Fonts.gstatic.com and 10% (10 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Proppy.co.nz.
Page size can be reduced by 123.5 kB (7%)
1.8 MB
1.6 MB
In fact, the total size of Proppy.co.nz main page is 1.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. 80% 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 37.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. This page needs HTML code to be minified as it can gain 8.0 kB, which is 16% 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 37.1 kB or 76% of the original size.
Potential reduce by 39.9 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. Proppy images are well optimized though.
Potential reduce by 2.3 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 44.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. Proppy.co.nz needs all CSS files to be minified and compressed as it can save up to 44.1 kB or 27% of the original size.
Number of requests can be reduced by 50 (64%)
78
28
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Proppy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.proppy.co.nz
994 ms
gtm.js
89 ms
css2
80 ms
css
142 ms
css
147 ms
styles.min.css
1003 ms
jquery-ui.min.css
45 ms
jquery.min.js
76 ms
bootstrap.bundle.js
111 ms
ion.rangeSlider.min.js
138 ms
select2.min.js
138 ms
jquery.magnific-popup.min.js
137 ms
slick.min.js
136 ms
lightbox.min.js
137 ms
jquery-ui.min.js
139 ms
jquery.ui.touch-punch.min.js
141 ms
custom.min.js
997 ms
calculator.min.js
997 ms
analytics.js
175 ms
roundtrip.js
234 ms
insight.min.js
262 ms
js
73 ms
asset_composer.js
252 ms
collect
176 ms
collect
51 ms
index.js
30 ms
index.js
319 ms
3wSUOtX4DTTCXwH1l5H62duUihsJroxa
248 ms
PBJ65DP4UVACXFVUDNZ6C6
82 ms
ga-audiences
78 ms
F5W2TZ6MSZFSHP74WHCGFB.js
416 ms
widget_v2.334.js
35 ms
045_Open2view_ID531861-50_Te_kohanga_Drive.jpg
1093 ms
9
815 ms
logo.png
542 ms
banner-2022.jpg
1361 ms
arrow-down.png
541 ms
proppy.png
844 ms
tall-poppy.png
900 ms
mike-pero.png
1359 ms
barfoots.png
1359 ms
lj-hooker.png
1360 ms
professionals.png
1377 ms
eves.png
1583 ms
ray-white.png
1573 ms
harcourts.png
1572 ms
bayleys.png
1574 ms
banner.jpg
2442 ms
logo-tagline-reverse.png
1594 ms
fern.png
1793 ms
diffuser.js
767 ms
fbevents.js
716 ms
onsiteloader.js
496 ms
sendrolling.js
160 ms
out
474 ms
out
473 ms
out
625 ms
out
625 ms
out
626 ms
ai.2.min.js
642 ms
lightbox-prev.png
1315 ms
lightbox-next.png
1316 ms
loading.gif
1321 ms
close.png
1334 ms
ajax-loader.gif
1535 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e4.woff
393 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e4.woff
500 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFkQl0k30e4.woff
543 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e4.woff
554 ms
pxiEyp8kv8JHgFVrJJfedA.woff
549 ms
pxiByp8kv8JHgFVrLEj6Z1xlEw.woff
550 ms
pxiByp8kv8JHgFVrLCz7Z1xlEw.woff
545 ms
pxiByp8kv8JHgFVrLDD4Z1xlEw.woff
551 ms
pxiByp8kv8JHgFVrLBT5Z1xlEw.woff
551 ms
fa-solid-900.woff
1728 ms
fa-regular-400.woff
1509 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQNis.woff
556 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QNis.woff
579 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXNis.woff
577 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXNis.woff
556 ms
themify.woff
1744 ms
LineIcons.ttf
2175 ms
main.39c29e42.js
127 ms
main.2a90a3dd.css
72 ms
tap.php
474 ms
Pug
401 ms
159 ms
1770804723136474
200 ms
prism.app-us1.com
353 ms
intlTelInput.min.css
340 ms
sync
84 ms
366154877859784
127 ms
rum
46 ms
pixel
84 ms
sd
100 ms
in
17 ms
xuid
65 ms
bounce
66 ms
in
38 ms
jftq2c8s_aclogo_dk.png
250 ms
avatar_simple_visitor.png
134 ms
297115860488377
100 ms
hbABjQBLsAhQWLEBAY5ZsUYGK1ghsBBZS7AUUlghsIBZHbAGK1xYWbAUKwAAAAFcPYvrAAA=
3 ms
proppy.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.
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.
proppy.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
proppy.co.nz SEO score
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 Proppy.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 Proppy.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.
proppy.co.nz
Open Graph description is not detected on the main page of Proppy. 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: