Tools & Wizards About Us
williamsfloristweddings.com.au screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

williamsfloristweddings.com.au

Flower Arrangements, Bouquets and Gift Baskets | Williams Weddings Florist Oakleigh

Page Load Speed

6.6 sec in total

First Response

1.9 sec

Resources Loaded

4.6 sec

Page Rendered

81 ms

williamsfloristweddings.com.au screenshot

About Website

Welcome to williamsfloristweddings.com.au homepage info - get ready to check Williams Florist Weddings best content right away, or after learning these important things about williamsfloristweddings.com.au

Williams Oakleigh Florist has been operating for the past 75 years in Oakleigh and servicing South Oakleigh, Oakleigh East, Mount Waverley, Armidale, Huntingdale, Bentleigh, Bentleigh East, Carnegie, ...

Visit williamsfloristweddings.com.au

Key Findings

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

Performance Metrics

williamsfloristweddings.com.au performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.324

35/100

15%

TTI (Time to Interactive)

Value8.5 s

37/100

10%

Network Requests Diagram

williamsfloristweddings.com.au

1895 ms

js

57 ms

css

23 ms

css

40 ms

style.css

427 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 79% of them (45 requests) were addressed to the original Williamsfloristweddings.com.au, 11% (6 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Williamsfloristweddings.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 69.3 kB (7%)

Content Size

998.9 kB

After Optimization

929.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Williamsfloristweddings.com.au main page is 998.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. 65% of websites need less resources to load. Images take 591.4 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 50.3 kB

  • Original 65.2 kB
  • After minification 64.4 kB
  • After compression 14.8 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 50.3 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 4.7 kB

  • Original 591.4 kB
  • After minification 586.7 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. Williams Florist Weddings images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 7.2 kB

  • Original 290.5 kB
  • After minification 290.5 kB
  • After compression 283.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

-14%

Potential reduce by 7.0 kB

  • Original 51.8 kB
  • After minification 51.8 kB
  • After compression 44.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. Williamsfloristweddings.com.au needs all CSS files to be minified and compressed as it can save up to 7.0 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (65%)

Requests Now

49

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

williamsfloristweddings.com.au

williamsfloristweddings.com.au

1895 ms

js

js

57 ms

css

css

23 ms

css

css

40 ms

style.css

style.css

427 ms

media.css

media.css

432 ms

photoMosaic.css

photoMosaic.css

433 ms

prettyPhoto.css

prettyPhoto.css

434 ms

styles.css

styles.css

434 ms

settings.css

settings.css

435 ms

captions.css

captions.css

642 ms

jquery.photoMosaic.js

jquery.photoMosaic.js

1088 ms

jquery.js

jquery.js

1080 ms

jquery-migrate.min.js

jquery-migrate.min.js

650 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

871 ms

jquery.form.min.js

jquery.form.min.js

450 ms

scripts.js

scripts.js

651 ms

modernizr.js

modernizr.js

658 ms

jquery.carouFredSel-6.2.1-packed.js

jquery.carouFredSel-6.2.1-packed.js

671 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

867 ms

imagesLoaded.js

imagesLoaded.js

873 ms

jquery.isotope.min.js

jquery.isotope.min.js

879 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

886 ms

jquery.fitvids.js

jquery.fitvids.js

1088 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

1089 ms

jquery.placeholder.js

jquery.placeholder.js

1089 ms

gmap.js

gmap.js

1093 ms

jquery.ddslick.min.js

jquery.ddslick.min.js

1094 ms

jquery.infinitescroll.min.js

jquery.infinitescroll.min.js

1104 ms

main.js

main.js

1305 ms

js

js

79 ms

all.css

all.css

1095 ms

custom.css

custom.css

1104 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

219 ms

analytics.js

analytics.js

26 ms

bg.jpg

bg.jpg

218 ms

logo.png

logo.png

219 ms

new-slides-4.jpg

new-slides-4.jpg

858 ms

slide3.jpg

slide3.jpg

1073 ms

slide1-new.jpg

slide1-new.jpg

646 ms

slide4.jpg

slide4.jpg

1036 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

42 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

42 ms

XLYgIZbkc4JPUL5CVArUVL0ntnAOTQ.ttf

XLYgIZbkc4JPUL5CVArUVL0ntnAOTQ.ttf

43 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

622 ms

collect

collect

56 ms

loader.gif

loader.gif

334 ms

timer.png

timer.png

552 ms

mobile_menu_bg.png

mobile_menu_bg.png

760 ms

bullet.png

bullet.png

219 ms

ls_prev.png

ls_prev.png

218 ms

ls_next.png

ls_next.png

220 ms

shadow-top.png

shadow-top.png

220 ms

shadow-bottom.png

shadow-bottom.png

219 ms

Accessibility Review

williamsfloristweddings.com.au accessibility score

77

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

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

williamsfloristweddings.com.au best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

williamsfloristweddings.com.au SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

williamsfloristweddings.com.au

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