4.3 sec in total
18 ms
3.3 sec
981 ms
Click here to check amazing Eligible content for United States. Otherwise, check out these important facts you probably never knew about eligible.com
Insurance billing APIs for healthcare businesses. Eligible is the easiest way for healthcare developers to add insurance billing experiences into their mobile and web applications.
Visit eligible.comWe analyzed Eligible.com page load time and found that the first response time was 18 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
eligible.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value6.4 s
10/100
25%
Value4.4 s
74/100
10%
Value730 ms
41/100
30%
Value0.244
51/100
15%
Value9.9 s
28/100
10%
18 ms
87 ms
9 ms
31 ms
54 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 52% of them (32 requests) were addressed to the original Eligible.com, 6% (4 requests) were made to Api.segment.io and 6% (4 requests) were made to Js.intercomcdn.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Api.segment.io.
Page size can be reduced by 1.5 MB (50%)
3.0 MB
1.5 MB
In fact, the total size of Eligible.com main page is 3.0 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. 70% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 161.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 161.4 kB or 84% of the original size.
Potential reduce by 202.5 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. Obviously, Eligible needs image optimization as it can save up to 202.5 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.0 MB
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 1.0 MB or 65% of the original size.
Potential reduce by 129.5 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. Eligible.com needs all CSS files to be minified and compressed as it can save up to 129.5 kB or 81% of the original size.
Number of requests can be reduced by 13 (24%)
54
41
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eligible. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
eligible.com
18 ms
eligible.com
87 ms
main-29bae4a3b326e5d0f9cc4de82081d28a.css
9 ms
modernizr-ac36a78b40010b3b7021993ec268ea84.js
31 ms
application-6e7c8356c0a781359b4992e1ab270395.js
54 ms
plugins-1707d0c5f55bba07e50549f7b8107e29.js
90 ms
main-e23c3bdc3481883fbf48481bcf7af381.js
44 ms
canvas-anim-aabc24514609d57e4a3c1de3576bd729.js
52 ms
style.css
389 ms
analytics.min.js
506 ms
clouds-6e8e5cc922a1eced5ef8328e9a2c12c7.png
520 ms
misc-claim-code2@2x-b0f7afd501925b10120a4cbb461a645f.png
484 ms
sherry-637680398b52514e75fac5a30cd1a37c.png
483 ms
laurence-856d8f8793bc2b71c3c49d13d962044b.png
483 ms
AshleySylvia-4b32ef5b46ce1ab08586dad665708d4c.jpg
481 ms
jordan-bc25171c8a34c1f79f1bdbf5dff4905f.png
485 ms
Arpita-d1d5ed32c072c2b8a9e2fdaf7f8b3acb.jpg
485 ms
macbook-iphone-a9db1b7ac214fae1cc422b873ab31c2f.png
497 ms
proximanova-regular-webfont-4ef715621842dcaf9dab2dd8facbeb36.woff
101 ms
proximanova-semibold-webfont-ecc3e870c53c0defcc72bdbc152342f4.woff
103 ms
proximanova-light-webfont-95f9811022b9f105b9caee26ca84c9bb.woff
109 ms
proximanova-bold-webfont-7a2b5d9186dc4ed782fb80236f1f2477.woff
108 ms
EligibleAPI.ttf
366 ms
i
1060 ms
p
1027 ms
t
1024 ms
t
1022 ms
analytics.js
463 ms
heap-3206696494.js
489 ms
d53bs80w
520 ms
mixpanel-2-latest.min.js
563 ms
h
48 ms
identify
47 ms
h
38 ms
intercom.bcfdf787.js
109 ms
178 ms
156 ms
155 ms
echo.515e8809.js
39 ms
ping
437 ms
nr-885.min.js
689 ms
animation-cd2dc678d5c6a45662ead82ddf095da6.json
14 ms
paths-27d10d97141be676ec21da1775b487e2.json
21 ms
config-814e99bdf76c26ce09d019fc5bb5b322.json
14 ms
humana-2301121b969c1eb396a4f572afa5287e.svg
14 ms
bsoc-4b02a90dba5e520cd29e29e95f5e53ed.svg
15 ms
wellmark-f4de9812e1d989ac9afdd3f24b31720a.svg
16 ms
cigna-d5c7c4533574df6b49e4e60dbd2f9561.svg
16 ms
humana-2301121b969c1eb396a4f572afa5287e.svg
409 ms
bsoc-4b02a90dba5e520cd29e29e95f5e53ed.svg
334 ms
wellmark-f4de9812e1d989ac9afdd3f24b31720a.svg
477 ms
cigna-d5c7c4533574df6b49e4e60dbd2f9561.svg
436 ms
logotype-eligible-cf13b72634fe976161a9e01a1927b9c2.svg
501 ms
events
552 ms
sherry4.jpg
375 ms
icon-launcher-acquire.8a742481.png
313 ms
client-test
438 ms
client-test
412 ms
icon-preview-close.ec1a68fc.png
313 ms
HSP_5684_pp.jpg
364 ms
IMG_0239.jpg
364 ms
c214c390af
253 ms
eligible.com accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
eligible.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
eligible.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eligible.com 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 Eligible.com 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.
eligible.com
Open Graph description is not detected on the main page of Eligible. 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: