13.8 sec in total
660 ms
12.9 sec
277 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 660 ms and then it took 13.1 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
Value6.2 s
3/100
10%
Value27.0 s
0/100
25%
Value26.1 s
0/100
10%
Value2,920 ms
3/100
30%
Value0.041
99/100
15%
Value18.9 s
3/100
10%
660 ms
5102 ms
120 ms
612 ms
660 ms
Our browser made a total of 132 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, 89% (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 (5.1 sec) relates to the external source Stoneset.co.nz.
Page size can be reduced by 755.7 kB (13%)
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 539.5 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 539.5 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.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. 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 91 (77%)
118
27
The browser has sent 118 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 59 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.
stonesetnz.co.nz
660 ms
stoneset.co.nz
5102 ms
js
120 ms
wp-emoji-release.min.js
612 ms
style.min.css
660 ms
wc-blocks-vendors-style.css
651 ms
wc-blocks-style.css
870 ms
bafis-css.min.css
657 ms
styles.css
656 ms
jquery-ui.min.css
29 ms
jquery-ui-timepicker-addon.min.css
823 ms
slick.css
863 ms
magnific-popup.css
879 ms
wp-pap-public.min.css
879 ms
rs6.css
882 ms
woocommerce-layout.css
1037 ms
woocommerce.css
1077 ms
wpforms-full.min.css
1083 ms
cb70d11b8.min.css
1085 ms
style.css
1087 ms
style.css
1086 ms
flaticon.css
1248 ms
all.min.css
1292 ms
main.css
1525 ms
elementor-icons.min.css
1311 ms
animations.min.css
1320 ms
frontend.min.css
1560 ms
post-8486.css
1457 ms
global.css
1500 ms
post-8777.css
1555 ms
post-8739.css
1565 ms
post-8740.css
1669 ms
post-8738.css
1713 ms
upw-theme-standard.min.css
1734 ms
photonic-baguettebox.min.css
1736 ms
frontend-gtag.min.js
1747 ms
jquery.min.js
1957 ms
jquery-migrate.min.js
1882 ms
rbtools.min.js
2141 ms
css
34 ms
api.js
49 ms
animate.css
1560 ms
rs6.min.js
1991 ms
regenerator-runtime.min.js
1327 ms
wp-polyfill.min.js
1449 ms
index.js
1515 ms
core.min.js
1517 ms
datepicker.min.js
1364 ms
jquery-ui-timepicker-addon.min.js
1455 ms
mouse.min.js
1485 ms
slider.min.js
1501 ms
controlgroup.min.js
1506 ms
checkboxradio.min.js
1514 ms
button.min.js
1493 ms
jquery-ui-sliderAccess.js
1495 ms
jquery.blockUI.min.js
1510 ms
js.cookie.min.js
1602 ms
woocommerce.min.js
1601 ms
cart-fragments.min.js
1715 ms
cb70d11b8.min.js
1555 ms
theme-addons.js
1619 ms
theme.js
1601 ms
perfect-scrollbar.min.js
1588 ms
wp-embed.min.js
1451 ms
jquery.appear.js
1451 ms
wgl_elementor_widgets.js
1442 ms
photonic-baguettebox.min.js
1563 ms
photonic-baguettebox.min.js
1576 ms
anime.min.js
1574 ms
parallax.min.js
1473 ms
jquery.paroller.min.js
1451 ms
imagesloaded.min.js
1475 ms
slick.min.js
1595 ms
jarallax.min.js
1596 ms
jarallax-video.min.js
1465 ms
elfsight-instagram-feed.js
1620 ms
wgl_elementor_sections.js
1407 ms
wgl_elementor_column.js
1452 ms
webpack.runtime.min.js
1459 ms
frontend-modules.min.js
1395 ms
waypoints.min.js
1396 ms
swiper.min.js
1434 ms
share-link.min.js
1455 ms
dialog.min.js
1458 ms
frontend.min.js
1421 ms
preloaded-modules.min.js
1406 ms
underscore.min.js
1399 ms
wp-util.min.js
1417 ms
frontend.min.js
1324 ms
jquery.validate.min.js
1414 ms
mailcheck.min.js
1401 ms
Naigation-Leaf.png
2400 ms
6a5d2a8bafcb3384ad40b37003b35352
182 ms
home-2_phone1.png
2561 ms
Hero-2-Homepage.jpg
3797 ms
Hero-3-Homepage.jpg
2613 ms
punycode.min.js
1314 ms
wpforms.js
1321 ms
stoneset-logo-2.png
1519 ms
Colour-Range-Hero-Image.jpg
2387 ms
Pour-On-scaled.jpg
3596 ms
IMG_6633-1-scaled.jpg
4681 ms
Close-up-Stoneset-Footer-Background.jpg
3242 ms
transparent.png
1477 ms
Home-slider-tree-surrounds.jpg
1569 ms
fa-solid-900.woff
1745 ms
fa-regular-400.woff
1363 ms
Flaticon.svg
1364 ms
Flaticon.woff
1361 ms
fa-brands-400.woff
1737 ms
About-Image-1-840x620.jpg
1695 ms
About-Image-3-840x620.png
1732 ms
Sydney_Observatory_07-840x620.jpg
1551 ms
stonset-driveway-840x620.jpg
1549 ms
Green-Leaf.png
1720 ms
David-Barnes-Signature-1024x310.png
1707 ms
Architect-Drawing-Home-page-600x620.jpg
1660 ms
submit-spin.svg
1529 ms
Porous-Tree.jpg
1530 ms
overlay-scale-zoom.jpg
1942 ms
blog_image-1.png
1705 ms
1962-Tuross-Heads-NSW-6mm-3mm-Charcoal-Overlay-5.JPG-small-1170x725.jpg
1871 ms
IMG_3090-1170x725.jpg
1530 ms
Pool-side-image-1170x725.jpg
1950 ms
earth-1389715_1280-1170x725.png
1740 ms
leaf-1082118_1280-1170x725.jpg
1689 ms
2279Roseville-Chase-NSW-Evergreen-Ash-1170x725.jpg
1689 ms
outside-254716_1280-1170x725.jpg
1869 ms
image-24-2.jpg
1739 ms
recaptcha__en.js
267 ms
stoneset.co.nz
2650 ms
woocommerce-smallscreen.css
213 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 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
Issues were logged in the Issues panel in Chrome Devtools
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: