Tools & Wizards About Us
yardart.co.nz screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

yardart.co.nz

Yard Art Garden Ornaments ::. Concrete Ornaments and Moulds

Page Load Speed

8.8 sec in total

First Response

674 ms

Resources Loaded

7.9 sec

Page Rendered

155 ms

yardart.co.nz screenshot

About Website

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.nz

Key Findings

We analyzed Yardart.co.nz page load time and found that the first response time was 674 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.

Performance Metrics

yardart.co.nz performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

gardenornaments.co.nz

674 ms

www.gardenornaments.co.nz

1224 ms

animate.min.css

422 ms

font-awesome.min.css

635 ms

normalize.min.css

647 ms

Our browser made a total of 99 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 and 2% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Gardenornaments.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 164.1 kB (20%)

Content Size

834.4 kB

After Optimization

670.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yardart.co.nz main page is 834.4 kB. 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 438.3 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 125.6 kB

  • Original 138.1 kB
  • After minification 138.1 kB
  • After compression 12.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 125.6 kB or 91% of the original size.

Image Optimization

-3%

Potential reduce by 13.8 kB

  • Original 438.3 kB
  • After minification 424.5 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.

JavaScript Optimization

-5%

Potential reduce by 7.7 kB

  • Original 165.6 kB
  • After minification 165.6 kB
  • After compression 157.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. This website has mostly compressed JavaScripts.

CSS Optimization

-18%

Potential reduce by 17.0 kB

  • Original 92.3 kB
  • After minification 92.2 kB
  • After compression 75.3 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 needs all CSS files to be minified and compressed as it can save up to 17.0 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 84 (90%)

Requests Now

93

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 93 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 40 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

gardenornaments.co.nz

gardenornaments.co.nz

674 ms

www.gardenornaments.co.nz

www.gardenornaments.co.nz

1224 ms

animate.min.css

animate.min.css

422 ms

font-awesome.min.css

font-awesome.min.css

635 ms

normalize.min.css

normalize.min.css

647 ms

normalize_buttons.min.css

normalize_buttons.min.css

648 ms

styles.css

styles.css

656 ms

menu.css

menu.css

638 ms

product.css

product.css

655 ms

search.css

search.css

845 ms

webcommand.css

webcommand.css

851 ms

hero_image.css

hero_image.css

857 ms

menu_button.css

menu_button.css

858 ms

footer_menu.css

footer_menu.css

866 ms

product_promotion.css

product_promotion.css

867 ms

jquery.js

jquery.js

1267 ms

jquery.noconflict.js

jquery.noconflict.js

1061 ms

jquery-migrate.js

jquery-migrate.js

1068 ms

jquery.lib.min.js

jquery.lib.min.js

1069 ms

dhtml.min.js

dhtml.min.js

1076 ms

sweet-alert.min.js

sweet-alert.min.js

1077 ms

sweet-alert.prodev.min.js

sweet-alert.prodev.min.js

1272 ms

sweet-alert.prodev_functions.min.js

sweet-alert.prodev_functions.min.js

1278 ms

animate.min.js

animate.min.js

1279 ms

pub_templates_page_vars.min.js

pub_templates_page_vars.min.js

1286 ms

fancy_menu.js

fancy_menu.js

1287 ms

header_scroll.js

header_scroll.js

1477 ms

search_input.js

search_input.js

1482 ms

handleFormFields.min.js

handleFormFields.min.js

1489 ms

mmenu_starter.min.js

mmenu_starter.min.js

1490 ms

widget_contact_item_vars.min.css

widget_contact_item_vars.min.css

1495 ms

widget_contact_item.min.css

widget_contact_item.min.css

1495 ms

widget_vertical_contact.min.css

widget_vertical_contact.min.css

1685 ms

jquery.mmenu.all.min.css

jquery.mmenu.all.min.css

1691 ms

slideshow.min.css

slideshow.min.css

1697 ms

slideshow-docs.min.css

slideshow-docs.min.css

1912 ms

photoswipe.min.css

photoswipe.min.css

1705 ms

default-skin.min.css

default-skin.min.css

1508 ms

photoswipe_prodev_styles.min.css

photoswipe_prodev_styles.min.css

1482 ms

mobile_user_styles.min.css

mobile_user_styles.min.css

1275 ms

jquery-ui.min.css

jquery-ui.min.css

1279 ms

AutoComplete_jQuery_UI_Library.min.css

AutoComplete_jQuery_UI_Library.min.css

1280 ms

autocomplete_search.css

autocomplete_search.css

1280 ms

bootstrap.min.css

bootstrap.min.css

1461 ms

bootstrap.min.css

bootstrap.min.css

1467 ms

bootstrap.min.css

bootstrap.min.css

1285 ms

sweet-alert.min.css

sweet-alert.min.css

1281 ms

products.css

products.css

1279 ms

slick.min.css

slick.min.css

1279 ms

stacktable.min.css

stacktable.min.css

1460 ms

jQuery.mobile_stacktable.min.css

jQuery.mobile_stacktable.min.css

1469 ms

back_to_top.min.css

back_to_top.min.css

1279 ms

select_colorselector.min.css

select_colorselector.min.css

1275 ms

fonts.css

fonts.css

1279 ms

btbuttons.css

btbuttons.css

1273 ms

window.event.min.js

window.event.min.js

1558 ms

jquery.mmenu.all.min.js

jquery.mmenu.all.min.js

1370 ms

uikit.min.js

uikit.min.js

1512 ms

slideshow.min.js

slideshow.min.js

1358 ms

slideshow-fx.min.js

slideshow-fx.min.js

1356 ms

scrollspy.min.js

scrollspy.min.js

1350 ms

jquery.actual.min.js

jquery.actual.min.js

1467 ms

photoswipe.min.js

photoswipe.min.js

1305 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

1318 ms

photo_swipe_dimensions.min.js

photo_swipe_dimensions.min.js

1312 ms

photo_swipe_pattern.min.js

photo_swipe_pattern.min.js

1312 ms

photo_swipe_img_pattern.min.js

photo_swipe_img_pattern.min.js

1459 ms

photoswipe.initPhotoSwipeFromDOM.min.js

photoswipe.initPhotoSwipeFromDOM.min.js

1473 ms

photo_swipe_prodev.min.js

photo_swipe_prodev.min.js

1285 ms

bgimage_spacer.min.js

bgimage_spacer.min.js

1280 ms

jquery-ui.min.js

jquery-ui.min.js

1280 ms

AutoComplete_UI_Get_Binds.min.js

AutoComplete_UI_Get_Binds.min.js

1271 ms

AutoComplete_UI_Position_Tracker.min.js

AutoComplete_UI_Position_Tracker.min.js

1459 ms

AutoComplete_Focus_Field.min.js

AutoComplete_Focus_Field.min.js

1283 ms

AutoComplete_JSON_Config_Extractor.min.js

AutoComplete_JSON_Config_Extractor.min.js

1278 ms

AutoComplete_Convert_Results.min.js

AutoComplete_Convert_Results.min.js

1273 ms

AutoComplete_UI_Create_Request.min.js

AutoComplete_UI_Create_Request.min.js

1277 ms

AutoComplete_UI_Create_Widget.min.js

AutoComplete_UI_Create_Widget.min.js

1271 ms

autocomplete.product_autocomplete.min.js

autocomplete.product_autocomplete.min.js

1457 ms

slick.min.js

slick.min.js

1285 ms

slick-starter.min.js

slick-starter.min.js

1279 ms

jQuery.mobile_stacktable.min.js

jQuery.mobile_stacktable.min.js

1275 ms

prodev_stacktable.lib.min.js

prodev_stacktable.lib.min.js

1276 ms

prodev_stacktable_init.min.js

prodev_stacktable_init.min.js

1272 ms

jquery.resize.min.js

jquery.resize.min.js

1458 ms

back_to_top.min.js

back_to_top.min.js

1287 ms

css

css

34 ms

css

css

52 ms

yardart_branding.png

yardart_branding.png

1189 ms

noimage_icon.png

noimage_icon.png

2458 ms

securityImageImage.php

securityImageImage.php

1291 ms

card1.png

card1.png

1265 ms

card2.png

card2.png

1381 ms

card3.png

card3.png

1186 ms

prodev_egg.png

prodev_egg.png

1186 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

18 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1529 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1618 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

30 ms

Accessibility Review

yardart.co.nz accessibility score

93

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

yardart.co.nz best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

yardart.co.nz SEO score

88

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: