Tools & Wizards About Us
hl7-fhir.github.io screenshot

Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 72

    SEO

    Google-friendlier than
    31% of websites

hl7-fhir.github.io

Page Load Speed

882 ms in total

First Response

97 ms

Resources Loaded

632 ms

Page Rendered

153 ms

hl7-fhir.github.io screenshot

About Website

Click here to check amazing Hl 7 Fhir Github content for China. Otherwise, check out these important facts you probably never knew about hl7-fhir.github.io

Visit hl7-fhir.github.io

Key Findings

We analyzed Hl7-fhir.github.io page load time and found that the first response time was 97 ms and then it took 785 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

hl7-fhir.github.io performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

74/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

hl7-fhir.github.io

97 ms

fhir.css

42 ms

bootstrap.css

77 ms

bootstrap-fhir.css

86 ms

project.css

85 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that all of those requests were addressed to Hl7-fhir.github.io and no external sources were called. The less responsive or slowest element that took the longest time to load (533 ms) belongs to the original domain Hl7-fhir.github.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 228.3 kB (47%)

Content Size

487.2 kB

After Optimization

258.9 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Hl7-fhir.github.io main page is 487.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. 40% of websites need less resources to load. Images take 233.1 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 22.2 kB

  • Original 26.6 kB
  • After minification 24.2 kB
  • After compression 4.5 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 22.2 kB or 83% of the original size.

Image Optimization

-5%

Potential reduce by 12.8 kB

  • Original 233.1 kB
  • After minification 220.3 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. Hl 7 Fhir Github images are well optimized though.

CSS Optimization

-85%

Potential reduce by 193.3 kB

  • Original 227.4 kB
  • After minification 181.3 kB
  • After compression 34.1 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. Hl7-fhir.github.io needs all CSS files to be minified and compressed as it can save up to 193.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (52%)

Requests Now

27

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hl7-fhir.github.io

hl7-fhir.github.io

97 ms

fhir.css

fhir.css

42 ms

bootstrap.css

bootstrap.css

77 ms

bootstrap-fhir.css

bootstrap-fhir.css

86 ms

project.css

project.css

85 ms

pygments-manni.css

pygments-manni.css

116 ms

jquery-ui.css

jquery-ui.css

118 ms

jquery.js

jquery.js

260 ms

bootstrap.min.js

bootstrap.min.js

147 ms

respond.min.js

respond.min.js

177 ms

fhir.js

fhir.js

285 ms

fhir-logo-www.png

fhir-logo-www.png

144 ms

hl7-logo.png

hl7-logo.png

160 ms

search.png

search.png

177 ms

external.png

external.png

185 ms

target.png

target.png

195 ms

icon-documentation.png

icon-documentation.png

353 ms

icon-implementation.png

icon-implementation.png

293 ms

icon-clinical.png

icon-clinical.png

287 ms

icon-administration.png

icon-administration.png

289 ms

icon-infrastructure.png

icon-infrastructure.png

533 ms

cc0.png

cc0.png

397 ms

fhir.css

fhir.css

24 ms

bootstrap.css

bootstrap.css

23 ms

bootstrap-fhir.css

bootstrap-fhir.css

24 ms

project.css

project.css

23 ms

pygments-manni.css

pygments-manni.css

22 ms

jquery-ui.css

jquery-ui.css

22 ms

Accessibility Review

hl7-fhir.github.io accessibility score

64

Accessibility Issues

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

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

[id] attributes on active, focusable elements are not unique

Best Practices

hl7-fhir.github.io best practices score

50

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

hl7-fhir.github.io SEO score

72

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hl7-fhir.github.io can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Hl7-fhir.github.io 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

hl7-fhir.github.io

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