Tools & Wizards About Us
barnettdyer.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% 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

  • 92

    SEO

    Google-friendlier than
    74% of websites

barnettdyer.com

Tualatin Prosthodontist | Barnett & Dyer Prosthodontic Group | Dental Implants Tualatin, OR 97062

Page Load Speed

4 sec in total

First Response

378 ms

Resources Loaded

3.4 sec

Page Rendered

135 ms

barnettdyer.com screenshot

About Website

Visit barnettdyer.com now to see the best up-to-date Barnett Dyer content and also check out these interesting facts you probably never knew about barnettdyer.com

Tualatin, OR prosthodontists, Barnett & Dyer Prosthodontic Group are dedicated to excellence in prosthodontics from prevention care to restorations and implant dentistry. We provide a variety of cosme...

Visit barnettdyer.com

Key Findings

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

barnettdyer.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

Network Requests Diagram

barnettdyer.com

378 ms

bootstrap.min.css

68 ms

css

35 ms

css

51 ms

font-awesome.min.css

232 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 23% of them (16 requests) were addressed to the original Barnettdyer.com, 43% (30 requests) were made to Styles.prosites.com and 10% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Styles.prosites.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 215.1 kB (26%)

Content Size

837.4 kB

After Optimization

622.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 37.4 kB

  • Original 47.7 kB
  • After minification 39.1 kB
  • After compression 10.3 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 18% 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 37.4 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 86 B

  • Original 331.6 kB
  • After minification 331.6 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. Barnett Dyer images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 101.3 kB

  • Original 335.8 kB
  • After minification 332.0 kB
  • After compression 234.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 101.3 kB or 30% of the original size.

CSS Optimization

-62%

Potential reduce by 76.3 kB

  • Original 122.3 kB
  • After minification 100.9 kB
  • After compression 45.9 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. Barnettdyer.com needs all CSS files to be minified and compressed as it can save up to 76.3 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (76%)

Requests Now

45

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

barnettdyer.com

barnettdyer.com

378 ms

bootstrap.min.css

bootstrap.min.css

68 ms

css

css

35 ms

css

css

51 ms

font-awesome.min.css

font-awesome.min.css

232 ms

slick.css

slick.css

69 ms

slick-theme.css

slick-theme.css

68 ms

owl.carousel.css

owl.carousel.css

273 ms

sm-core-css.css

sm-core-css.css

276 ms

jquery.fancybox.css

jquery.fancybox.css

273 ms

video-js.css

video-js.css

285 ms

pagecontrols.css

pagecontrols.css

69 ms

default.css

default.css

64 ms

navigation.css

navigation.css

68 ms

stylesheet.css

stylesheet.css

107 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

107 ms

default.css

default.css

123 ms

bootstrap.min.css

bootstrap.min.css

115 ms

slick-theme.css

slick-theme.css

139 ms

slick.css

slick.css

139 ms

navigation.css

navigation.css

120 ms

pagecontrols.css

pagecontrols.css

120 ms

bootstrap.min.js

bootstrap.min.js

212 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

3000 ms

owl.carousel.min.js

owl.carousel.min.js

279 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

315 ms

video.js

video.js

397 ms

scrolling-nav.js

scrolling-nav.js

313 ms

jquery.easing.min.js

jquery.easing.min.js

317 ms

Functions.js

Functions.js

331 ms

RWDUtil.js

RWDUtil.js

408 ms

functions.js

functions.js

65 ms

placeholders.min.js

placeholders.min.js

83 ms

jquery-migrate-1.1.0.min.js

jquery-migrate-1.1.0.min.js

98 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

112 ms

stylesheet.css

stylesheet.css

100 ms

MicrosoftAjaxWebForms.js

MicrosoftAjaxWebForms.js

14 ms

MicrosoftAjax.js

MicrosoftAjax.js

14 ms

slick.js

slick.js

66 ms

WebForms.js

WebForms.js

7 ms

functions.js

functions.js

80 ms

placeholders.min.js

placeholders.min.js

72 ms

matomo.js

matomo.js

150 ms

analytics.js

analytics.js

19 ms

header-bg.jpg

header-bg.jpg

56 ms

cover1.jpg

cover1.jpg

79 ms

blue-bg.jpg

blue-bg.jpg

43 ms

content-bg.jpg

content-bg.jpg

43 ms

8vIU7ww63mVu7gtR-kwKxNvkNOjw-tbnfY3lCGxcZqT1UA.ttf

8vIU7ww63mVu7gtR-kwKxNvkNOjw-tbnfY3lCGxcZqT1UA.ttf

66 ms

8vIU7ww63mVu7gtR-kwKxNvkNOjw-jHgfY3lCGxcZqT1UA.ttf

8vIU7ww63mVu7gtR-kwKxNvkNOjw-jHgfY3lCGxcZqT1UA.ttf

83 ms

daaCSScvJGqLYhG8nNt8KPPswUAPni7TTMlpazyD.ttf

daaCSScvJGqLYhG8nNt8KPPswUAPni7TTMlpazyD.ttf

83 ms

daaHSScvJGqLYhG8nNt8KPPswUAPniZoadlESTSplhXF.ttf

daaHSScvJGqLYhG8nNt8KPPswUAPniZoadlESTSplhXF.ttf

81 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX9-p7K4GLs.ttf

56 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX9-p7K4GLs.ttf

104 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

371 ms

collect

collect

28 ms

testimonial-bg.jpg

testimonial-bg.jpg

83 ms

footer-bg.jpg

footer-bg.jpg

26 ms

dg4n_p3sv6gCJkwzT6RXiJwtYQAugw.ttf

dg4n_p3sv6gCJkwzT6RXiJwtYQAugw.ttf

49 ms

js

js

67 ms

Functions.js

Functions.js

223 ms

matomo.js

matomo.js

398 ms

matomo.php

matomo.php

68 ms

configs.php

configs.php

202 ms

matomo.php

matomo.php

1750 ms

configs.php

configs.php

958 ms

matomo.php

matomo.php

308 ms

configs.php

configs.php

256 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

24 ms

Accessibility Review

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Best Practices

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

barnettdyer.com 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 Barnettdyer.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 Barnettdyer.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

barnettdyer.com

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