MEDICARE.GOV Medicare.gov: the official U.S. government site for Medicare | Medicare


medicare.gov website information.

medicare.gov domain name is registered by .GOV top-level domain registry. See the other sites registred in .GOV domain zone.

No name server records were found.

and probably website medicare.gov is hosted by FACEBOOK - Facebook, Inc., US web hosting company. Check the complete list of other most popular websites hosted by FACEBOOK - Facebook, Inc., US hosting company.

According to Alexa traffic rank the highest website medicare.gov position was 2055 (in the world). The lowest Alexa rank position was 172428. Now website medicare.gov ranked in Alexa database as number 5665 (in the world).

Website medicare.gov Desktop speed measurement score (62/100) is better than the results of 38.44% of other sites shows that the page desktop performance can be improved.

medicare.gov Mobile usability score (96/100) is better than the results of 46.59% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of medicare.gov (51/100) is better than the results of 35.73% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Oct-07-2022 5,665-2,773
Oct-06-2022 2,8928,129
Oct-05-2022 11,0211,602
Oct-04-2022 12,623-4,556
Oct-03-2022 8,067-2,333
Oct-02-2022 5,7345,951
Oct-01-2022 11,685-2,561

Advertisement

medicare.gov Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



medicare.gov whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


% DOTGOV WHOIS Server ready
Domain Name: MEDICARE.GOV
Status: ACTIVE
Security Contact Email: responsibledisclosure@hhs.gov

>>> Last update of whois database: 2021-04-25T02:15:48Z

medicare.gov server information

Servers Location

IP Address
Country
Region
City

medicare.gov desktop page speed rank

Last tested: 2019-12-04


Desktop Speed Bad
62/100

medicare.gov Desktop Speed Test Quick Summary


priority - 32 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 6 blocking script resources and 5 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://assets.cms.gov/Resources/Global/JS/lib/jquery-1.7.2.js
https://assets.cms.gov/Resources/Global/JS/sharewidget-4.0.js
https://tags.tiqcdn.com/utag/cmsgov/medicare-www/prod/utag.sync.js
https://www.medicare.gov/optimizely/optimizely-medicare.js
https://www.medicare.gov/sites/default/files/js/js…F8RSBYzu5WPUD4XVEyA.js
https://www.medicare.gov/static/d72d76e0cb0170b38c42782b811d5d7

Optimize CSS Delivery of the following:

https://www.medicare.gov/sites/default/files/css/c…l_jWqHHNYsw.css?q1wn82
https://www.medicare.gov/sites/default/files/css/c…4irPu5Dvn3A.css?q1wn82
https://assets.cms.gov/resources/global/css/sharewidget-4.0.css
https://assets.cms.gov/resources/libs/fonts/adobeBlank/adobe-blank.css
https://fonts.googleapis.com/css?family=Open+Sans:800,400

priority - 10 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://assets.cms.gov/Resources/Global/JS/lib/jquery-1.7.2.js (expiration not specified)
https://assets.cms.gov/Resources/Global/JS/sharewidget-4.0.js (expiration not specified)
https://assets.cms.gov/resources/global/css/sharewidget-4.0.css (expiration not specified)
https://assets.cms.gov/resources/libs/fonts/adobeBlank/adobe-blank.css (expiration not specified)
https://content.govdelivery.com/attachments/fancy_…verlay-01_original.png (expiration not specified)
https://content.govdelivery.com/attachments/fancy_…verlay-02_original.png (expiration not specified)
https://content.govdelivery.com/attachments/fancy_…rlay-2-bg_original.jpg (expiration not specified)
https://content.govdelivery.com/attachments/fancy_…y-reverse_original.png (expiration not specified)
https://content.govdelivery.com/overlay/js/7993.js (expiration not specified)
https://www.medicare.gov/optimizely/optimizely-medicare.js (expiration not specified)
https://zn56jl522ec1a1wzf-medicare.gov1.siteinterc…%2Fwww.medicare.gov%2F (60 seconds)
https://tags.tiqcdn.com/utag/cmsgov/medicare-www/prod/utag.js (5 minutes)
https://tags.tiqcdn.com/utag/cmsgov/medicare-www/prod/utag.sync.js (5 minutes)
https://tags.tiqcdn.com/utag/tiqapp/utag.v.js?a=cm…92013&cb=1575464421229 (10 minutes)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://www.googletagmanager.com/gtag/js?id=AW-784…_rnd=0.267734139226377 (15 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://js-agent.newrelic.com/nr-spa-1153.min.js (2 hours)
https://static.chartbeat.com/js/chartbeat.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)
https://cdn.quantummetric.com/qscripts/quantum-medicare.js (4 hours)
https://cdn3.optimizely.com/js/geo2.js (10.8 hours)

priority - 9 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://medicare.gov/
https://medicare.gov/
https://www.medicare.gov/

priority - 5 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 49KiB (31% reduction).

Minifying https://assets.cms.gov/Resources/Global/JS/lib/jquery-1.7.2.js could save 37.4KiB (49% reduction) after compression.
Minifying https://www.medicare.gov/sites/default/files/js/js…F8RSBYzu5WPUD4XVEyA.js could save 11.3KiB (15% reduction) after compression.
Minifying https://assets.cms.gov/Resources/Global/JS/sharewidget-4.0.js could save 255B (14% reduction) after compression.

priority - 4 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 43.1KiB (25% reduction).

Compressing https://content.govdelivery.com/attachments/fancy_…rlay-2-bg_original.jpg could save 32.8KiB (32% reduction).
Compressing https://www.medicare.gov/sites/default/files/headerlogo.png could save 4.3KiB (11% reduction).
Compressing https://www.medicare.gov/themes/custom/medicare_ba…dicare-footer-logo.png could save 1.6KiB (16% reduction).
Compressing https://yt3.ggpht.com/-ugqRBvM0WfY/AAAAAAAAAAI/AAA…rj-c0xffffff/photo.jpg could save 954B (38% reduction).
Compressing https://www.medicare.gov/sites/default/files/2020-plan-costs.png could save 644B (40% reduction).
Compressing https://www.medicare.gov/themes/custom/medicare_ba…es/hhs-footer-logo.png could save 644B (30% reduction).
Compressing https://content.govdelivery.com/attachments/fancy_…verlay-02_original.png could save 633B (21% reduction).
Compressing https://content.govdelivery.com/attachments/fancy_…verlay-01_original.png could save 553B (19% reduction).
Compressing https://content.govdelivery.com/attachments/fancy_…y-reverse_original.png could save 411B (37% reduction).
Compressing https://www.medicare.gov/sites/default/files/findcare.png could save 408B (32% reduction).
Compressing https://www.medicare.gov/sites/default/files/whatscovered.png could save 201B (15% reduction).

priority - 2 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 66% of the final above-the-fold content could be rendered with the full HTML response.
Click to see the screenshot with only the HTML response:

priority - 1 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 13.7KiB (72% reduction).

Compressing https://dap.digitalgov.gov/Universal-Federated-Ana…ncy=DHHS&subagency=CMS could save 13.4KiB (73% reduction).
Compressing https://visitor-service-us-east-1.tealiumiq.com/cm…2%5D&rnd=1575464421858 could save 270B (48% reduction).

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 111B (12% reduction).

Minifying https://assets.cms.gov/resources/global/css/sharewidget-4.0.css could save 111B (12% reduction) after compression.

medicare.gov Desktop Resources

Total Resources101
Number of Hosts34
Static Resources51
JavaScript Resources46
CSS Resources6

medicare.gov Desktop Resource Breakdown

medicare.gov mobile page speed rank

Last tested: 2019-12-04


Mobile Speed Bad
51/100

medicare.gov Mobile Speed Test Quick Summary


priority - 48 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://assets.cms.gov/Resources/Global/JS/lib/jquery-1.7.2.js
https://assets.cms.gov/Resources/Global/JS/sharewidget-4.0.js
https://tags.tiqcdn.com/utag/cmsgov/medicare-www/prod/utag.sync.js
https://www.medicare.gov/optimizely/optimizely-medicare.js

Optimize CSS Delivery of the following:

https://www.medicare.gov/sites/default/files/css/c…l_jWqHHNYsw.css?q1zuqp
https://www.medicare.gov/sites/default/files/css/c…4irPu5Dvn3A.css?q1zuqp
https://assets.cms.gov/resources/global/css/sharewidget-4.0.css
https://assets.cms.gov/resources/libs/fonts/adobeBlank/adobe-blank.css

priority - 34 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://medicare.gov/
https://medicare.gov/
https://www.medicare.gov/

priority - 14 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://assets.cms.gov/Resources/Global/JS/lib/jquery-1.7.2.js (expiration not specified)
https://assets.cms.gov/Resources/Global/JS/sharewidget-4.0.js (expiration not specified)
https://assets.cms.gov/resources/global/css/sharewidget-4.0.css (expiration not specified)
https://assets.cms.gov/resources/libs/fonts/adobeBlank/adobe-blank.css (expiration not specified)
https://content.govdelivery.com/attachments/fancy_…verlay-01_original.png (expiration not specified)
https://content.govdelivery.com/attachments/fancy_…verlay-02_original.png (expiration not specified)
https://content.govdelivery.com/overlay/js/7993.js (expiration not specified)
https://www.medicare.gov/optimizely/optimizely-medicare.js (expiration not specified)
https://zn56jl522ec1a1wzf-medicare.gov1.siteinterc…%2Fwww.medicare.gov%2F (60 seconds)
https://tags.tiqcdn.com/utag/cmsgov/medicare-www/prod/utag.js (5 minutes)
https://tags.tiqcdn.com/utag/cmsgov/medicare-www/prod/utag.sync.js (5 minutes)
https://tags.tiqcdn.com/utag/tiqapp/utag.v.js?a=cm…92013&cb=1575484488686 (10 minutes)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://www.googletagmanager.com/gtag/js?id=AW-784…rnd=0.2654579575173557 (15 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://js-agent.newrelic.com/nr-spa-1153.min.js (2 hours)
https://static.chartbeat.com/js/chartbeat.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)
https://cdn.quantummetric.com/qscripts/quantum-medicare.js (4 hours)
https://cdn3.optimizely.com/js/geo2.js (6.8 hours)

priority - 5 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 49KiB (31% reduction).

Minifying https://assets.cms.gov/Resources/Global/JS/lib/jquery-1.7.2.js could save 37.4KiB (49% reduction) after compression.
Minifying https://www.medicare.gov/sites/default/files/js/js…F8RSBYzu5WPUD4XVEyA.js could save 11.3KiB (15% reduction) after compression.
Minifying https://assets.cms.gov/Resources/Global/JS/sharewidget-4.0.js could save 255B (14% reduction) after compression.

priority - 1 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 13.7KiB (72% reduction).

Compressing https://dap.digitalgov.gov/Universal-Federated-Ana…ncy=DHHS&subagency=CMS could save 13.4KiB (73% reduction).
Compressing https://visitor-service-us-east-1.tealiumiq.com/cm…2%5D&rnd=1575484489340 could save 281B (49% reduction).

priority - 1 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 9.8KiB (15% reduction).

Compressing https://www.medicare.gov/sites/default/files/headerlogo.png could save 4.3KiB (11% reduction).
Compressing https://www.medicare.gov/themes/custom/medicare_ba…dicare-footer-logo.png could save 1.6KiB (16% reduction).
Compressing https://yt3.ggpht.com/-ugqRBvM0WfY/AAAAAAAAAAI/AAA…rj-c0xffffff/photo.jpg could save 954B (38% reduction).
Compressing https://www.medicare.gov/sites/default/files/2020-plan-costs.png could save 644B (40% reduction).
Compressing https://www.medicare.gov/themes/custom/medicare_ba…es/hhs-footer-logo.png could save 644B (30% reduction).
Compressing https://content.govdelivery.com/attachments/fancy_…verlay-02_original.png could save 633B (21% reduction).
Compressing https://content.govdelivery.com/attachments/fancy_…verlay-01_original.png could save 553B (19% reduction).
Compressing https://www.medicare.gov/sites/default/files/findcare.png could save 408B (32% reduction).
Compressing https://www.medicare.gov/sites/default/files/whatscovered.png could save 201B (15% reduction).

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 111B (12% reduction).

