Tools & Wizards About Us
stonemasonry.net.au screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

stonemasonry.net.au

Damien Rush Stone Masonry

Page Load Speed

8.7 sec in total

First Response

1.6 sec

Resources Loaded

6.5 sec

Page Rendered

584 ms

stonemasonry.net.au screenshot

About Website

Click here to check amazing Stone Masonry content. Otherwise, check out these important facts you probably never knew about stonemasonry.net.au

Visit stonemasonry.net.au

Key Findings

We analyzed Stonemasonry.net.au page load time and found that the first response time was 1.6 sec and then it took 7.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

stonemasonry.net.au performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.593

11/100

15%

TTI (Time to Interactive)

Value6.1 s

63/100

10%

Network Requests Diagram

www.stonemasonry.net.au

1594 ms

style.css

208 ms

style.min.css

406 ms

prototype.js

23 ms

scriptaculous.js

27 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 76% of them (29 requests) were addressed to the original Stonemasonry.net.au, 24% (9 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Stonemasonry.net.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.2 kB (5%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stonemasonry.net.au main page is 1.5 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 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 28.2 kB

  • Original 35.5 kB
  • After minification 34.5 kB
  • After compression 7.3 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 28.2 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 18.9 kB

  • Original 1.3 MB
  • After minification 1.3 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. Stone Masonry images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 19.0 kB

  • Original 135.0 kB
  • After minification 134.7 kB
  • After compression 116.0 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 19.0 kB or 14% of the original size.

CSS Optimization

-12%

Potential reduce by 2.0 kB

  • Original 16.8 kB
  • After minification 16.8 kB
  • After compression 14.8 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. Stonemasonry.net.au needs all CSS files to be minified and compressed as it can save up to 2.0 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (47%)

Requests Now

36

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stone Masonry. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.stonemasonry.net.au

www.stonemasonry.net.au

1594 ms

style.css

style.css

208 ms

style.min.css

style.min.css

406 ms

prototype.js

prototype.js

23 ms

scriptaculous.js

scriptaculous.js

27 ms

effects.js

effects.js

30 ms

lightbox.js

lightbox.js

406 ms

jquery.min.js

jquery.min.js

675 ms

jquery-migrate.min.js

jquery-migrate.min.js

413 ms

jquery.cycle.js

jquery.cycle.js

419 ms

wp-embed.min.js

wp-embed.min.js

417 ms

screen.css

screen.css

402 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

208 ms

builder.js

builder.js

6 ms

effects.js

effects.js

13 ms

dragdrop.js

dragdrop.js

9 ms

controls.js

controls.js

12 ms

slider.js

slider.js

11 ms

sound.js

sound.js

10 ms

lightbox.css

lightbox.css

204 ms

bg.jpg

bg.jpg

619 ms

repeater.png

repeater.png

211 ms

Eco-Outdoor-Crackenback-950x425.jpg

Eco-Outdoor-Crackenback-950x425.jpg

834 ms

Rustic-Stone-Random-Blend-950x425.jpg

Rustic-Stone-Random-Blend-950x425.jpg

824 ms

Quarry-Matador-950x425.jpg

Quarry-Matador-950x425.jpg

608 ms

Quarry-Merlot-Cranbourne-950x425.jpg

Quarry-Merlot-Cranbourne-950x425.jpg

835 ms

Eco-Outdoor-Crackenback-590x1048.jpg

Eco-Outdoor-Crackenback-590x1048.jpg

1019 ms

Stacked-Stone-1.jpg

Stacked-Stone-1.jpg

1011 ms

Sandstone-Pillar-1.jpg

Sandstone-Pillar-1.jpg

825 ms

Sandstone-Steps-1-590x393.jpg

Sandstone-Steps-1-590x393.jpg

1236 ms

Bluestone-Pitchers-1-590x393.jpg

Bluestone-Pitchers-1-590x393.jpg

1033 ms

SthLSWhiteOak1.jpg

SthLSWhiteOak1.jpg

1044 ms

Stacked-Ledgestone-Fireplace.jpg

Stacked-Ledgestone-Fireplace.jpg

1251 ms

Rustic-Stone-Random-Blend.jpg

Rustic-Stone-Random-Blend.jpg

1214 ms

Quarry-Matador.jpg

Quarry-Matador.jpg

1221 ms

Quarry-Merlot-Cranbourne.jpg

Quarry-Merlot-Cranbourne.jpg

1238 ms

double-border.png

double-border.png

1253 ms

print.css

print.css

911 ms

Accessibility Review

stonemasonry.net.au accessibility score

93

Accessibility Issues

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

stonemasonry.net.au best practices score

67

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

High

Browser errors were logged to the console

SEO Factors

stonemasonry.net.au SEO score

69

Search Engine Optimization Advices

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 Stonemasonry.net.au 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 Stonemasonry.net.au 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

stonemasonry.net.au

Open Graph description is not detected on the main page of Stone Masonry. 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: