Tools & Wizards About Us
hmedata.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

hmedata.com

HMEdata.com - HME billing data - NPI Search Lookup, UPIN, ICD-9, Medicare Fee Schedule

Page Load Speed

1.1 sec in total

First Response

56 ms

Resources Loaded

922 ms

Page Rendered

119 ms

hmedata.com screenshot

About Website

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

Tech-Savvy's HMEdata.com - The HME Billing Data Experts! Free NPI,UPIN, ICD9, Medicare Allowables, Medigap Database Searches.

Visit hmedata.com

Key Findings

We analyzed Hmedata.com page load time and found that the first response time was 56 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

hmedata.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value6.4 s

41/100

10%

TBT (Total Blocking Time)

Value5,700 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

hmedata.com

56 ms

Default.asp

86 ms

gtm.js

71 ms

hd_main.css

10 ms

api.js

52 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 13% of them (6 requests) were addressed to the original Hmedata.com, 20% (9 requests) were made to Static.xx.fbcdn.net and 7% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (300 ms) relates to the external source Facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 183.6 kB (28%)

Content Size

653.7 kB

After Optimization

470.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hmedata.com main page is 653.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. 50% of websites need less resources to load. Javascripts take 503.6 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 23.2 kB

  • Original 31.7 kB
  • After minification 28.3 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 3.4 kB, which is 11% 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 23.2 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 3.6 kB

  • Original 112.9 kB
  • After minification 109.4 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. HMEdata images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 153.2 kB

  • Original 503.6 kB
  • After minification 503.6 kB
  • After compression 350.4 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 153.2 kB or 30% of the original size.

CSS Optimization

-67%

Potential reduce by 3.6 kB

  • Original 5.4 kB
  • After minification 4.5 kB
  • After compression 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. Hmedata.com needs all CSS files to be minified and compressed as it can save up to 3.6 kB or 67% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (58%)

Requests Now

40

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hmedata.com

hmedata.com

56 ms

Default.asp

Default.asp

86 ms

gtm.js

gtm.js

71 ms

hd_main.css

hd_main.css

10 ms

api.js

api.js

52 ms

show_ads.js

show_ads.js

119 ms

pubcode.min.js

pubcode.min.js

67 ms

pubcode.min.js

pubcode.min.js

144 ms

recaptcha__en.js

recaptcha__en.js

108 ms

all.js

all.js

65 ms

hmedata.gif

hmedata.gif

13 ms

ds.jpg

ds.jpg

63 ms

firestick4k.jpg

firestick4k.jpg

103 ms

js

js

112 ms

analytics.js

analytics.js

184 ms

destination

destination

184 ms

bat.js

bat.js

247 ms

all.js

all.js

43 ms

adsbygoogle.js

adsbygoogle.js

237 ms

get.media

get.media

217 ms

cookie_sync

cookie_sync

150 ms

collect

collect

151 ms

137 ms

300x250_default.jpg

300x250_default.jpg

145 ms

fallback

fallback

36 ms

like_box.php

like_box.php

160 ms

likebox.php

likebox.php

300 ms

collect

collect

54 ms

fallback__ltr.css

fallback__ltr.css

17 ms

39 ms

css

css

36 ms

22 ms

logo_48.png

logo_48.png

4 ms

font

font

19 ms

moyZY4gLn_0.css

moyZY4gLn_0.css

20 ms

SHojUHmeyWm.js

SHojUHmeyWm.js

35 ms

teTZ2tZqwkq.js

teTZ2tZqwkq.js

34 ms

D0hW5UcG2V4.js

D0hW5UcG2V4.js

59 ms

qnn7MVQZYOT.js

qnn7MVQZYOT.js

63 ms

7CmGfGBVS6H.js

7CmGfGBVS6H.js

62 ms

OWkNLphO4cA.js

OWkNLphO4cA.js

65 ms

p55HfXW__mM.js

p55HfXW__mM.js

62 ms

305850841_193235103080107_789037547458595246_n.png

305850841_193235103080107_789037547458595246_n.png

60 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

38 ms

305850841_193235103080107_789037547458595246_n.png

305850841_193235103080107_789037547458595246_n.png

7 ms

Accessibility Review

hmedata.com accessibility score

72

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Best Practices

hmedata.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

hmedata.com SEO score

69

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hmedata.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 Hmedata.com main page’s claimed encoding is iso-8859-1. 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.

Social Sharing Optimization

hmedata.com

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