3.1 sec in total
32 ms
2.6 sec
513 ms
Welcome to interoperabilityshowcase.org homepage info - get ready to check Interoperability Showcase best content right away, or after learning these important things about interoperabilityshowcase.org
The HIMSS Interoperability Showcase™ demonstrates the power of standards-based interoperability by showcasing how multiple stakeholders connect health IT to exchange and use data in real time to impro...
Visit interoperabilityshowcase.orgWe analyzed Interoperabilityshowcase.org page load time and found that the first response time was 32 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
interoperabilityshowcase.org performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value7.0 s
6/100
25%
Value12.7 s
3/100
10%
Value6,110 ms
0/100
30%
Value0.139
79/100
15%
Value20.6 s
2/100
10%
32 ms
50 ms
85 ms
112 ms
11 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Interoperabilityshowcase.org, 29% (30 requests) were made to Himss.org and 10% (10 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source M.addthis.com.
Page size can be reduced by 399.0 kB (56%)
706.7 kB
307.7 kB
In fact, the total size of Interoperabilityshowcase.org main page is 706.7 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. HTML takes 365.6 kB which makes up the majority of the site volume.
Potential reduce by 298.2 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 298.2 kB or 82% of the original size.
Potential reduce by 7.6 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. Interoperability Showcase images are well optimized though.
Potential reduce by 11.5 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. This website has mostly compressed JavaScripts.
Potential reduce by 81.7 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. Interoperabilityshowcase.org needs all CSS files to be minified and compressed as it can save up to 81.7 kB or 60% of the original size.
Number of requests can be reduced by 69 (81%)
85
16
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Interoperability Showcase. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
interoperabilityshowcase.org
32 ms
himss-interoperability-showcase
50 ms
latest.min.js
85 ms
gpt.js
112 ms
fonts.js
11 ms
gtm.js
151 ms
addthis_widget.js
109 ms
css_HHHeAHEOY8Rn-4-SaaNJjRvACarLNQgkHwdsB9xPsdA.css
37 ms
css_wF7kgOaZAxusRx2wT_Hi4Cfi6UWsqzy1KTw0V5YR9ss.css
65 ms
font-awesome.min.css
109 ms
css_hmesIomKx7EfrmqbbBKKHQnI8wuEcHqjnqSBYcVJjcA.css
65 ms
js_Begq96ZmU0EAWRfYgZoK_ya9Uk5Dj9KtvxXQKEV9iLw.js
64 ms
underscore-min.js
72 ms
js_d7KsC2SV2brL8Qm1UmOyS4aJ7w_TeY8HcS7Vk9PtBqE.js
57 ms
popper.min.js
109 ms
js_FIv4FA6VIRFl6uqsoHRw1Idsm-g8VHKYkzE01pHKg5s.js
63 ms
css-vars-ponyfill@2
106 ms
js_DnSdrnO02amz2rBuDESjSycmVWNxEb3L8TPs41JI_fU.js
62 ms
eu_cookie_compliance.js
67 ms
js_lC2Ua9YUmFSMos8zr57_KruliWvvkO1aJQPqecN9840.js
69 ms
mburger.js
72 ms
js_3WI_gbXfkeQj7ipRtFi-FH8EmLkZD-wBrqRbIxz4WCo.js
70 ms
min.js
107 ms
js_VTFFEdWEQSQdMUfLXuj3Af9BUTdYhNngIrDNjuwKR40.js
67 ms
webfont.js
69 ms
fonts.css
32 ms
vzq7qoi.css
72 ms
f90a09148820c55399932d701b9bb01a
51 ms
pubads_impl_2022092701.js
58 ms
ppub_config
56 ms
p.css
199 ms
f90a09148820c55399932d701b9bb01a
109 ms
optimize.js
379 ms
analytics.js
376 ms
hotjar-592673.js
615 ms
js
83 ms
3bd64e1f-86a9-49c5-a71a-1e1b7661fb2f
286 ms
f90a09148820c55399932d701b9bb01a
300 ms
moatframe.js
574 ms
HIMSSlogo_Hwhitelogotype_RGB.svg
146 ms
search_icon.svg
134 ms
lazysizes-1x1.png
378 ms
arrow_forward.svg
136 ms
accelerate-mark-color.png
139 ms
fbevents.js
422 ms
insight.min.js
596 ms
munchkin.js
854 ms
uwt.js
899 ms
collect.js
270 ms
_ate.track.config_resp
878 ms
300lo.json
1085 ms
fonts.css
254 ms
vzq7qoi.css
246 ms
css_HHHeAHEOY8Rn-4-SaaNJjRvACarLNQgkHwdsB9xPsdA.css
250 ms
css_wF7kgOaZAxusRx2wT_Hi4Cfi6UWsqzy1KTw0V5YR9ss.css
264 ms
font-awesome.min.css
261 ms
css_hmesIomKx7EfrmqbbBKKHQnI8wuEcHqjnqSBYcVJjcA.css
266 ms
Verlag-Light.woff
303 ms
Verlag-XLight.woff
386 ms
Verlag-Book.woff
386 ms
Verlag-Bold.woff
435 ms
Verlag-Black.woff
450 ms
d
385 ms
d
822 ms
d
776 ms
d
824 ms
d
492 ms
d
775 ms
d
820 ms
d
1040 ms
fontawesome-webfont.woff
775 ms
sh.f48a1a04fe8dbf021b4cda1d.html
269 ms
collect
328 ms
collect
324 ms
p.css
285 ms
modules.61e17720cf639c3e96a7.js
798 ms
collect
576 ms
collect
575 ms
1663010833996523
525 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
709 ms
collect
654 ms
collect
948 ms
munchkin.js
133 ms
703907503302065
116 ms
layers.fa6cd1947ce26e890d3d.js
113 ms
oct.js
110 ms
behavior-addiction-mgmt-x.jpg
107 ms
pathfora.min.js
104 ms
visitWebPage
752 ms
visitWebPage
766 ms
adsct
512 ms
adsct
511 ms
ga-audiences
466 ms
pathfora.min.css
119 ms
himss-overrides.css
179 ms
ga-audiences
201 ms
adsct
149 ms
adsct
140 ms
adsct
148 ms
adsct
149 ms
css
135 ms
css
149 ms
css
155 ms
config.js
27 ms
19 ms
interoperabilityshowcase.org accessibility score
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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
interoperabilityshowcase.org 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
interoperabilityshowcase.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Interoperabilityshowcase.org 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 Interoperabilityshowcase.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.
interoperabilityshowcase.org
Open Graph data is detected on the main page of Interoperability Showcase. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: