12.1 sec in total
657 ms
11.2 sec
291 ms
Click here to check amazing Stone Set Nz content. Otherwise, check out these important facts you probably never knew about stonesetnz.co.nz
All StoneSet products are porous so can be used to create a hardwearing surface suitable for vehicular traffic but also one which allows water to pass through.
Visit stonesetnz.co.nzWe analyzed Stonesetnz.co.nz page load time and found that the first response time was 657 ms and then it took 11.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
stonesetnz.co.nz performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value27.7 s
0/100
25%
Value31.8 s
0/100
10%
Value4,260 ms
1/100
30%
Value0.041
99/100
15%
Value19.9 s
2/100
10%
657 ms
3212 ms
87 ms
412 ms
631 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Stonesetnz.co.nz, 86% (117 requests) were made to Stoneset.co.nz and 6% (8 requests) were made to Stoneset.com.au. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Stoneset.com.au.
Page size can be reduced by 756.6 kB (14%)
5.6 MB
4.8 MB
In fact, the total size of Stonesetnz.co.nz main page is 5.6 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 4.0 MB which makes up the majority of the site volume.
Potential reduce by 540.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. 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 540.1 kB or 92% of the original size.
Potential reduce by 184.6 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. Stone Set Nz images are well optimized though.
Potential reduce by 14.4 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 17.6 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. Stonesetnz.co.nz has all CSS files already compressed.
Number of requests can be reduced by 94 (77%)
122
28
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stone Set Nz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 62 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.
stonesetnz.co.nz
657 ms
stoneset.co.nz
3212 ms
js
87 ms
wp-emoji-release.min.js
412 ms
style.min.css
631 ms
wc-blocks-vendors-style.css
688 ms
wc-blocks-style.css
912 ms
bafis-css.min.css
697 ms
styles.css
700 ms
jquery-ui.min.css
30 ms
jquery-ui-timepicker-addon.min.css
698 ms
slick.css
850 ms
magnific-popup.css
900 ms
wp-pap-public.min.css
919 ms
rs6.css
921 ms
woocommerce-layout.css
924 ms
woocommerce.css
1069 ms
wpforms-full.min.css
1115 ms
cb70d11b8.min.css
1128 ms
style.css
1131 ms
style.css
1137 ms
flaticon.css
1137 ms
all.min.css
1290 ms
main.css
1963 ms
elementor-icons.min.css
1343 ms
animations.min.css
1344 ms
frontend.min.css
1352 ms
post-8486.css
1357 ms
global.css
1507 ms
post-8777.css
1560 ms
post-8739.css
1561 ms
post-8740.css
1572 ms
post-8738.css
1573 ms
upw-theme-standard.min.css
1725 ms
photonic-baguettebox.min.css
1781 ms
frontend-gtag.min.js
1780 ms
jquery.min.js
1791 ms
jquery-migrate.min.js
1792 ms
rbtools.min.js
1950 ms
js
41 ms
js
45 ms
analytics.js
4 ms
collect
21 ms
css
62 ms
api.js
78 ms
animate.css
1821 ms
rs6.min.js
2028 ms
regenerator-runtime.min.js
1394 ms
wp-polyfill.min.js
1338 ms
index.js
1487 ms
core.min.js
1484 ms
datepicker.min.js
1528 ms
jquery-ui-timepicker-addon.min.js
1393 ms
mouse.min.js
1344 ms
slider.min.js
1484 ms
controlgroup.min.js
1480 ms
checkboxradio.min.js
1607 ms
button.min.js
1608 ms
jquery-ui-sliderAccess.js
1459 ms
jquery.blockUI.min.js
1553 ms
js.cookie.min.js
1542 ms
woocommerce.min.js
1541 ms
cart-fragments.min.js
1535 ms
cb70d11b8.min.js
1646 ms
theme-addons.js
1492 ms
theme.js
1494 ms
perfect-scrollbar.min.js
1504 ms
wp-embed.min.js
1515 ms
jquery.appear.js
1529 ms
wgl_elementor_widgets.js
1494 ms
photonic-baguettebox.min.js
1452 ms
photonic-baguettebox.min.js
1490 ms
anime.min.js
1501 ms
parallax.min.js
1515 ms
jquery.paroller.min.js
1378 ms
imagesloaded.min.js
1438 ms
slick.min.js
1450 ms
jarallax.min.js
1475 ms
jarallax-video.min.js
1501 ms
elfsight-instagram-feed.js
1584 ms
wgl_elementor_sections.js
1316 ms
wgl_elementor_column.js
1426 ms
webpack.runtime.min.js
1435 ms
frontend-modules.min.js
1462 ms
waypoints.min.js
1346 ms
swiper.min.js
1593 ms
share-link.min.js
1445 ms
dialog.min.js
1449 ms
frontend.min.js
1461 ms
preloaded-modules.min.js
1353 ms
underscore.min.js
1381 ms
Naigation-Leaf.png
2007 ms
6a5d2a8bafcb3384ad40b37003b35352
131 ms
home-2_phone1.png
2156 ms
Hero-2-Homepage.jpg
4698 ms
Hero-3-Homepage.jpg
2742 ms
wp-util.min.js
1361 ms
frontend.min.js
1383 ms
jquery.validate.min.js
1391 ms
mailcheck.min.js
1395 ms
Colour-Range-Hero-Image.jpg
1944 ms
Pour-On-scaled.jpg
2493 ms
IMG_6633-1-scaled.jpg
3401 ms
Close-up-Stoneset-Footer-Background.jpg
3528 ms
punycode.min.js
1330 ms
wpforms.js
1330 ms
fa-solid-900.woff
1943 ms
fa-regular-400.woff
1585 ms
Flaticon.svg
1697 ms
Flaticon.woff
1509 ms
fa-brands-400.woff
1644 ms
stoneset-logo-2.png
1444 ms
transparent.png
1700 ms
Home-slider-tree-surrounds.jpg
1861 ms
About-Image-1-840x620.jpg
1773 ms
About-Image-3-840x620.png
3156 ms
Sydney_Observatory_07-840x620.jpg
1864 ms
stonset-driveway-840x620.jpg
2355 ms
Green-Leaf.png
1729 ms
David-Barnes-Signature-1024x310.png
1861 ms
Architect-Drawing-Home-page-600x620.jpg
1774 ms
submit-spin.svg
1806 ms
Porous-Tree.jpg
1869 ms
overlay-scale-zoom.jpg
1899 ms
blog_image-1.png
1885 ms
1962-Tuross-Heads-NSW-6mm-3mm-Charcoal-Overlay-5.JPG-small-1170x725.jpg
2470 ms
IMG_3090-1170x725.jpg
1903 ms
Pool-side-image-1170x725.jpg
1933 ms
earth-1389715_1280-1170x725.png
2351 ms
leaf-1082118_1280-1170x725.jpg
1998 ms
2279Roseville-Chase-NSW-Evergreen-Ash-1170x725.jpg
1969 ms
outside-254716_1280-1170x725.jpg
2180 ms
image-24-2.jpg
2100 ms
recaptcha__en.js
292 ms
stoneset.co.nz
3155 ms
woocommerce-smallscreen.css
222 ms
stonesetnz.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
button, link, and menuitem elements do not have accessible names.
[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
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.
stonesetnz.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 Stonesetnz.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 Stonesetnz.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.
stonesetnz.co.nz
Open Graph data is detected on the main page of Stone Set Nz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: