Your Website Score is

Similar Ranking

54
LOWE'S HOME IMPROVEMENT
lowes.com
54
RADIO--- ASIA
rfa.org
54
NAIRALAND FORUM
nairaland.com
54
RENT THE RUNWAY | RENT UNLIMITED DESIGNER CLOTHING, DRESSES, ACCESSORIES
renttherunway.com
54
BACKSTAGE | AUDITIONS, CASTING CALLS, JOBS, TALENT SEEKING, ADVICE
backstage.com
54
BROWSE SAFELY AND STEER CLEAR OF ONLINE DANGERS | MCAFEE WEBADVISOR
siteadvisor.com
54
NICHE: EXPLORE SCHOOLS, COMPANIES, AND NEIGHBORHOODS
niche.com

Latest Sites

14
OSLOWAY | YOUR BEST LOCAL TOURS AND EXPERIENCES IN OSLO
osloway.no
22
JUST A MOMENT...
hourlyminer.com
33
ピアノ教室ネット|先生との出会いはここから。全国のピアノ教室から検索!
pnet.kawai.jp
19
ADAGIETTOピアノ教室|飯能|ピアノに興味がある皆さんへ|
adagiettopiano.com
33
ГЛАВНАЯ | UNIEX
uniex.biz
23
AHMADIMADO - TRUSTED DOGECOIN CLOUD MINING
ahmadimado.net
19
DOGESILVA LIMITED - HOME
dogesilva.com

Top Technologies

Nginx
Web Servers
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

54 medicare.gov Last Updated: 7 months

Success 62% of passed verification steps
Warning 15% of total warning
Errors 23% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 64%
Best Practices Desktop Score 69%
SEO Desktop Score 91%
Progressive Web App Desktop Score 27%
Performance Mobile Score 13%
Best Practices Mobile Score 69%
SEO Mobile Score 92%
Progressive Web App Mobile Score 26%
Page Authority Authority 65%
Domain Authority Domain Authority 79%
Moz Rank 6.5/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 71 Characters
MEDICARE.GOV: THE OFFICIAL U.S. GOVERNMENT SITE FOR MEDICARE | MEDICARE
Meta Description 0 Characters
NO DATA
Effective URL 24 Characters
https://www.medicare.gov
Excerpt Page content
Medicare.gov: the official U.S. government site for Medicare | Medicare Skip to main content Expand Main Menu close resourc...
Keywords Cloud Density
medicare59 part24 what21 health20 costs19 plans16 drug15 coverage12 privacy11 insurance11
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
medicare 59
part 24
what 21
health 20
costs 19
plans 16
drug 15
coverage 12
privacy 11
insurance 11
Google Preview Your look like this in google search result
MEDICARE.GOV: THE OFFICIAL U.S. GOVERNMENT SITE FOR MEDICARE
https://www.medicare.gov
Medicare.gov: the official U.S. government site for Medicare | Medicare Skip to main content Expand Main Menu close resourc...
Robots.txt File Detected
Sitemap.xml File Detected
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
Updated: 1970-01-01 / 51 years
Create on: 1970-01-01 / 51 years
Expires on: 1970-01-01 / 616 months 9 days
Page Size Code & Text Ratio
Document Size: ~94.55 KB
Code Size: ~85.68 KB
Text Size: ~8.88 KB Ratio: 9.39%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
User Timing marks and measures 4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Server response times are low (TTFB) Root document took 500 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 400 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 15 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 160 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Total Blocking Time 550 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 1.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 6 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Speed Index 2.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 3.3 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 2,439 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 2.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 1.1 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 16 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoids an excessive DOM size 671 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Minify JavaScript Potential savings of 58 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.3 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 99 requests • 2,439 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 53 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 250 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 3.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 18.0 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 60 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Remove unused CSS Potential savings of 87 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 750 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Mobile

Mobile Screenshot
Serve images in next-gen formats Potential savings of 698 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
User Timing marks and measures 4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Server response times are low (TTFB) Root document took 160 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 960 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Reduce the impact of third-party code Third-party code blocked the main thread for 1,920 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Total Blocking Time 4,860 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 8.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Defer offscreen images Potential savings of 18 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 9.4 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 15.0 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 2,384 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 11.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 4.9 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 16 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoids an excessive DOM size 681 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Minify JavaScript Potential savings of 58 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 5.6 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 98 requests • 2,384 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 51 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 1,100 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 18.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Page load is not fast enough on mobile networks Interactive at 18.3 s
A fast page load over a cellular network ensures a good mobile user experience
First Contentful Paint (3G) 10440 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Estimated Input Latency 670 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Tap targets are sized appropriately 100% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Document uses legible font sizes 98.62% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Remove unused CSS Potential savings of 89 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Accept-Ranges: bytes
Cache-Control: max-age=2764800, public
Content-Encoding: gzip
Content-Language: en
Content-Type: text/html; charset=UTF-8
ETag: "1578409159"
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Last-Modified: Tue, 07 Jan 2020 14:59:19 GMT
Link: ; rel="shortlink", ; rel="canonical"
Link: ; rel="alternate"; hreflang="en"
Link: ; rel="revision"
X-Age: 2607
X-AH-Environment: prod
X-Cache-Hits: 32
X-Content-Type-Options: nosniff
X-Drupal-Cache: HIT
X-Drupal-Dynamic-Cache: MISS
X-Generator: Drupal 8 (https://www.drupal.org)
X-Request-ID: v-6a213168-315e-11ea-99cf-db5916f7f930
X-UA-Compatible: IE=edge
Content-Length: 22588
Date: Wed, 08 Jan 2020 00:45:04 GMT
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: optimizelyEndUserId=5d83d717c44e00001026155e0c010000481c0000; expires=Fri, 07-Jan-2022 00:45:04 GMT; path=/; domain=.medicare.gov; secure
Set-Cookie: _ga=GA1.2.1362499118.1578444304; expires=Fri, 07-Jan-2022 00:45:04 GMT; path=/; domain=.medicare.gov; secure
Strict-Transport-Security: max-age=31536000
Set-Cookie: akavpau_default=1578444604~id=3b41b40f209863b260f1b44290ed3dea; Path=/
X-Frame-Options: SAMEORIGIN
Set-Cookie: bm_sz=9E0939EDE4C532970655B21F6429AEBB~YAAQXYPXF2+Zf3xvAQAAja+cggbRCSBE/lRPNAqg8HxzLDTCk4n+MFz1y2UAnGt+WSx3JyWfyp9WyYEFQ86GyfQoNsLVp1JpLBt+Bgg6PpmUS6WHqKF5V/cSLqZ97VCS+QNXx5eU9TB4i/fgtF4mevlHgXJC/KuV2DxiZ1+R7uXf/EzjOdExTWImbMvABUzAVV8=; Domain=.medicare.gov; Path=/; Expires=Wed, 08 Jan 2020 04:45:04 GMT; Max-Age=14400; HttpOnly
Set-Cookie: _abck=E35898A27831F21414C13E0F9E747AC3~-1~YAAQXYPXF3CZf3xvAQAAja+cggO2urD3Wqr9ld5aI7/IodOVUMIKYagXyKdhrBbuAZR0tHCVNHlHwSqxzEXPB9ooay+KBd74WUeBqYvRd0Co96A2WTEDeHrq3Y1ku1+dD4DauW/BnQCASoJ0SerDRkkCAMH7BNLmGEOyX2Zh5o4GNKiI/vlWzGJ2fFzj8Pz3WzMJcZj3aLPriOubNYu/XJ5eo6pofXBp2l07ZU5Hcg0qpBdYJ2RZyl3FwdcqGjDXaqsfE3daFmIT2OPtm2IS4MIYa1hkKYP6LWX52px5bFP3dPGv5YBVHrpUazA=~-1~-1~-1; Domain=.medicare.gov; Path=/; Expires=Thu, 07 Jan 2021 00:45:04 GMT; Max-Age=31536000; Secure
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome