7.4 sec in total
511 ms
5.9 sec
900 ms
Welcome to wrens.co.nz homepage info - get ready to check Wrens best content right away, or after learning these important things about wrens.co.nz
Get a full project scope and specification service for a variety of projects like exterior installations,commercial floor tiling,bathroom renovation, with wrens.
Visit wrens.co.nzWe analyzed Wrens.co.nz page load time and found that the first response time was 511 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
wrens.co.nz performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value21.2 s
0/100
25%
Value19.8 s
0/100
10%
Value6,650 ms
0/100
30%
Value0.078
95/100
15%
Value21.0 s
1/100
10%
511 ms
1115 ms
411 ms
611 ms
1235 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 82% of them (63 requests) were addressed to the original Wrens.co.nz, 9% (7 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Wrens.co.nz.
Page size can be reduced by 3.7 MB (38%)
9.9 MB
6.2 MB
In fact, the total size of Wrens.co.nz main page is 9.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. 75% 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 9.0 MB which makes up the majority of the site volume.
Potential reduce by 39.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 6.8 kB, which is 15% 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 39.0 kB or 84% of the original size.
Potential reduce by 3.0 MB
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. Obviously, Wrens needs image optimization as it can save up to 3.0 MB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 316.9 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 316.9 kB or 68% of the original size.
Potential reduce by 373.9 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. Wrens.co.nz needs all CSS files to be minified and compressed as it can save up to 373.9 kB or 87% of the original size.
Number of requests can be reduced by 22 (34%)
65
43
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wrens. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
wrens.co.nz
511 ms
www.wrens.co.nz
1115 ms
themify-icons.css
411 ms
flaticon.css
611 ms
bootstrap.min.css
1235 ms
animate.css
1039 ms
owl.carousel.css
645 ms
owl.theme.css
643 ms
slick.css
644 ms
slick-theme.css
816 ms
owl.transitions.css
845 ms
jquery.fancybox.css
841 ms
perfect-scrollbar.css
840 ms
odometer-theme-default.css
1011 ms
lightbox.min.css
1048 ms
TweenMax.min.js
138 ms
style.css
1831 ms
js
222 ms
jquery.min.js
1245 ms
bootstrap.min.js
1018 ms
jquery-plugin-collection.js
1633 ms
script.js
1244 ms
lightbox-plus-jquery.min.js
1416 ms
css
48 ms
css2
60 ms
analytics.js
351 ms
footer-logo.png
543 ms
railway.jpg
1419 ms
slider.jpg
1033 ms
slide-2.jpg
825 ms
paint-3.png
1917 ms
about-us4.jpg
1243 ms
about-us3.jpg
774 ms
service-section-bg-s2.jpg
1031 ms
rttr.png
1055 ms
residential.jpg
1374 ms
who-we-are-2.jpg
1230 ms
who-we-are-3.jpg
1231 ms
who-we-are-1.jpg
1407 ms
about-us.jpg
1428 ms
gal2.jpg
1444 ms
gal6.jpg
1576 ms
gal7.jpg
1608 ms
gal9.jpg
1616 ms
gal3.jpg
1636 ms
gal4.jpg
1651 ms
service-section-bg.png
1776 ms
project1.jpg
1806 ms
project2.jpg
2013 ms
project3.jpg
1837 ms
slide-v1-2.jpg
2044 ms
client-1.png
1974 ms
client-2.png
2004 ms
client-3.png
2037 ms
client-4.png
2112 ms
client-6.png
2175 ms
client-7.png
2203 ms
contact-map.png
2211 ms
eco_decorator_col_on_black.jpg
2234 ms
slide-v1-3.jpg
2244 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSysdUmj.ttf
427 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1EuyysdUmj.ttf
550 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1E1yysdUmj.ttf
552 ms
Flaticon.svg
2216 ms
Flaticon.woff
2279 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
552 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYA.ttf
554 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf
554 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf
555 ms
themify9f24.woff
1888 ms
collect
91 ms
collect
64 ms
ajax-loader.gif
1645 ms
prev.png
1623 ms
next.png
1411 ms
loading.gif
1462 ms
close.png
1522 ms
wrens.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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
wrens.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
wrens.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
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 Wrens.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 Wrens.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.
wrens.co.nz
Open Graph description is not detected on the main page of Wrens. 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: