Tools & Wizards About Us
afteroursdoc.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

afteroursdoc.com

Urgent Care in Colorado | AfterOurs Urgent Care

Page Load Speed

1.6 sec in total

First Response

33 ms

Resources Loaded

1.2 sec

Page Rendered

372 ms

afteroursdoc.com screenshot

About Website

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

AfterOurs Urgent Care provides immediate care for common ailments and injuries, with clinics in Denver, Littleton, and Thornton, Colorado. Learn more.

Visit afteroursdoc.com

Key Findings

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

Performance Metrics

afteroursdoc.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value1,300 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.136

80/100

15%

TTI (Time to Interactive)

Value16.2 s

6/100

10%

Network Requests Diagram

afteroursdoc.com

33 ms

afteroursinc.com

126 ms

www.afteroursinc.com

217 ms

bootstrap.min.css

45 ms

slick.css

36 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Afteroursdoc.com, 65% (33 requests) were made to Afteroursinc.com and 8% (4 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (406 ms) relates to the external source Ehr.charmtracker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 378.9 kB (28%)

Content Size

1.4 MB

After Optimization

990.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Afteroursdoc.com main page is 1.4 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. 30% of websites need less resources to load. Images take 631.1 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 233.6 kB

  • Original 273.7 kB
  • After minification 263.4 kB
  • After compression 40.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. 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 233.6 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 137 B

  • Original 631.1 kB
  • After minification 631.0 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. Afteroursdoc images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 423 B

  • Original 315.0 kB
  • After minification 315.0 kB
  • After compression 314.6 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.

CSS Optimization

-97%

Potential reduce by 144.7 kB

  • Original 149.8 kB
  • After minification 5.5 kB
  • After compression 5.1 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. Afteroursdoc.com needs all CSS files to be minified and compressed as it can save up to 144.7 kB or 97% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (38%)

Requests Now

47

After Optimization

29

  • Images
  • JavaScript
  • CSS

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Afteroursdoc. 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 from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

afteroursdoc.com

afteroursdoc.com

33 ms

afteroursinc.com

afteroursinc.com

126 ms

www.afteroursinc.com

www.afteroursinc.com

217 ms

bootstrap.min.css

bootstrap.min.css

45 ms

slick.css

slick.css

36 ms

slick-theme.css

slick-theme.css

43 ms

wpo-minify-header-8e8f626e.min.css

wpo-minify-header-8e8f626e.min.css

79 ms

wpo-minify-header-27233032.min.js

wpo-minify-header-27233032.min.js

54 ms

dnc4bjx.css

dnc4bjx.css

50 ms

nkp.min.css

nkp.min.css

33 ms

16db093817.js

16db093817.js

142 ms

slick.min.js

slick.min.js

45 ms

popper.min.js

popper.min.js

36 ms

bootstrap.min.js

bootstrap.min.js

55 ms

wpo-minify-footer-158b7a48.min.js

wpo-minify-footer-158b7a48.min.js

50 ms

w.chatlio-widget.js

w.chatlio-widget.js

96 ms

p.css

p.css

26 ms

font-awesome.min.css

font-awesome.min.css

30 ms

gtm.js

gtm.js

192 ms

logo-1.png

logo-1.png

59 ms

charmbot.do

charmbot.do

406 ms

widget.js

widget.js

203 ms

1568286222-hero-image.png

1568286222-hero-image.png

135 ms

buildings-sunset.jpg

buildings-sunset.jpg

134 ms

Aarp.png

Aarp.png

133 ms

Daco_5062198-sm-min.png

Daco_5062198-sm-min.png

134 ms

anthem-logo-sm-min.png

anthem-logo-sm-min.png

133 ms

PikPng-sm-min.png

PikPng-sm-min.png

236 ms

united-healthcare-logo-1.jpg

united-healthcare-logo-1.jpg

152 ms

health-net-vector-logo-sm-min.png

health-net-vector-logo-sm-min.png

186 ms

Humana_logo-sm-min.png

Humana_logo-sm-min.png

191 ms

multiplan-logo-sm-min.png

multiplan-logo-sm-min.png

186 ms

medicare-gov.png

medicare-gov.png

186 ms

tricare-logo.png

tricare-logo.png

247 ms

Introducing-Health-First-Colarado-The-Re-branded-Medicaid-Program-900x450-1.jpg

Introducing-Health-First-Colarado-The-Re-branded-Medicaid-Program-900x450-1.jpg

195 ms

First-Health-Logo-min.jpg

First-Health-Logo-min.jpg

199 ms

cofinity-min.png

cofinity-min.png

245 ms

phcs-logo.png

phcs-logo.png

258 ms

medicaid-logo-522-min.jpg

medicaid-logo-522-min.jpg

209 ms

colorado-access-logo-522.jpg

colorado-access-logo-522.jpg

217 ms

DenverHealth-logo-522-scaled-min.jpg

DenverHealth-logo-522-scaled-min.jpg

230 ms

RR-Medicare-logo-522.jpg

RR-Medicare-logo-522.jpg

233 ms

Triwest-logo-sm-min.png

Triwest-logo-sm-min.png

284 ms

Logo-Mark.png

Logo-Mark.png

283 ms

service-3.jpg

service-3.jpg

254 ms

service-4.jpg

service-4.jpg

262 ms

service-2.jpg

service-2.jpg

268 ms

service-1.jpg

service-1.jpg

278 ms

w.chatlio-widget.js

w.chatlio-widget.js

128 ms

modules.woff

modules.woff

212 ms

widget_app_base_1724849559553.js

widget_app_base_1724849559553.js

18 ms

Accessibility Review

afteroursdoc.com accessibility score

79

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

afteroursdoc.com best practices score

67

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

High

Missing source maps for large first-party JavaScript

SEO Factors

afteroursdoc.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 Afteroursdoc.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 Afteroursdoc.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

afteroursdoc.com

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