Tools & Wizards About Us
floreydental.com.au screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

floreydental.com.au

Florey Dental Care, Quality Dentistry in Belconnen 02 6258 2255

Page Load Speed

2.2 sec in total

First Response

794 ms

Resources Loaded

1.3 sec

Page Rendered

76 ms

floreydental.com.au screenshot

About Website

Visit floreydental.com.au now to see the best up-to-date Florey Dental content and also check out these interesting facts you probably never knew about floreydental.com.au

Florey Dental surgery is proud to offer quality dental care in Belconnen, Canberra. We see emergency dental patients daily as well as our regular patients.

Visit floreydental.com.au

Key Findings

We analyzed Floreydental.com.au page load time and found that the first response time was 794 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

floreydental.com.au performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value280 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.05

99/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

www.floreydental.com.au

794 ms

originTrials.41d7301a.bundle.min.js

42 ms

minified.js

51 ms

focus-within-polyfill.js

45 ms

polyfill.min.js

112 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Floreydental.com.au, 42% (15 requests) were made to Static.parastorage.com and 33% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (794 ms) belongs to the original domain Floreydental.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 285.8 kB (45%)

Content Size

631.9 kB

After Optimization

346.1 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-77%

Potential reduce by 283.0 kB

  • Original 367.0 kB
  • After minification 365.3 kB
  • After compression 84.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 283.0 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 36.2 kB
  • After minification 36.2 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. Florey Dental images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 228.7 kB
  • After minification 228.7 kB
  • After compression 225.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.

Requests Breakdown

Number of requests can be reduced by 11 (52%)

Requests Now

21

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.floreydental.com.au

www.floreydental.com.au

794 ms

originTrials.41d7301a.bundle.min.js

originTrials.41d7301a.bundle.min.js

42 ms

minified.js

minified.js

51 ms

focus-within-polyfill.js

focus-within-polyfill.js

45 ms

polyfill.min.js

polyfill.min.js

112 ms

thunderbolt-commons.ec68bee9.bundle.min.js

thunderbolt-commons.ec68bee9.bundle.min.js

34 ms

main.f286c407.bundle.min.js

main.f286c407.bundle.min.js

34 ms

lodash.min.js

lodash.min.js

33 ms

react.production.min.js

react.production.min.js

31 ms

react-dom.production.min.js

react-dom.production.min.js

36 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

34 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

35 ms

Florey%20Dental%20Care%20half%20white.png

Florey%20Dental%20Care%20half%20white.png

246 ms

bundle.min.js

bundle.min.js

47 ms

floreydental-general-dentistry1-202x113.jpg

floreydental-general-dentistry1-202x113.jpg

140 ms

floreydental-dental-implants1-202x113.jpg

floreydental-dental-implants1-202x113.jpg

140 ms

floreydental-cosmetic-dentistry1-202x113.jpg

floreydental-cosmetic-dentistry1-202x113.jpg

147 ms

floreydental-root-canal-treatment1-202x113.jpg

floreydental-root-canal-treatment1-202x113.jpg

147 ms

68 ms

9 ms

13 ms

12 ms

14 ms

16 ms

68 ms

71 ms

70 ms

71 ms

68 ms

92 ms

opensans-regular-webfont.woff

opensans-regular-webfont.woff

6 ms

opensans-bold-webfont.woff

opensans-bold-webfont.woff

9 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

26 ms

deprecation-style.v5.css

deprecation-style.v5.css

11 ms

right-arrow.svg

right-arrow.svg

11 ms

Accessibility Review

floreydental.com.au accessibility score

88

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

floreydental.com.au best practices score

92

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

Page has valid source maps

SEO Factors

floreydental.com.au SEO score

100

Search Engine Optimization Advices

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

floreydental.com.au

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