8.9 sec in total
755 ms
7.9 sec
153 ms
Click here to check amazing Yard Art content. Otherwise, check out these important facts you probably never knew about yardart.co.nz
Yard Art produces an exciting range of concrete garden ornaments, created to enhance your garden, patio, deck, foyer or home. From elegant modern sculptures through to traditional garden ornaments, we...
Visit yardart.co.nzWe analyzed Yardart.co.nz page load time and found that the first response time was 755 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
yardart.co.nz performance score
name
value
score
weighting
Value9.1 s
0/100
10%
Value9.1 s
1/100
25%
Value13.8 s
1/100
10%
Value100 ms
98/100
30%
Value0.05
99/100
15%
Value11.0 s
21/100
10%
755 ms
1268 ms
427 ms
608 ms
620 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Yardart.co.nz, 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Gardenornaments.co.nz.
Page size can be reduced by 368.1 kB (15%)
2.4 MB
2.0 MB
In fact, the total size of Yardart.co.nz main page is 2.4 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. 50% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 194.4 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 194.4 kB or 93% of the original size.
Potential reduce by 165.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. Yard Art images are well optimized though.
Potential reduce by 3.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 5.0 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. Yardart.co.nz has all CSS files already compressed.
Number of requests can be reduced by 83 (82%)
101
18
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yard Art. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 39 to 1 for CSS and as a result speed up the page load time.
gardenornaments.co.nz
755 ms
www.gardenornaments.co.nz
1268 ms
animate.min.css
427 ms
font-awesome.min.css
608 ms
normalize.min.css
620 ms
normalize_buttons.min.css
627 ms
styles.css
628 ms
menu.css
637 ms
product.css
641 ms
search.css
809 ms
webcommand.css
824 ms
hero_image.css
836 ms
menu_button.css
836 ms
footer_menu.css
847 ms
product_promotion.css
863 ms
jquery.js
1211 ms
jquery.noconflict.js
1026 ms
jquery-migrate.js
1038 ms
jquery.lib.min.js
1038 ms
dhtml.min.js
1057 ms
sweet-alert.min.js
1083 ms
sweet-alert.prodev.min.js
1227 ms
sweet-alert.prodev_functions.min.js
1242 ms
animate.min.js
1242 ms
pub_templates_page_vars.min.js
1266 ms
fancy_menu.js
1275 ms
header_scroll.js
1399 ms
search_input.js
1426 ms
handleFormFields.min.js
1447 ms
mmenu_starter.min.js
1445 ms
widget_contact_item_vars.min.css
1280 ms
widget_contact_item.min.css
1289 ms
widget_vertical_contact.min.css
1404 ms
jquery.mmenu.all.min.css
1433 ms
slideshow.min.css
1455 ms
slideshow-docs.min.css
1665 ms
photoswipe.min.css
1490 ms
default-skin.min.css
1498 ms
photoswipe_prodev_styles.min.css
1388 ms
mobile_user_styles.min.css
1240 ms
jquery-ui.min.css
1256 ms
AutoComplete_jQuery_UI_Library.min.css
1290 ms
autocomplete_search.css
1294 ms
bootstrap.min.css
1381 ms
bootstrap.min.css
1411 ms
bootstrap.min.css
1275 ms
sweet-alert.min.css
1261 ms
products.css
1289 ms
slick.min.css
1298 ms
stacktable.min.css
1370 ms
jQuery.mobile_stacktable.min.css
1396 ms
back_to_top.min.css
1260 ms
fonts.css
1247 ms
btbuttons.css
1292 ms
window.event.min.js
1675 ms
jquery.mmenu.all.min.js
1650 ms
uikit.min.js
1534 ms
slideshow.min.js
1507 ms
slideshow-fx.min.js
1491 ms
scrollspy.min.js
1491 ms
jquery.actual.min.js
1467 ms
photoswipe.min.js
1458 ms
photoswipe-ui-default.min.js
1334 ms
photo_swipe_dimensions.min.js
1308 ms
photo_swipe_pattern.min.js
1360 ms
photo_swipe_img_pattern.min.js
1361 ms
photoswipe.initPhotoSwipeFromDOM.min.js
1336 ms
photo_swipe_prodev.min.js
1373 ms
bgimage_spacer.min.js
1300 ms
jquery-ui.min.js
1273 ms
AutoComplete_UI_Get_Binds.min.js
1307 ms
AutoComplete_UI_Position_Tracker.min.js
1281 ms
AutoComplete_Focus_Field.min.js
1313 ms
AutoComplete_JSON_Config_Extractor.min.js
1260 ms
AutoComplete_Convert_Results.min.js
1273 ms
AutoComplete_UI_Create_Request.min.js
1249 ms
AutoComplete_UI_Create_Widget.min.js
1309 ms
autocomplete.product_autocomplete.min.js
1276 ms
slick.min.js
1304 ms
slick-starter.min.js
1263 ms
jQuery.mobile_stacktable.min.js
1279 ms
prodev_stacktable.lib.min.js
1250 ms
prodev_stacktable_init.min.js
1312 ms
jquery.resize.js
1279 ms
back_to_top.min.js
1292 ms
css
28 ms
css
41 ms
yardart_branding.png
1151 ms
securityImageImage.php
1266 ms
card1.png
1202 ms
card2.png
1230 ms
card3.png
877 ms
prodev_egg.png
888 ms
nut_house.jpg
1352 ms
on_books.jpg
1002 ms
cat_tall.jpg
1711 ms
witch_planter.jpg
1927 ms
gnome_resting_on_elbows.jpg
1482 ms
log_planter.jpg
1934 ms
scroll_planter.jpg
1826 ms
tortoise_on_grass.jpg
1754 ms
angel_wall_plaque.jpg
1807 ms
stand_round_lge.jpg
1846 ms
fontawesome-webfont.woff
1887 ms
fontawesome-webfont.woff
1961 ms
yardart.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-hidden="true"] elements contain focusable descendents
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
Links do not have a discernible name
yardart.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
yardart.co.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Yardart.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 Yardart.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.
yardart.co.nz
Open Graph description is not detected on the main page of Yard Art. 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: