6.8 sec in total
409 ms
5.9 sec
520 ms
Visit urban.co.nz now to see the best up-to-date Urban content and also check out these interesting facts you probably never knew about urban.co.nz
At Urban Homes, we build beautiful homes in the Waikato, Bay of Plenty, Coromandel & South Auckland. We take ownership of your project as if it were our own
Visit urban.co.nzWe analyzed Urban.co.nz page load time and found that the first response time was 409 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
urban.co.nz performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value22.8 s
0/100
25%
Value17.9 s
0/100
10%
Value940 ms
30/100
30%
Value0.035
100/100
15%
Value24.6 s
0/100
10%
409 ms
2470 ms
584 ms
789 ms
596 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 98% of them (60 requests) were addressed to the original Urban.co.nz, 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Urban.co.nz.
Page size can be reduced by 1.4 MB (34%)
4.1 MB
2.7 MB
In fact, the total size of Urban.co.nz main page is 4.1 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.5 MB which makes up the majority of the site volume.
Potential reduce by 64.8 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 64.8 kB or 80% of the original size.
Potential reduce by 105.3 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. Urban images are well optimized though.
Potential reduce by 798.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 798.1 kB or 76% of the original size.
Potential reduce by 437.4 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. Urban.co.nz needs all CSS files to be minified and compressed as it can save up to 437.4 kB or 85% of the original size.
Number of requests can be reduced by 38 (69%)
55
17
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Urban. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
urban.co.nz
409 ms
urban.co.nz
2470 ms
style.min.css
584 ms
style.css
789 ms
magnific-popup.css
596 ms
slick.css
595 ms
fontawesome.min.css
991 ms
jquery-ui.css
794 ms
jquery-ui-slider-pips.css
777 ms
style_urban.css
1195 ms
responsive.css
993 ms
jquery.min.js
975 ms
jquery-migrate.min.js
986 ms
generate-pdf.js
994 ms
formreset.min.css
1103 ms
formsmain.min.css
1204 ms
readyclass.min.css
1103 ms
browsers.min.css
1104 ms
navigation.js
1102 ms
jquery.magnific-popup.js
1217 ms
jquery.touchSwipe.min.js
1204 ms
slick.min.js
1406 ms
jquery-ui.js
1822 ms
jquery-ui-slider-pips.min.js
1216 ms
slider.js
1401 ms
TweenMax.min.js
1600 ms
jquery.youtube-background.min.js
1408 ms
general.js
1609 ms
wp-polyfill-inert.min.js
1598 ms
regenerator-runtime.min.js
1607 ms
wp-polyfill.min.js
1608 ms
dom-ready.min.js
1793 ms
hooks.min.js
1801 ms
i18n.min.js
1807 ms
a11y.min.js
1808 ms
jquery.json.min.js
1808 ms
gravityforms.min.js
1989 ms
placeholders.jquery.min.js
1998 ms
utils.min.js
1614 ms
vendor-theme.min.js
1607 ms
scripts-theme.min.js
1610 ms
gtm.js
141 ms
phone-icon.svg
995 ms
Urban_20-Years-Badge_Logo-Lockup.svg
1165 ms
Story-Time-video-thumbnails.jpg
1176 ms
icon-play.png
1178 ms
journey-home1.jpg
1381 ms
Riverpoint_HL-Image_381x256-1.jpg
1790 ms
journey-home3.jpg
1196 ms
dropdown-arrow.svg
1359 ms
185.Cumberland-96_cropped-for-website-1-845x450.jpg
1304 ms
map-pin.svg
1303 ms
Kelly-Rd-Twilight-Front-Exterior-690x460.jpg
1328 ms
Previous-show-homes-leader-845x460.png
1879 ms
Oxygen-Light.woff
1497 ms
Oxygen-Regular.woff
1401 ms
Oxygen-Bold.woff
1402 ms
fa-brands-400.woff
1425 ms
urban-logo.svg
1603 ms
Urban_awards-logos_2022_Deloitte-5.png
1432 ms
TC_logo_final-01.png
1425 ms
urban.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
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
urban.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
urban.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 Urban.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 Urban.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.
urban.co.nz
Open Graph data is detected on the main page of Urban. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: