Tools & Wizards About Us
mclemorefamilydental.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

mclemorefamilydental.com

Clarkston Dentist | Aaron McLemore, DMD | Family Dental

Page Load Speed

3.6 sec in total

First Response

358 ms

Resources Loaded

3 sec

Page Rendered

283 ms

mclemorefamilydental.com screenshot

About Website

Click here to check amazing Mc Lemore Family Dental content. Otherwise, check out these important facts you probably never knew about mclemorefamilydental.com

Clarkston dentist, Aaron McLemore, DMD is a dental professional dedicated to general, family, and cosmetic dentistry with services including dental exams, dental makeovers, teeth whitening, veneers, c...

Visit mclemorefamilydental.com

Key Findings

We analyzed Mclemorefamilydental.com page load time and found that the first response time was 358 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

mclemorefamilydental.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

1/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.214

58/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

mclemorefamilydental.com

358 ms

bootstrap.min.css

247 ms

css

18 ms

css

31 ms

animate.min.css

144 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 31% of them (27 requests) were addressed to the original Mclemorefamilydental.com, 24% (21 requests) were made to Styles.prosites.com and 16% (14 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Analytics.prosites.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 195.9 kB (11%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mclemorefamilydental.com main page is 1.7 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 41.5 kB

  • Original 55.0 kB
  • After minification 46.4 kB
  • After compression 13.5 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 8.6 kB, which is 16% 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 41.5 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 19.2 kB

  • Original 1.3 MB
  • After minification 1.2 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. Mc Lemore Family Dental images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 100.9 kB

  • Original 335.0 kB
  • After minification 332.5 kB
  • After compression 234.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 100.9 kB or 30% of the original size.

CSS Optimization

-44%

Potential reduce by 34.2 kB

  • Original 78.5 kB
  • After minification 69.9 kB
  • After compression 44.2 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. Mclemorefamilydental.com needs all CSS files to be minified and compressed as it can save up to 34.2 kB or 44% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (74%)

Requests Now

53

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mc Lemore Family 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 27 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

mclemorefamilydental.com

mclemorefamilydental.com

358 ms

bootstrap.min.css

bootstrap.min.css

247 ms

css

css

18 ms

css

css

31 ms

animate.min.css

animate.min.css

144 ms

owl.carousel.css

owl.carousel.css

145 ms

sm-core-css.css

sm-core-css.css

144 ms

video-js.css

video-js.css

172 ms

jquery.fancybox.css

jquery.fancybox.css

208 ms

plugins.css

plugins.css

211 ms

flexslider.css

flexslider.css

79 ms

pagecontrols.css

pagecontrols.css

79 ms

navigation.css

navigation.css

37 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

45 ms

jquery-migrate-1.1.0.min.js

jquery-migrate-1.1.0.min.js

42 ms

d-tect.js

d-tect.js

207 ms

navigation.css

navigation.css

83 ms

jquery-migrate-1.1.0.min.js

jquery-migrate-1.1.0.min.js

92 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

112 ms

flexslider.css

flexslider.css

96 ms

bootstrap.min.js

bootstrap.min.js

180 ms

jquery.smartmenus_v1.0.0.js

jquery.smartmenus_v1.0.0.js

182 ms

RWDUtil.js

RWDUtil.js

198 ms

Functions.js

Functions.js

197 ms

default.js

default.js

23 ms

carousel.js

carousel.js

199 ms

jquery.easing.min.js

jquery.easing.min.js

233 ms

wow.min.js

wow.min.js

244 ms

owl.carousel.min.js

owl.carousel.min.js

249 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

261 ms

video.js

video.js

262 ms

classie.js

classie.js

265 ms

scrolling-nav.js

scrolling-nav.js

316 ms

placeholders.min.js

placeholders.min.js

317 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

29 ms

pagecontrols.css

pagecontrols.css

80 ms

default.js

default.js

79 ms

animate.min.css

animate.min.css

230 ms

WebForms.js

WebForms.js

32 ms

WebUIValidation.js

WebUIValidation.js

34 ms

MicrosoftAjaxWebForms.js

MicrosoftAjaxWebForms.js

34 ms

default.css

default.css

23 ms

MicrosoftAjax.js

MicrosoftAjax.js

19 ms

font-awesome.min.css

font-awesome.min.css

212 ms

d-tect.js

d-tect.js

182 ms

video.js

video.js

204 ms

analytics.js

analytics.js

14 ms

matomo.js

matomo.js

203 ms

bg.jpg

bg.jpg

115 ms

iStock_000009713050XSmall.jpg

iStock_000009713050XSmall.jpg

147 ms

fb.png

fb.png

149 ms

google_plus%20(2).png

google_plus%20(2).png

199 ms

CareCredit.jpg

CareCredit.jpg

200 ms

panel1.jpg

panel1.jpg

62 ms

panel2.jpg

panel2.jpg

61 ms

panel3.jpg

panel3.jpg

63 ms

collect

collect

59 ms

panel2.jpg

panel2.jpg

82 ms

panel1.jpg

panel1.jpg

138 ms

panel3.jpg

panel3.jpg

138 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

49 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

48 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

51 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

51 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

49 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

219 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

27 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

29 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

30 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

31 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf

32 ms

cover-testimonial.jpg

cover-testimonial.jpg

54 ms

js

js

125 ms

iStock_000009713050XSmall.jpg

iStock_000009713050XSmall.jpg

581 ms

fb.png

fb.png

339 ms

google_plus%20(2).png

google_plus%20(2).png

271 ms

matomo.js

matomo.js

423 ms

CareCredit.jpg

CareCredit.jpg

312 ms

u-4n0qyriQwlOrhSvowK_l521wRZWMf_.ttf

u-4n0qyriQwlOrhSvowK_l521wRZWMf_.ttf

30 ms

u-440qyriQwlOrhSvowK_l5-fCZJ.ttf

u-440qyriQwlOrhSvowK_l5-fCZJ.ttf

28 ms

u-4n0qyriQwlOrhSvowK_l52xwNZWMf_.ttf

u-4n0qyriQwlOrhSvowK_l52xwNZWMf_.ttf

30 ms

u-4n0qyriQwlOrhSvowK_l52_wFZWMf_.ttf

u-4n0qyriQwlOrhSvowK_l52_wFZWMf_.ttf

29 ms

matomo.php

matomo.php

66 ms

configs.php

configs.php

117 ms

matomo.php

matomo.php

1298 ms

configs.php

configs.php

1608 ms

matomo.php

matomo.php

241 ms

configs.php

configs.php

217 ms

Accessibility Review

mclemorefamilydental.com accessibility score

86

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

mclemorefamilydental.com SEO score

83

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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

mclemorefamilydental.com

Open Graph description is not detected on the main page of Mc Lemore Family Dental. 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: