Tools & Wizards About Us
florenceazdental.com screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

florenceazdental.com

Florence Dentist, Dr. Jason Whetten

Page Load Speed

1.8 sec in total

First Response

331 ms

Resources Loaded

1.3 sec

Page Rendered

220 ms

florenceazdental.com screenshot

About Website

Welcome to florenceazdental.com homepage info - get ready to check Florence Azdental best content right away, or after learning these important things about florenceazdental.com

Florence Dentist, Dr. Jason Whetten is a professional dedicated to Excellence in General, Family, & Cosmetic Dentistry such as Cleanings & Prevention, Restorations, Periodontal Disease & many other de...

Visit florenceazdental.com

Key Findings

We analyzed Florenceazdental.com page load time and found that the first response time was 331 ms and then it took 1.5 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

florenceazdental.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.1 s

64/100

10%

Network Requests Diagram

florenceazdental.com

331 ms

bootstrap.min.css

37 ms

font-awesome.min.css

42 ms

css

73 ms

css

110 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 27% of them (16 requests) were addressed to the original Florenceazdental.com, 46% (27 requests) were made to Styles.prosites.com and 12% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (413 ms) relates to the external source Webstats.prosites.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 287.1 kB (32%)

Content Size

907.3 kB

After Optimization

620.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Florenceazdental.com main page is 907.3 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. 60% of websites need less resources to load. Javascripts take 383.0 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 79.4 kB

  • Original 93.6 kB
  • After minification 71.2 kB
  • After compression 14.1 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. This page needs HTML code to be minified as it can gain 22.4 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 79.4 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 25 B

  • Original 346.8 kB
  • After minification 346.8 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. Florence Azdental images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 169.8 kB

  • Original 383.0 kB
  • After minification 348.0 kB
  • After compression 213.3 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 169.8 kB or 44% of the original size.

CSS Optimization

-45%

Potential reduce by 37.9 kB

  • Original 83.9 kB
  • After minification 73.1 kB
  • After compression 46.0 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. Florenceazdental.com needs all CSS files to be minified and compressed as it can save up to 37.9 kB or 45% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (78%)

Requests Now

40

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

florenceazdental.com

florenceazdental.com

331 ms

bootstrap.min.css

bootstrap.min.css

37 ms

font-awesome.min.css

font-awesome.min.css

42 ms

css

css

73 ms

css

css

110 ms

font-awesome.min.css

font-awesome.min.css

143 ms

slick.css

slick.css

33 ms

slick-theme.css

slick-theme.css

53 ms

owl.carousel.css

owl.carousel.css

152 ms

jquery.fancybox.css

jquery.fancybox.css

153 ms

video-js.css

video-js.css

153 ms

pagecontrols.css

pagecontrols.css

38 ms

stylesheet.css

stylesheet.css

51 ms

jquery-migrate-1.1.0.min.js

jquery-migrate-1.1.0.min.js

50 ms

slick.css

slick.css

45 ms

bootstrap.min.css

bootstrap.min.css

47 ms

navigation.css

navigation.css

68 ms

pagecontrols.css

pagecontrols.css

64 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

65 ms

default.css

default.css

59 ms

jquery-migrate-1.1.0.min.js

jquery-migrate-1.1.0.min.js

58 ms

stylesheet.css

stylesheet.css

58 ms

slick-theme.css

slick-theme.css

60 ms

bootstrap.min.js

bootstrap.min.js

80 ms

owl.carousel.min.js

owl.carousel.min.js

168 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

168 ms

video.js

video.js

245 ms

scrolling-nav.js

scrolling-nav.js

167 ms

jquery.easing.min.js

jquery.easing.min.js

166 ms

Functions.js

Functions.js

164 ms

RWDUtil.js

RWDUtil.js

239 ms

functions.js

functions.js

37 ms

placeholders.min.js

placeholders.min.js

35 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

43 ms

slick.js

slick.js

37 ms

placeholders.min.js

placeholders.min.js

17 ms

functions.js

functions.js

13 ms

sm-core-css.css

sm-core-css.css

230 ms

video-js.css

video-js.css

220 ms

MicrosoftAjaxWebForms.js

MicrosoftAjaxWebForms.js

20 ms

WebForms.js

WebForms.js

25 ms

MicrosoftAjax.js

MicrosoftAjax.js

24 ms

header-bg.jpg

header-bg.jpg

36 ms

cover1.jpg

cover1.jpg

53 ms

blue-bg.jpg

blue-bg.jpg

52 ms

content-bg.jpg

content-bg.jpg

51 ms

8vIU7ww63mVu7gtR-kwKxNvkNOjw-tbnfY3lCA.ttf

8vIU7ww63mVu7gtR-kwKxNvkNOjw-tbnfY3lCA.ttf

168 ms

8vIU7ww63mVu7gtR-kwKxNvkNOjw-jHgfY3lCA.ttf

8vIU7ww63mVu7gtR-kwKxNvkNOjw-jHgfY3lCA.ttf

178 ms

daaCSScvJGqLYhG8nNt8KPPswUAPni7TTMk.ttf

daaCSScvJGqLYhG8nNt8KPPswUAPni7TTMk.ttf

170 ms

daaHSScvJGqLYhG8nNt8KPPswUAPniZoadlESTQ.ttf

daaHSScvJGqLYhG8nNt8KPPswUAPniZoadlESTQ.ttf

171 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

168 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

170 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

216 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

152 ms

testimonial-bg.jpg

testimonial-bg.jpg

116 ms

footer-bg.jpg

footer-bg.jpg

115 ms

dg4n_p3sv6gCJkwzT6RXiJwt.ttf

dg4n_p3sv6gCJkwzT6RXiJwt.ttf

128 ms

matomo.js

matomo.js

413 ms

Whetten_Final.gif

Whetten_Final.gif

295 ms

Accessibility Review

florenceazdental.com accessibility score

87

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

Best Practices

florenceazdental.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

florenceazdental.com SEO score

93

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

florenceazdental.com

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