Minifying https://assets.cms.gov/resources/global/css/sharewidget-4.0.css could save 111B (12% reduction) after compression.

medicare.gov Mobile Resources

Total Resources96
Number of Hosts34
Static Resources49
JavaScript Resources45
CSS Resources6

medicare.gov Mobile Resource Breakdown

medicare.gov mobile page usability

Last tested: 2019-12-04


Mobile Usability Good
96/100

medicare.gov Mobile Usability Test Quick Summary


priority - 3 Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 418 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

The element <main id="content" class="column main-co…empty-sidebar2">Medicare.gov:…Television Ad</main> falls outside the viewport.

priority - 0 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <button id="open-mobile-aux" class="mobile-auxnav-…-display--none">Expand Resource Menu</button> is close to 2 other tap targets.

The tap target <button id="open-mobile-aux" class="mobile-auxnav-…-display--none">Expand Resource Menu</button> is close to 2 other tap targets.

The tap target <div id="homecard1" class="ds-l-sm-col--1…l--3 home-card">2020 Costs See basic costs</div> is close to 1 other tap targets.

The tap target <div id="prefix-overlay-header">Close subscription dialog</div> and 1 others are close to other tap targets.

medicare.gov similar domains

Similar domains:
www.medicare.com
www.medicare.net
www.medicare.org
www.medicare.info
www.medicare.biz
www.medicare.us
www.medicare.mobi
www.edicare.gov
www.medicare.gov
www.nedicare.gov
www.mnedicare.gov
www.nmedicare.gov
www.jedicare.gov
www.mjedicare.gov
www.jmedicare.gov
www.kedicare.gov
www.mkedicare.gov
www.kmedicare.gov
www.mdicare.gov
www.mwdicare.gov
www.mewdicare.gov
www.mwedicare.gov
www.msdicare.gov
www.mesdicare.gov
www.msedicare.gov
www.mddicare.gov
www.meddicare.gov
www.mdedicare.gov
www.mrdicare.gov
www.merdicare.gov
www.mredicare.gov
www.meicare.gov
www.mexicare.gov
www.medxicare.gov
www.mexdicare.gov
www.mesicare.gov
www.medsicare.gov
www.meeicare.gov
www.medeicare.gov
www.meedicare.gov
www.mericare.gov
www.medricare.gov
www.meficare.gov
www.medficare.gov
www.mefdicare.gov
www.mecicare.gov
www.medcicare.gov
www.mecdicare.gov
www.medcare.gov
www.meducare.gov
www.mediucare.gov
www.meduicare.gov
www.medjcare.gov
www.medijcare.gov
www.medjicare.gov
www.medkcare.gov
www.medikcare.gov
www.medkicare.gov
www.medocare.gov
www.mediocare.gov
www.medoicare.gov
www.mediare.gov
www.medixare.gov
www.medicxare.gov
www.medixcare.gov
www.medidare.gov
www.medicdare.gov
www.medidcare.gov
www.medifare.gov
www.medicfare.gov
www.medifcare.gov
www.medivare.gov
www.medicvare.gov
www.medivcare.gov
www.medicre.gov
www.medicqre.gov
www.medicaqre.gov
www.medicqare.gov
www.medicwre.gov
www.medicawre.gov
www.medicware.gov
www.medicsre.gov
www.medicasre.gov
www.medicsare.gov
www.mediczre.gov
www.medicazre.gov
www.mediczare.gov
www.medicae.gov
www.medicaee.gov
www.medicaree.gov
www.medicaere.gov
www.medicade.gov
www.medicarde.gov
www.medicadre.gov
www.medicafe.gov
www.medicarfe.gov
www.medicafre.gov
www.medicate.gov
www.medicarte.gov
www.medicatre.gov
www.medicar.gov
www.medicarw.gov
www.medicarew.gov
www.medicarwe.gov
www.medicars.gov
www.medicares.gov
www.medicarse.gov
www.medicard.gov
www.medicared.gov
www.medicarr.gov
www.medicarer.gov
www.medicarre.gov

medicare.gov Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


medicare.gov TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.