Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

steliz.org

HSHS St. Elizabeth's Hospital, O'Fallon, Illinois

Page Load Speed

7.2 sec in total

First Response

194 ms

Resources Loaded

5.7 sec

Page Rendered

1.4 sec

steliz.org screenshot

About Website

Visit steliz.org now to see the best up-to-date St Eliz content for United States and also check out these interesting facts you probably never knew about steliz.org

An accredited general acute care health facility in the south-central illinois region offers quality inpatient and outpatient care, including a nationally-recognized cardiac care network.

Visit steliz.org

Key Findings

We analyzed Steliz.org page load time and found that the first response time was 194 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

steliz.org performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value28.8 s

0/100

25%

SI (Speed Index)

Value23.3 s

0/100

10%

TBT (Total Blocking Time)

Value11,650 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.113

86/100

15%

TTI (Time to Interactive)

Value40.3 s

0/100

10%

Network Requests Diagram

steliz.org

194 ms

1055 ms

gtm.js

217 ms

gtm.js

300 ms

wp-emoji-release.min.js

102 ms

Our browser made a total of 161 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Steliz.org, 70% (112 requests) were made to Hshs.org and 16% (26 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Hshs.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 395.4 kB (6%)

Content Size

6.5 MB

After Optimization

6.1 MB

In fact, the total size of Steliz.org main page is 6.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. 85% 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. Images take 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 155.0 kB

  • Original 198.4 kB
  • After minification 178.6 kB
  • After compression 43.4 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 155.0 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 173.8 kB

  • Original 6.0 MB
  • After minification 5.8 MB

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. St Eliz images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 66.7 kB

  • Original 286.3 kB
  • After minification 286.2 kB
  • After compression 219.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 66.7 kB or 23% of the original size.

CSS Optimization

-0%

Potential reduce by 18 B

  • Original 12.2 kB
  • After minification 12.2 kB
  • After compression 12.2 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. Steliz.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 81 (63%)

Requests Now

129

After Optimization

48

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

Accessibility Review

steliz.org accessibility score

68

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

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

steliz.org best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

steliz.org SEO score

82

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

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 Steliz.org 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 Steliz.org 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

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