Tools & Wizards About Us
citydoc.net screenshot

Report Summary

  • 22

    Performance

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

  • 84

    SEO

    Google-friendlier than
    52% of websites

citydoc.net

CityDoc Urgent Care: Convenient Care in Dallas-Fort Worth

Page Load Speed

2.1 sec in total

First Response

147 ms

Resources Loaded

1.3 sec

Page Rendered

610 ms

citydoc.net screenshot

About Website

Visit citydoc.net now to see the best up-to-date City Doc content and also check out these interesting facts you probably never knew about citydoc.net

Need urgent care without the wait? CityDoc offers convenient & affordable urgent care services. 4 locations in Dallas & Fort Worth. Walk in today!

Visit citydoc.net

Key Findings

We analyzed Citydoc.net page load time and found that the first response time was 147 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

citydoc.net performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

69/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value3,160 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.127

82/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

citydoc.net

147 ms

citydoc.net

196 ms

seo-automation-styles.css

63 ms

swiper-bundle.css

92 ms

custom.css

88 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 55% of them (41 requests) were addressed to the original Citydoc.net, 7% (5 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Cdn03.jotfor.ms. The less responsive or slowest element that took the longest time to load (463 ms) relates to the external source Acsbapp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 219.4 kB (15%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Citydoc.net main page is 1.5 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 665.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 208.5 kB

  • Original 252.7 kB
  • After minification 248.0 kB
  • After compression 44.2 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 208.5 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 24 B

  • Original 665.9 kB
  • After minification 665.9 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. City Doc images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.1 kB

  • Original 448.2 kB
  • After minification 448.2 kB
  • After compression 445.1 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

-8%

Potential reduce by 7.8 kB

  • Original 96.8 kB
  • After minification 96.8 kB
  • After compression 89.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. Citydoc.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 41 (64%)

Requests Now

64

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

citydoc.net

citydoc.net

147 ms

citydoc.net

citydoc.net

196 ms

seo-automation-styles.css

seo-automation-styles.css

63 ms

swiper-bundle.css

swiper-bundle.css

92 ms

custom.css

custom.css

88 ms

screen.min.css

screen.min.css

94 ms

style.min.css

style.min.css

121 ms

style.css

style.css

93 ms

jquery.min.js

jquery.min.js

134 ms

jquery-migrate.min.js

jquery-migrate.min.js

107 ms

swiper-bundle.min.js

swiper-bundle.min.js

145 ms

global.js

global.js

116 ms

js

js

67 ms

swap.js

swap.js

43 ms

lazysizes.min.js

lazysizes.min.js

113 ms

conversion.js

conversion.js

33 ms

front.min.js

front.min.js

123 ms

scripts.min.js

scripts.min.js

353 ms

jquery.fitvids.js

jquery.fitvids.js

193 ms

jquery.mobile.js

jquery.mobile.js

194 ms

frontend-bundle.min.js

frontend-bundle.min.js

194 ms

common.js

common.js

197 ms

nmb2nm6os9

nmb2nm6os9

452 ms

stat.js

stat.js

346 ms

bat.js

bat.js

394 ms

gtm.js

gtm.js

345 ms

62704699347165

62704699347165

1 ms

Uptown-Dallas-Location.jpg

Uptown-Dallas-Location.jpg

274 ms

City-Doc-Service-Youtube-Video-Image.jpg

City-Doc-Service-Youtube-Video-Image.jpg

369 ms

app.js

app.js

463 ms

RadikalRegular.woff

RadikalRegular.woff

363 ms

62704699347165

62704699347165

457 ms

402 ms

logo-1.svg

logo-1.svg

151 ms

cropped-icon.png

cropped-icon.png

152 ms

icon-phn.svg

icon-phn.svg

150 ms

icon-nav.svg

icon-nav.svg

151 ms

mtm-bookonline.svg

mtm-bookonline.svg

154 ms

facebook-logo.svg

facebook-logo.svg

151 ms

instagram-icon-1-1.png

instagram-icon-1-1.png

184 ms

icon-pay.svg

icon-pay.svg

182 ms

Inwood-Dallas-location-.png

Inwood-Dallas-location-.png

213 ms

City-Doc-Convenient-Family-.jpg

City-Doc-Convenient-Family-.jpg

269 ms

Citydoc-Video-Visit-Appointment-doc.jpg

Citydoc-Video-Visit-Appointment-doc.jpg

236 ms

134261330_m_normal_none-scaled.jpg

134261330_m_normal_none-scaled.jpg

313 ms

CityDoc-Web-Locations-building_11.jpg

CityDoc-Web-Locations-building_11.jpg

236 ms

We-Accept-Insurance-or-Self-Pay-payment-banner-scaled-1.jpg

We-Accept-Insurance-or-Self-Pay-payment-banner-scaled-1.jpg

239 ms

RadikalBold.woff

RadikalBold.woff

214 ms

modules.woff

modules.woff

239 ms

17478459.js

17478459.js

46 ms

clarity.js

clarity.js

18 ms

36 ms

formCss.css

formCss.css

46 ms

form-common.css

form-common.css

43 ms

nova.css

nova.css

97 ms

49 ms

566a91c2977cdfcd478b4567.css

566a91c2977cdfcd478b4567.css

127 ms

payment_feature.css

payment_feature.css

94 ms

css

css

48 ms

css

css

69 ms

prototype.forms.js

prototype.forms.js

124 ms

jotform.forms.js

jotform.forms.js

71 ms

api.js

api.js

38 ms

control_appointment.css

control_appointment.css

30 ms

control_inline.css

control_inline.css

38 ms

urgent-care.jpg

urgent-care.jpg

38 ms

Fort-Worth-.png

Fort-Worth-.png

58 ms

recaptcha__en.js

recaptcha__en.js

28 ms

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

19 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

25 ms

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

82 ms

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

93 ms

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

93 ms

style.min.css

style.min.css

54 ms

c.gif

c.gif

7 ms

Accessibility Review

citydoc.net accessibility score

86

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

citydoc.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

SEO Factors

citydoc.net SEO score

84

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

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 Citydoc.net 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 Citydoc.net 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

citydoc.net

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