Tools & Wizards About Us
fmccares.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

fmccares.com

Baylor Scott & White Family Medical Center – North Garland

Page Load Speed

2.9 sec in total

First Response

578 ms

Resources Loaded

1.8 sec

Page Rendered

583 ms

fmccares.com screenshot

About Website

Click here to check amazing Fmccares content for United States. Otherwise, check out these important facts you probably never knew about fmccares.com

Learn about the full range of convenient care we provide to families in north Garland, including primary care, cosmetic and plastic surgery, and even urgent care.

Visit fmccares.com

Key Findings

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

Performance Metrics

fmccares.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value19.3 s

0/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value1,270 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.28

43/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

Network Requests Diagram

family-medical-center-north-garland

578 ms

optimized-min.css

18 ms

optimized-min.css

39 ms

optimized-min.css

45 ms

pre-optimized-min.css

74 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fmccares.com, 8% (5 requests) were made to Wadcdn.azureedge.net and 8% (5 requests) were made to Bswh-p-001.sitecorecontenthub.cloud. The less responsive or slowest element that took the longest time to load (647 ms) relates to the external source Bswh-p-001-delivery.sitecorecontenthub.cloud.

Page Optimization Overview & Recommendations

Page size can be reduced by 483.1 kB (22%)

Content Size

2.2 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fmccares.com main page is 2.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 113.3 kB

  • Original 132.4 kB
  • After minification 92.6 kB
  • After compression 19.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. This page needs HTML code to be minified as it can gain 39.8 kB, which is 30% 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 113.3 kB or 86% of the original size.

Image Optimization

-13%

Potential reduce by 50.8 kB

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

JavaScript Optimization

-15%

Potential reduce by 224.6 kB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 1.3 MB

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 224.6 kB or 15% of the original size.

CSS Optimization

-66%

Potential reduce by 94.3 kB

  • Original 142.2 kB
  • After minification 61.4 kB
  • After compression 47.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. Fmccares.com needs all CSS files to be minified and compressed as it can save up to 94.3 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (71%)

Requests Now

51

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

family-medical-center-north-garland

family-medical-center-north-garland

578 ms

optimized-min.css

optimized-min.css

18 ms

optimized-min.css

optimized-min.css

39 ms

optimized-min.css

optimized-min.css

45 ms

pre-optimized-min.css

pre-optimized-min.css

74 ms

optimized-min.css

optimized-min.css

95 ms

mained32a9be.css

mained32a9be.css

46 ms

main.css

main.css

60 ms

VisitorIdentification.js

VisitorIdentification.js

62 ms

gsap.min.js

gsap.min.js

216 ms

ScrollTrigger.min.js

ScrollTrigger.min.js

133 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

124 ms

js

js

53 ms

optimize.js

optimize.js

53 ms

bsw-icons.css

bsw-icons.css

126 ms

forms2.min.js

forms2.min.js

159 ms

main.css

main.css

65 ms

chunk.js

chunk.js

122 ms

main.js

main.js

141 ms

bablic-57c745d43bc985e6680df36a.js

bablic-57c745d43bc985e6680df36a.js

122 ms

en-override.js

en-override.js

121 ms

bsw-icons.css

bsw-icons.css

131 ms

sitecore.css

sitecore.css

158 ms

optimized-min.js

optimized-min.js

137 ms

optimized-min.js

optimized-min.js

121 ms

optimized-min.js

optimized-min.js

126 ms

optimized-min.js

optimized-min.js

126 ms

optimized-min.js

optimized-min.js

125 ms

optimized-min.js

optimized-min.js

137 ms

optimized-min.js

optimized-min.js

326 ms

7871b464a79chunk.js

7871b464a79chunk.js

153 ms

main39bd49e5.js

main39bd49e5.js

509 ms

chunk.js

chunk.js

158 ms

main.js

main.js

194 ms

analytics.js

analytics.js

2 ms

gtm.js

gtm.js

409 ms

552c2a19e52743b39d9b1524df9826fb

552c2a19e52743b39d9b1524df9826fb

408 ms

b28d715181544801baa2e7d04f5b86c6

b28d715181544801baa2e7d04f5b86c6

396 ms

ee2ea4a9673d4da69a3497e001799519

ee2ea4a9673d4da69a3497e001799519

474 ms

6ce345094da24da6b1e9df37163bbbc8

6ce345094da24da6b1e9df37163bbbc8

475 ms

bswh-icon-gray.svg

bswh-icon-gray.svg

48 ms

logo-bswh-full.svg

logo-bswh-full.svg

57 ms

bswh-icon-color.svg

bswh-icon-color.svg

67 ms

sharpsans-bold-woff.woff

sharpsans-bold-woff.woff

71 ms

sharpsans-bold-woff.svg

sharpsans-bold-woff.svg

210 ms

sharpsans-semibold-woff.woff

sharpsans-semibold-woff.woff

265 ms

sharpsans-semibold-woff.svg

sharpsans-semibold-woff.svg

346 ms

sitecore.css

sitecore.css

265 ms

f02c4a1deaa24570b6c8f48789c5d447

f02c4a1deaa24570b6c8f48789c5d447

572 ms

b7465e0ae9714f6bbde58eac5a7249cc

b7465e0ae9714f6bbde58eac5a7249cc

567 ms

8e98100da97446d9976ac35870598aa8

8e98100da97446d9976ac35870598aa8

645 ms

fd81a9920d6a471683e03105af798ce4

fd81a9920d6a471683e03105af798ce4

647 ms

sharpsans-medium-woff.svg

sharpsans-medium-woff.svg

224 ms

sharpsans-medium-woff.woff

sharpsans-medium-woff.woff

226 ms

main.js

main.js

224 ms

a95838567131424bb345700250336432

a95838567131424bb345700250336432

562 ms

bsw-icons.woff

bsw-icons.woff

244 ms

pling

pling

178 ms

95 ms

Accessibility Review

fmccares.com accessibility score

89

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

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

High

Missing source maps for large first-party JavaScript

SEO Factors

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fmccares.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fmccares.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

fmccares.com

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