Tools & Wizards About Us
healthtexas.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

healthtexas.com

Baylor Scott & White HealthTexas Provider Network | Baylor Scott & White Health

Page Load Speed

3.2 sec in total

First Response

240 ms

Resources Loaded

2.1 sec

Page Rendered

901 ms

healthtexas.com screenshot

About Website

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

HealthTexas Provider Network (HTPN), a member of the Baylor Scott & White Health system, is making healthcare better by providing quality patient care.

Visit healthtexas.com

Key Findings

We analyzed Healthtexas.com page load time and found that the first response time was 240 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

healthtexas.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value23.3 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value5,040 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.055

98/100

15%

TTI (Time to Interactive)

Value25.7 s

0/100

10%

Network Requests Diagram

www.bswhealth.com

240 ms

optimized-min.css

21 ms

optimized-min.css

45 ms

optimized-min.css

52 ms

pre-optimized-min.css

63 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 454.4 kB (46%)

Content Size

987.2 kB

After Optimization

532.8 kB

  • HTML
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 298.5 kB

  • Original 338.5 kB
  • After minification 276.8 kB
  • After compression 40.0 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 61.7 kB, which is 18% 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 298.5 kB or 88% of the original size.

JavaScript Optimization

-13%

Potential reduce by 70.3 kB

  • Original 546.5 kB
  • After minification 546.4 kB
  • After compression 476.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 70.3 kB or 13% of the original size.

CSS Optimization

-84%

Potential reduce by 85.6 kB

  • Original 102.1 kB
  • After minification 21.3 kB
  • After compression 16.5 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. Healthtexas.com needs all CSS files to be minified and compressed as it can save up to 85.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (56%)

Requests Now

59

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.bswhealth.com

www.bswhealth.com

240 ms

optimized-min.css

optimized-min.css

21 ms

optimized-min.css

optimized-min.css

45 ms

optimized-min.css

optimized-min.css

52 ms

pre-optimized-min.css

pre-optimized-min.css

63 ms

optimized-min.css

optimized-min.css

54 ms

VisitorIdentification.js

VisitorIdentification.js

108 ms

gsap.min.js

gsap.min.js

164 ms

ScrollTrigger.min.js

ScrollTrigger.min.js

157 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

150 ms

optimize.js

optimize.js

99 ms

bsw-icons.css

bsw-icons.css

131 ms

main5b9ae86a.css

main5b9ae86a.css

128 ms

787025f27dfchunk.js

787025f27dfchunk.js

96 ms

main116cb6a2.js

main116cb6a2.js

148 ms

munchkin.js

munchkin.js

145 ms

forms2-marketo.min.js

forms2-marketo.min.js

347 ms

57c745d43bc985e6680df36a.js

57c745d43bc985e6680df36a.js

608 ms

en-override.js

en-override.js

123 ms

bsw-icons.css

bsw-icons.css

127 ms

sitecore.css

sitecore.css

345 ms

optimized-min.js

optimized-min.js

136 ms

optimized-min.js

optimized-min.js

127 ms

optimized-min.js

optimized-min.js

127 ms

optimized-min.js

optimized-min.js

127 ms

optimized-min.js

optimized-min.js

135 ms

optimized-min.js

optimized-min.js

142 ms

optimized-min.js

optimized-min.js

139 ms

analytics.js

analytics.js

35 ms

gtm.js

gtm.js

741 ms

552c2a19e52743b39d9b1524df9826fb

552c2a19e52743b39d9b1524df9826fb

716 ms

f02c4a1deaa24570b6c8f48789c5d447

f02c4a1deaa24570b6c8f48789c5d447

699 ms

b28d715181544801baa2e7d04f5b86c6

b28d715181544801baa2e7d04f5b86c6

564 ms

ee2ea4a9673d4da69a3497e001799519

ee2ea4a9673d4da69a3497e001799519

563 ms

6ce345094da24da6b1e9df37163bbbc8

6ce345094da24da6b1e9df37163bbbc8

564 ms

6ce10a5b3d2741c0ac44c1052c47bd83

6ce10a5b3d2741c0ac44c1052c47bd83

559 ms

aa0b77d96fe94a6487e9a4f0f433c5ed

aa0b77d96fe94a6487e9a4f0f433c5ed

561 ms

fbdfc39728fb49f8906a9219fb58f86a

fbdfc39728fb49f8906a9219fb58f86a

804 ms

21bdb21cdfd24b8ab6f50ae38c32750f

21bdb21cdfd24b8ab6f50ae38c32750f

719 ms

bswh-icon-gray.svg

bswh-icon-gray.svg

27 ms

logo-bswh-full.svg

logo-bswh-full.svg

22 ms

logo-bswh-fullnegative.svg

logo-bswh-fullnegative.svg

339 ms

sharpsans-bold-woff.woff

sharpsans-bold-woff.woff

142 ms

sharpsans-bold-woff.svg

sharpsans-bold-woff.svg

339 ms

2097a1d7e37a454db61096b99dd5720c

2097a1d7e37a454db61096b99dd5720c

659 ms

b4c8f2c354fc4e9db3f9357c4041a569

b4c8f2c354fc4e9db3f9357c4041a569

605 ms

2629777d09714964b0739840a9794333

2629777d09714964b0739840a9794333

604 ms

bswh-full-gray.svg

bswh-full-gray.svg

306 ms

bswh-logo-gray.svg

bswh-logo-gray.svg

307 ms

mejs-controls.svg

mejs-controls.svg

304 ms

sharpsans-semibold-woff.woff

sharpsans-semibold-woff.woff

280 ms

sharpsans-semibold-woff.svg

sharpsans-semibold-woff.svg

280 ms

fontawesome-webfont-woff.woff

fontawesome-webfont-woff.woff

340 ms

sitecore.css

sitecore.css

227 ms

getForm

getForm

427 ms

a95838567131424bb345700250336432

a95838567131424bb345700250336432

278 ms

fd81a9920d6a471683e03105af798ce4

fd81a9920d6a471683e03105af798ce4

279 ms

8e98100da97446d9976ac35870598aa8

8e98100da97446d9976ac35870598aa8

275 ms

x-social.svg

x-social.svg

158 ms

bsw-icons.woff

bsw-icons.woff

103 ms

forms2.css

forms2.css

57 ms

forms2-theme-simple.css

forms2-theme-simple.css

84 ms

pling

pling

304 ms

219 ms

ajax-loader.gif

ajax-loader.gif

93 ms

sharpsans-medium-woff.svg

sharpsans-medium-woff.svg

89 ms

sharpsans-medium-woff.woff

sharpsans-medium-woff.woff

34 ms

slick.woff

slick.woff

34 ms

XDFrame

XDFrame

72 ms

forms2.min.js

forms2.min.js

63 ms

slick.ttf

slick.ttf

48 ms

Accessibility Review

healthtexas.com accessibility score

70

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Image elements do not have [alt] attributes

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.

Best Practices

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

healthtexas.com SEO score

77

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

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Healthtexas.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 Healthtexas.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

healthtexas.com

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