Tools & Wizards About Us
futureshade.com.au screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

futureshade.com.au

Future Shade | Shade Sails For Melbourne | Waterproof Shade Sails For Outdoors

Page Load Speed

16.7 sec in total

First Response

3.5 sec

Resources Loaded

12.9 sec

Page Rendered

288 ms

futureshade.com.au screenshot

About Website

Welcome to futureshade.com.au homepage info - get ready to check Future Shade best content right away, or after learning these important things about futureshade.com.au

Future Shade offers shade sails, cantaport, outdoor shade umbrella, custom shade sails in Melbourne to create fully functional outdoor spaces

Visit futureshade.com.au

Key Findings

We analyzed Futureshade.com.au page load time and found that the first response time was 3.5 sec and then it took 13.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

futureshade.com.au performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value1,200 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.583

11/100

15%

TTI (Time to Interactive)

Value10.5 s

24/100

10%

Network Requests Diagram

futureshade.com.au

3490 ms

magnific_popup.css

663 ms

animate.css

691 ms

slick.min.css

702 ms

magnific-popup.min.css

701 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 62% of them (53 requests) were addressed to the original Futureshade.com.au, 35% (30 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (6.1 sec) belongs to the original domain Futureshade.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 326.2 kB (44%)

Content Size

740.9 kB

After Optimization

414.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Futureshade.com.au main page is 740.9 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. 55% of websites need less resources to load. HTML takes 366.3 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 322.3 kB

  • Original 366.3 kB
  • After minification 358.0 kB
  • After compression 44.0 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 322.3 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 29.1 kB
  • After minification 29.1 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. Future Shade images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.1 kB

  • Original 306.5 kB
  • After minification 306.5 kB
  • After compression 303.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.

CSS Optimization

-2%

Potential reduce by 754 B

  • Original 39.0 kB
  • After minification 39.0 kB
  • After compression 38.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. Futureshade.com.au has all CSS files already compressed.

Requests Breakdown

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

Requests Now

53

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

futureshade.com.au

futureshade.com.au

3490 ms

magnific_popup.css

magnific_popup.css

663 ms

animate.css

animate.css

691 ms

slick.min.css

slick.min.css

702 ms

magnific-popup.min.css

magnific-popup.min.css

701 ms

frontend.css

frontend.css

697 ms

app.min.css

app.min.css

796 ms

style.min.css

style.min.css

823 ms

style.css

style.css

974 ms

mailin-front.css

mailin-front.css

1531 ms

jquery.min.js

jquery.min.js

1840 ms

jquery-migrate.min.js

jquery-migrate.min.js

1820 ms

mailin-front.js

mailin-front.js

2831 ms

et-core-unified-241527.min.css

et-core-unified-241527.min.css

2846 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

2735 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

2740 ms

slick.min.js

slick.min.js

3351 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

3679 ms

react.min.js

react.min.js

3713 ms

react-dom.min.js

react-dom.min.js

3719 ms

frontend.js

frontend.js

3728 ms

scripts.min.js

scripts.min.js

3747 ms

smoothscroll.js

smoothscroll.js

4087 ms

jquery.fitvids.js

jquery.fitvids.js

4380 ms

easypiechart.js

easypiechart.js

4587 ms

salvattore.js

salvattore.js

3974 ms

hooks.min.js

hooks.min.js

4624 ms

i18n.min.js

i18n.min.js

4647 ms

app.min.js

app.min.js

4774 ms

frontend-bundle.min.js

frontend-bundle.min.js

4777 ms

jquery.lazy.min.js

jquery.lazy.min.js

5083 ms

jquery.lazy.iframe.min.js

jquery.lazy.iframe.min.js

5319 ms

jquery.lazy.vimeo.min.js

jquery.lazy.vimeo.min.js

5323 ms

jquery.lazy.youtube.min.js

jquery.lazy.youtube.min.js

5330 ms

jquery.lazy.picture.min.js

jquery.lazy.picture.min.js

5430 ms

jquery.lazy.av.min.js

jquery.lazy.av.min.js

5466 ms

jquery.lazy.ajax.min.js

jquery.lazy.ajax.min.js

5753 ms

jquery.lazy.script.min.js

jquery.lazy.script.min.js

5988 ms

jquery.lazy.noop.min.js

jquery.lazy.noop.min.js

5980 ms

dpsb-init.min.js

dpsb-init.min.js

6001 ms

common.js

common.js

6104 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

5700 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

5779 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

5814 ms

typed.min.js

typed.min.js

5874 ms

frontend.min.js

frontend.min.js

5330 ms

sticky-elements.js

sticky-elements.js

4637 ms

gtm.js

gtm.js

171 ms

hotjar-3603138.js

hotjar-3603138.js

203 ms

et-divi-dynamic-tb-240334-tb-240584-241527-late.css

et-divi-dynamic-tb-240334-tb-240584-241527-late.css

4122 ms

preloader.gif

preloader.gif

4253 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVQ.woff

20 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

28 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

36 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

45 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

47 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

46 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

47 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

47 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

43 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

54 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

56 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

55 ms

pxiByp8kv8JHgFVrLGT9Z1JlEw.woff

pxiByp8kv8JHgFVrLGT9Z1JlEw.woff

55 ms

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

56 ms

pxiEyp8kv8JHgFVrJJnedA.woff

pxiEyp8kv8JHgFVrJJnedA.woff

56 ms

pxiEyp8kv8JHgFVrJJnedw.ttf

pxiEyp8kv8JHgFVrJJnedw.ttf

57 ms

pxiByp8kv8JHgFVrLDz8Z1JlEw.woff

pxiByp8kv8JHgFVrLDz8Z1JlEw.woff

58 ms

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

57 ms

pxiByp8kv8JHgFVrLFj_Z1JlEw.woff

pxiByp8kv8JHgFVrLFj_Z1JlEw.woff

58 ms

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

58 ms

pxiGyp8kv8JHgFVrLPTufntG.woff

pxiGyp8kv8JHgFVrLPTufntG.woff

58 ms

pxiGyp8kv8JHgFVrLPTufntF.ttf

pxiGyp8kv8JHgFVrLPTufntF.ttf

59 ms

pxiByp8kv8JHgFVrLEj6Z1JlEw.woff

pxiByp8kv8JHgFVrLEj6Z1JlEw.woff

59 ms

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

60 ms

pxiByp8kv8JHgFVrLCz7Z1JlEw.woff

pxiByp8kv8JHgFVrLCz7Z1JlEw.woff

61 ms

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

60 ms

pxiByp8kv8JHgFVrLDD4Z1JlEw.woff

pxiByp8kv8JHgFVrLDD4Z1JlEw.woff

60 ms

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

79 ms

pxiByp8kv8JHgFVrLBT5Z1JlEw.woff

pxiByp8kv8JHgFVrLBT5Z1JlEw.woff

79 ms

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

80 ms

modules.woff

modules.woff

4728 ms

FS_treehouse-learing-logo-img-220x94-1.jpg

FS_treehouse-learing-logo-img-220x94-1.jpg

685 ms

FS_billanook-logo-img-220x110-1.jpg

FS_billanook-logo-img-220x110-1.jpg

698 ms

future-logo_retina.png

future-logo_retina.png

675 ms

Accessibility Review

futureshade.com.au accessibility score

86

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

futureshade.com.au 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

futureshade.com.au SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

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 Futureshade.com.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 Futureshade.com.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

futureshade.com.au

Open Graph data is detected on the main page of Future Shade. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: