Tools & Wizards About Us
kindredsanantoniocentral.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

kindredsanantoniocentral.com

Kindred Hospital San Antonio Central | Long-Term Acute Care (LTAC) Hospital

Page Load Speed

21.2 sec in total

First Response

73 ms

Resources Loaded

20.8 sec

Page Rendered

322 ms

kindredsanantoniocentral.com screenshot

About Website

Visit kindredsanantoniocentral.com now to see the best up-to-date Kindred San Antonio Central content and also check out these interesting facts you probably never knew about kindredsanantoniocentral.com

Kindred Hospital San Antonio Central is a long-term acute care hospital offering the same in-depth care you would receive in a traditional hospital, but for an extended recovery period. We partner wit...

Visit kindredsanantoniocentral.com

Key Findings

We analyzed Kindredsanantoniocentral.com page load time and found that the first response time was 73 ms and then it took 21.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

kindredsanantoniocentral.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value390 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

kindredsanantoniocentral.com

73 ms

kindred-hospital-san-antonio-central

101 ms

kindred-hospital-san-antonio-central

53 ms

kindred-hospital-san-antonio-central

132 ms

vendor.min.css

25 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Kindredsanantoniocentral.com, 55% (32 requests) were made to Kindredhospitals.com and 9% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Fusion.realtourvision.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 100.1 kB (16%)

Content Size

643.8 kB

After Optimization

543.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 43.8 kB

  • Original 59.4 kB
  • After minification 56.2 kB
  • After compression 15.6 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 43.8 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 2.5 kB

  • Original 193.6 kB
  • After minification 191.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. Kindred San Antonio Central images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 31.0 kB

  • Original 292.3 kB
  • After minification 292.2 kB
  • After compression 261.2 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 31.0 kB or 11% of the original size.

CSS Optimization

-23%

Potential reduce by 22.8 kB

  • Original 98.6 kB
  • After minification 98.6 kB
  • After compression 75.8 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. Kindredsanantoniocentral.com needs all CSS files to be minified and compressed as it can save up to 22.8 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (55%)

Requests Now

44

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kindredsanantoniocentral.com

kindredsanantoniocentral.com

73 ms

kindred-hospital-san-antonio-central

kindred-hospital-san-antonio-central

101 ms

kindred-hospital-san-antonio-central

kindred-hospital-san-antonio-central

53 ms

kindred-hospital-san-antonio-central

kindred-hospital-san-antonio-central

132 ms

vendor.min.css

vendor.min.css

25 ms

kindredhealthcare.min.css

kindredhealthcare.min.css

58 ms

analytics.js

analytics.js

51 ms

sitefinity-insight-client.min.3.1.2.js

sitefinity-insight-client.min.3.1.2.js

46 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

52 ms

WebResource.axd

WebResource.axd

103 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

101 ms

ScriptResource.axd

ScriptResource.axd

102 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

118 ms

jquery-ui.min.js

jquery-ui.min.js

52 ms

Search-box.min.js

Search-box.min.js

132 ms

js

js

137 ms

WebResource.axd

WebResource.axd

102 ms

address-field.min.js

address-field.min.js

101 ms

bootstrap.min.js

bootstrap.min.js

133 ms

js

js

133 ms

widget3.php

widget3.php

20163 ms

js

js

177 ms

kindred.min.js

kindred.min.js

131 ms

siteanalyze_78525.js

siteanalyze_78525.js

53 ms

WebResource.axd

WebResource.axd

132 ms

pixie.js

pixie.js

115 ms

pixie

pixie

107 ms

getuid

getuid

120 ms

san_antonio_central_logo.svg

san_antonio_central_logo.svg

99 ms

khhoustonmedcenterhero3.jpg

khhoustonmedcenterhero3.jpg

105 ms

joint_commission_goldseal100x100.png

joint_commission_goldseal100x100.png

57 ms

esgrlogolarge.tmb-small.png

esgrlogolarge.tmb-small.png

177 ms

stories-of-caring-judiths-story-211.jpg

stories-of-caring-judiths-story-211.jpg

59 ms

how-ed-survived-a-near-fatal-motorcycle-accident-211.jpg

how-ed-survived-a-near-fatal-motorcycle-accident-211.jpg

57 ms

your-guide-to-medicare-and-transitional-care-211.jpg

your-guide-to-medicare-and-transitional-care-211.jpg

58 ms

5-faq-s-about-long-term-acute-care-hospitals-211.jpg

5-faq-s-about-long-term-acute-care-hospitals-211.jpg

58 ms

collect

collect

95 ms

collect

collect

108 ms

collect

collect

99 ms

collect

collect

116 ms

js

js

44 ms

js

js

59 ms

attr.ml-api.io

attr.ml-api.io

229 ms

a0bbbce9-cbea-4aa1-83c3-6aaa0d57d432.woff

a0bbbce9-cbea-4aa1-83c3-6aaa0d57d432.woff

8 ms

10238a7f-3b49-4835-a12c-0eb7ed3391ac.woff

10238a7f-3b49-4835-a12c-0eb7ed3391ac.woff

56 ms

5c9994cb-9ea4-4a97-bdea-8b44e3f33b7c.woff

5c9994cb-9ea4-4a97-bdea-8b44e3f33b7c.woff

6 ms

050b1948-f226-4d20-a65a-15d8ed031222.woff

050b1948-f226-4d20-a65a-15d8ed031222.woff

56 ms

1be79393-9ab6-4f5e-8ff8-786d00be4238.woff

1be79393-9ab6-4f5e-8ff8-786d00be4238.woff

14 ms

439c5962-f9fe-4eaf-a1f6-f41d42edba75.woff

439c5962-f9fe-4eaf-a1f6-f41d42edba75.woff

14 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

54 ms

34e0e4c0-c294-49bb-9a8e-1b2cafd54e32.woff

34e0e4c0-c294-49bb-9a8e-1b2cafd54e32.woff

14 ms

insight.min.js

insight.min.js

49 ms

munchkin.js

munchkin.js

45 ms

gtm.js

gtm.js

55 ms

mtiFontTrackingCode.js

mtiFontTrackingCode.js

22 ms

insight_tag_errors.gif

insight_tag_errors.gif

62 ms

munchkin.js

munchkin.js

189 ms

image.aspx

image.aspx

11 ms

Accessibility Review

kindredsanantoniocentral.com accessibility score

100

Accessibility Issues

Best Practices

kindredsanantoniocentral.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

kindredsanantoniocentral.com SEO score

98

Search Engine Optimization Advices

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

kindredsanantoniocentral.com

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