Tools & Wizards About Us
williamrpike.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

williamrpike.com

Dentist Estes Park CO, Cosmetic Dentist Estes Park, Family Dentist 80517

Page Load Speed

987 ms in total

First Response

65 ms

Resources Loaded

692 ms

Page Rendered

230 ms

williamrpike.com screenshot

About Website

Click here to check amazing Williamrpike content. Otherwise, check out these important facts you probably never knew about williamrpike.com

Our Dentist in Estes Park CO, Dr William R Pike offers dental treatments like Cosmetic dentistry, Dental Implants, Family Dentistry and Emergency Dentistry services in Colorado.

Visit williamrpike.com

Key Findings

We analyzed Williamrpike.com page load time and found that the first response time was 65 ms and then it took 922 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

williamrpike.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value920 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.234

53/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

williamrpike.com

65 ms

williamrpike.com

58 ms

www.williamrpike.com

105 ms

css

52 ms

css

71 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 85% of them (57 requests) were addressed to the original Williamrpike.com, 4% (3 requests) were made to Fonts.googleapis.com and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (295 ms) belongs to the original domain Williamrpike.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 209.8 kB (18%)

Content Size

1.2 MB

After Optimization

969.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Williamrpike.com main page is 1.2 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 895.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 81.3 kB

  • Original 96.6 kB
  • After minification 77.9 kB
  • After compression 15.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 18.7 kB, which is 19% 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 81.3 kB or 84% of the original size.

Image Optimization

-11%

Potential reduce by 96.5 kB

  • Original 895.4 kB
  • After minification 798.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. Obviously, Williamrpike needs image optimization as it can save up to 96.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-18%

Potential reduce by 26.1 kB

  • Original 146.1 kB
  • After minification 146.1 kB
  • After compression 120.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 26.1 kB or 18% of the original size.

CSS Optimization

-14%

Potential reduce by 5.8 kB

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

Requests Breakdown

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

Requests Now

60

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

williamrpike.com

williamrpike.com

65 ms

williamrpike.com

williamrpike.com

58 ms

www.williamrpike.com

www.williamrpike.com

105 ms

css

css

52 ms

css

css

71 ms

css

css

79 ms

bootstrap.min.css

bootstrap.min.css

37 ms

ddlevelsmenu-base.css

ddlevelsmenu-base.css

48 ms

ddlevelsmenu-topbar.css

ddlevelsmenu-topbar.css

49 ms

flexslider.css

flexslider.css

55 ms

slider.css

slider.css

56 ms

prettyPhoto.css

prettyPhoto.css

62 ms

font-awesome.min.css

font-awesome.min.css

59 ms

style.css

style.css

64 ms

color.css

color.css

57 ms

intlTelInput.css

intlTelInput.css

69 ms

google.png

google.png

71 ms

pf-icon.png

pf-icon.png

69 ms

pt-icon.png

pt-icon.png

69 ms

ct-icon.png

ct-icon.png

71 ms

logo.png

logo.png

89 ms

fb.png

fb.png

90 ms

twtr.png

twtr.png

91 ms

insta.png

insta.png

91 ms

1.jpg

1.jpg

96 ms

jquery.js

jquery.js

96 ms

bootstrap.js

bootstrap.js

91 ms

intlTelInput.min.js

intlTelInput.min.js

88 ms

contact-form.js

contact-form.js

89 ms

api.js

api.js

82 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

89 ms

isotope.js

isotope.js

91 ms

ddlevelsmenu.js

ddlevelsmenu.js

92 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

212 ms

jquery.carouFredSel-6.2.1-packed.js

jquery.carouFredSel-6.2.1-packed.js

222 ms

jquery.cslider.js

jquery.cslider.js

214 ms

respond.min.js

respond.min.js

220 ms

html5shiv.js

html5shiv.js

220 ms

modernizr.custom.28468.js

modernizr.custom.28468.js

227 ms

custom.js

custom.js

229 ms

jquery.bpopup.min.js

jquery.bpopup.min.js

256 ms

js

js

90 ms

3.jpg

3.jpg

295 ms

4.jpg

4.jpg

294 ms

6.jpg

6.jpg

265 ms

cosmetic.png

cosmetic.png

262 ms

before-after.png

before-after.png

262 ms

dental-bridges2.jpg

dental-bridges2.jpg

253 ms

dental-implants2.jpg

dental-implants2.jpg

253 ms

tmj.png

tmj.png

254 ms

periodontal.png

periodontal.png

251 ms

endontics.png

endontics.png

249 ms

oral.png

oral.png

245 ms

specialists.png

specialists.png

242 ms

emergency.png

emergency.png

244 ms

family.png

family.png

241 ms

MasterCard.jpg

MasterCard.jpg

243 ms

Visa.jpg

Visa.jpg

226 ms

discover.jpg

discover.jpg

224 ms

CareCredit.jpg

CareCredit.jpg

224 ms

gtm.js

gtm.js

73 ms

arrow-down.gif

arrow-down.gif

39 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

77 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

78 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

26 ms

js

js

67 ms

analytics.js

analytics.js

61 ms

Accessibility Review

williamrpike.com accessibility score

79

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

williamrpike.com best practices score

58

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

High

Browser errors were logged to the console

SEO Factors

williamrpike.com SEO score

84

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

williamrpike.com

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