1.7 sec in total
112 ms
1.2 sec
441 ms
Click here to check amazing Regency Hospital content for United States. Otherwise, check out these important facts you probably never knew about regencyhospital.com
Regency Hospitals specialize in treating patients recovering from catastrophic critical illness. Our multidisciplinary teams develop individual treatment plans to meet each patient’s needs with a goal...
Visit regencyhospital.comWe analyzed Regencyhospital.com page load time and found that the first response time was 112 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
regencyhospital.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value8.5 s
2/100
25%
Value6.5 s
39/100
10%
Value1,590 ms
12/100
30%
Value0.133
81/100
15%
Value12.3 s
15/100
10%
112 ms
64 ms
116 ms
32 ms
46 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 90% of them (122 requests) were addressed to the original Regencyhospital.com, 6% (8 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (451 ms) belongs to the original domain Regencyhospital.com.
Page size can be reduced by 51.6 kB (20%)
260.3 kB
208.7 kB
In fact, the total size of Regencyhospital.com main page is 260.3 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. 80% 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 141.0 kB which makes up the majority of the site volume.
Potential reduce by 49.7 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 49.7 kB or 72% of the original size.
Potential reduce by 0 B
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. Regency Hospital images are well optimized though.
Potential reduce by 42 B
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.
Potential reduce by 1.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. Regencyhospital.com has all CSS files already compressed.
Number of requests can be reduced by 102 (84%)
121
19
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Regency Hospital. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 83 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
regencyhospital.com
112 ms
regencyhospital.com
64 ms
www.regencyhospital.com
116 ms
bootstrap.css
32 ms
mediaelementplayer.css
46 ms
mediaelementplayer-legacy.css
45 ms
font-awesomemin.css
70 ms
fullcalendar.css
43 ms
jquerymcustomscrollbar.css
40 ms
jquery-ui.css
54 ms
author.css
80 ms
core.css
67 ms
file-type-icons.css
71 ms
grayscale-mode.css
72 ms
reset.css
83 ms
accessibility_global.css
94 ms
pre-optimized-min.css
118 ms
css
42 ms
font-awesome.min.css
35 ms
jquery-3.5.1.min.js
25 ms
ie-origin-fix.js
108 ms
xaquery.js
111 ms
moment.js
114 ms
lo-dash.js
111 ms
modernizr.js
221 ms
galleria-161.js
326 ms
fullcalendar.js
375 ms
gcal.js
326 ms
jqueryuitouch-punchmin.js
326 ms
hammer.js
327 ms
backbone-min.js
328 ms
typeahead.js
373 ms
jquerymcustomscrollbar.js
327 ms
flash-polyfill.js
373 ms
mediaelement-and-player.js
374 ms
dailymotion.js
372 ms
facebook.js
372 ms
soundcloud.js
432 ms
twitch.js
374 ms
vimeo.js
451 ms
xa.js
434 ms
observer.js
432 ms
partial-design-highlight.js
344 ms
google-maps-connector.js
401 ms
component-location-service.js
417 ms
component-map.js
415 ms
component-location-service.js
416 ms
component-search.js
405 ms
component-search-ajax.js
390 ms
component-search-base-model.js
423 ms
component-search-base-view.js
413 ms
component-search-box.js
413 ms
component-search-facet-data.js
405 ms
component-search-facet-summary.js
400 ms
component-search-facet-dropdown.js
388 ms
component-search-facet-managed-range.js
412 ms
component-search-facet-range-slider.js
410 ms
component-search-facet-slider.js
411 ms
component-search-load-more.js
416 ms
gtm.js
290 ms
component-search-location-filter.js
291 ms
component-search-page-selector.js
185 ms
component-search-page-size.js
209 ms
component-search-parameters.js
205 ms
component-search-query.js
220 ms
component-search-radius-filter.js
208 ms
component-search-results.js
210 ms
component-search-results-count.js
174 ms
component-search-results-filter.js
182 ms
component-search-sort.js
186 ms
component-search-url.js
187 ms
component-search-variant-filter.js
187 ms
component-search-service.js
201 ms
component-search-router.js
195 ms
component-search-facet-daterange.js
212 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
83 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
104 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
113 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf
132 ms
fontawesome-webfont.woff
79 ms
accessibility.js
209 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVc.ttf
132 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVc.ttf
131 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVc.ttf
130 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVc.ttf
130 ms
component-accordions.js
156 ms
component-archive.js
158 ms
component-breadcrumb.js
157 ms
component-carousel.js
157 ms
component-container.js
156 ms
component-disqus.js
157 ms
component-facebook.js
158 ms
component-flash.js
162 ms
component-flip.js
168 ms
component-fullcalendar.js
186 ms
component-galleria.js
155 ms
component-language-selector.js
154 ms
component-navigation.js
162 ms
component-overlay.js
163 ms
component-snippet.js
163 ms
component-social.js
163 ms
component-tabs.js
150 ms
component-toggle.js
183 ms
component-video.js
152 ms
component-video-playlist.js
170 ms
details-polyfill.js
149 ms
fixheight.js
146 ms
search-fixheight.js
165 ms
resolveconflicts.js
160 ms
6-jquery-phone-mask.js
166 ms
pre-optimized-min.js
173 ms
fontawesome-webfont-woff.woff
204 ms
fontawesome-webfont-woff.woff
211 ms
cirh-hero-pastorgreg-v1.jpg
209 ms
schedule-a-tour.svg
186 ms
make-a-referral.svg
184 ms
talk-to-us.svg
185 ms
regency-hospital-pulmonary-vent-liberation-hero.jpg
186 ms
medically-complex-critical-illness-hospital-hero.jpg
187 ms
brain-injury-critical-illness-hospital-hero.jpg
184 ms
neurological-critical-illness-hospital-hero.jpg
198 ms
infectious-disease-critical-illness-hospital-hero.jpg
195 ms
cardiac-critical-illness-hospital-hero.jpg
185 ms
wound-care-critical-illness-hospital-hero.jpg
180 ms
renal-care-critical-illness-hospital-hero.jpg
179 ms
cirh-icon-map-41x41px-01.png
180 ms
cirh-icon-lungs-41x41px-01.png
184 ms
patients-treated-icon.png
184 ms
patient-success-story-infectious-disease-bill-riccio-card.jpg
178 ms
patient-success-story-deandre-laster-medically-complex-card.jpg
174 ms
patient-success-story-neurological-sharon-mortenson-2-card.jpg
175 ms
fb.svg
184 ms
linkedin.svg
176 ms
twitter.svg
189 ms
success-quote.svg
81 ms
regencyhospital.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
regencyhospital.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
regencyhospital.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Regencyhospital.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 Regencyhospital.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
regencyhospital.com
Open Graph description is not detected on the main page of Regency Hospital. 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: