Your Website Score is

Similar Ranking

59
KASKUS - BERBAGI HOBI, BERKOMUNITAS
kaskus.co.id
59
GET 2020 HEALTH COVERAGE. HEALTH INSURANCE MARKETPLACE| HEALTHCARE.GOV
healthcare.gov
59
EPIK - CHEAP DOMAIN NAMES, HOSTING, DOMAINING & MORE!
epik.com
59
WARGAMING.NET GAMES — THE FULL LIST OF GAMES AVAILABLE FOR PLAYERS ON THE OFFICIAL WEBSITE
wargaming.net
59
THE HISTORY PRESS | THE DESTINATION FOR HISTORY
thehistorypress.co.uk
59
STACKPATH
rafmuseum.org.uk
59
THE DRIVE - AUTOMOTIVE NEWS, CAR REVIEWS AND CAR TECH
thedrive.com

Latest Sites

19
SUDAR BLOGGER - PERSONAL BLOG
sudarblogger.web.id
19
JASA WEB DEVELOPMENT | JASA PEMBUATAN WEBSITE | LAYANAN HOSTING
jasawebdevelopment.com
14
DEON ONLINE
deononline.com
19
ALLSEOPART - SEO CHECKER AND ALL IN ONE REVIEW WEBSITE TOOLS
allseopart.com
14
????SEO CHECKER WEBSITE | WEBSITE REVIEWS | SEO TOOL AUDIT - OYWSEO
oywseo.com
39
WORDPRESS, WEBSITE, AND RESELLER WEB HOSTING, VPS | 20I
20i.com

Top Technologies

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

59 healthcare.gov Last Updated: 4 months

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

Desktop

Mobile

Performance Desktop Score 72%
Best Practices Desktop Score 79%
SEO Desktop Score 82%
Progressive Web App Desktop Score 30%
Performance Mobile Score 24%
Best Practices Mobile Score 79%
SEO Mobile Score 82%
Progressive Web App Mobile Score 32%
Page Authority Authority 66%
Domain Authority Domain Authority 80%
Moz Rank 6.6/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 70 Characters
GET 2020 HEALTH COVERAGE. HEALTH INSURANCE MARKETPLACE| HEALTHCARE.GOV
Meta Description 137 Characters
Official site of Affordable Care Act. Enroll now for 2020 coverage. See health coverage choices, ways to save today, how law affects you.
Effective URL 26 Characters
https://www.healthcare.gov
Excerpt Page content
Get 2020 health coverage. Health Insurance Marketplace| HealthCare.gov Skip navigation Menu ...
Keywords Cloud Density
coverage21 health18 insurance13 plans12 marketplace10 help10 email10 information10 enrollment10 change9
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
coverage 21
health 18
insurance 13
plans 12
marketplace 10
help 10
email 10
information 10
enrollment 10
change 9
Google Preview Your look like this in google search result
GET 2020 HEALTH COVERAGE. HEALTH INSURANCE MARKETPLACE| HEAL
https://www.healthcare.gov
Official site of Affordable Care Act. Enroll now for 2020 coverage. See health coverage choices, ways to save today, how law affects you.
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 / 621 months 14 days
Page Size Code & Text Ratio
Document Size: ~57.8 KB
Code Size: ~41.23 KB
Text Size: ~16.57 KB Ratio: 28.67%

Social Data

Delicious Total: 0
Facebook Total: 3,003,275
Google Total: 0
Linkedin Total: 0
Pinterest Total: 3
Stumbleupon Total: 0
Tumblr Total: 0
Vk Total: 0

Estimation Traffic and Earnings

32,186
Unique Visits
Daily
59,544
Pages Views
Daily
$38
Income
Daily
901,208
Unique Visits
Monthly
1,697,004
Pages Views
Monthly
$950
Income
Monthly
10,428,264
Unique Visits
Yearly
20,006,784
Pages Views
Yearly
$10,032
Income
Yearly

Technologies

PWA - Manifest

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

Desktop

Desktop Screenshot
Estimated Input Latency 10 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
Links do not have descriptive text 3 links found
Descriptive link text helps search engines understand your content
Max Potential First Input Delay 160 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Initial server response time was short Root document took 390 ms
Keep the server response time for the main document short because all other requests depend on it
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
Remove unused CSS Potential savings of 48 KiB
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 1,324 KiB
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
Eliminate render-blocking resources Potential savings of 660 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid an excessive DOM size 990 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 8 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Total Blocking Time 120 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Remove unused JavaScript Potential savings of 109 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoid serving legacy JavaScript to modern browsers Potential savings of 6 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Avoid long main-thread tasks 3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Cumulative Layout Shift 0.002
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid chaining critical requests 17 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
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Efficiently encode images Potential savings of 273 KiB
Optimized images load faster and consume less cellular data
Keep request counts low and transfer sizes small 72 requests • 2,276 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First Meaningful Paint 1.4 s
First Meaningful Paint measures when the primary content of a page is visible
Preload key requests Potential savings of 390 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Largest Contentful Paint 3.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Time to Interactive 2.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Minimize third-party usage Third-party code blocked the main thread for 60 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
First CPU Idle 2.4 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/).
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
Avoids enormous network payloads Total size was 2,276 KiB
Large network payloads cost users real money and are highly correlated with long load times
Properly size images Potential savings of 310 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Serve static assets with an efficient cache policy 44 resources found
A long cache lifetime can speed up repeat visits to your page
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 10.2 s
A fast page load over a cellular network ensures a good mobile user experience
Minimizes main-thread work 1.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
User Timing marks and measures 1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
robots.txt is not valid 4 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Speed Index 1.9 s
Speed Index shows how quickly the contents of a page are visibly populated
JavaScript execution time 0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Mobile

Mobile Screenshot
Avoids enormous network payloads Total size was 1,409 KiB
Large network payloads cost users real money and are highly correlated with long load times
Links do not have descriptive text 3 links found
Descriptive link text helps search engines understand your content
Time to Interactive 10.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Serve static assets with an efficient cache policy 43 resources found
A long cache lifetime can speed up repeat visits to your page
Minimize main-thread work 6.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First CPU Idle 10.1 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/).
Avoid an excessive DOM size 990 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)
Tap targets are not sized appropriately 70% 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
Preload key requests Potential savings of 3,090 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Avoid serving legacy JavaScript to modern browsers Potential savings of 6 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
First Meaningful Paint 5.3 s
First Meaningful Paint measures when the primary content of a page is visible
Eliminate render-blocking resources Potential savings of 3,120 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Document uses legible font sizes 63.48% 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
Serve images in next-gen formats Potential savings of 437 KiB
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
Remove unused CSS Potential savings of 48 KiB
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
Avoid chaining critical requests 17 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
Efficiently encode images Potential savings of 273 KiB
Optimized images load faster and consume less cellular data
Reduce JavaScript execution time 3.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
robots.txt is not valid 4 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
First Contentful Paint (3G) 8400 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
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
Defer offscreen images Potential savings of 359 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
User Timing marks and measures 1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Total Blocking Time 1,470 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Remove unused JavaScript Potential savings of 110 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Page load is not fast enough on mobile networks Interactive at 10.3 s
A fast page load over a cellular network ensures a good mobile user experience
Largest Contentful Paint 7.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Minify JavaScript Potential savings of 8 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Speed Index 6.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Initial server response time was short Root document took 490 ms
Keep the server response time for the main document short because all other requests depend on it
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
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
Estimated Input Latency 180 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
Keep request counts low and transfer sizes small 71 requests • 1,409 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Contentful Paint 4.3 s
First Contentful Paint marks the time at which the first text or image is painted
Cumulative Layout Shift 0.013
Cumulative Layout Shift measures the movement of visible elements within the viewport
Max Potential First Input Delay 630 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Reduce the impact of third-party code Third-party code blocked the main thread for 1,310 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

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Warning! Your title is not optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

6,674

Global Rank

1,264

United States
Traffic
Search

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200 
content-type: text/html
set-cookie: optimizelyEndUserId=4ca93817543e0000911a615f250300006a6c0000; expires=Thu, 15-Sep-2022 19:48:33 GMT; path=/; domain=.healthcare.gov; secure
set-cookie: _abck=6AE13CE48C80F0D1CA9C7EE1A77F2653~-1~YAAQTKk4F3ovEYF0AQAAjclPkwTGmBriEl2q0wwbODptDCqEQczGHcFnKWzAcZLDl6RhAJL+4e2Ot0T0tHBkPy9YlUC7sNK5zNGZN/UUgYwmFREmQ9GxRBzBNC7WDHkaPT4G6Fa/bAzQriEseZoi13bgJx/SAhpvUlXeKWqI1lMg2/r1aYSvEbZ0YpGm3MvkfOK4o7xwMwpbWBHSZkQjX4xGjFjx2xXGVjj6XvQIiFnoHGRkMdWnW8x13VF842LU8cbbsddsm6rqSPMxhNWARGIgQW1PIeEUcB5tC4x+5+CwAMBRnk4ck0+t9yrASQ==~-1~-1~-1; Domain=.healthcare.gov; Path=/; Expires=Wed, 15 Sep 2021 19:48:33 GMT; Max-Age=31536000; Secure
set-cookie: bm_sz=418E68F8FFE2FA096FD9FDB5680A6407~YAAQTKk4F3kvEYF0AQAAjclPkwlvDRFFGfKUWm0U+A+gubyxxW1Fwc8DTLS3mlj/n20e3YfFwDWGfaNnRFn64+VTUhZyJ+A7yD4w5gYiZLjMlni1aQ0TQxT3tq0vl/KCVbIPdOy6FUVsVGyqsEU/SLNdXvhhaIKWNXEVpQ1FMGXBugt702YeFgJMJ3eRbKP9UwKqtw==; Domain=.healthcare.gov; Path=/; Expires=Tue, 15 Sep 2020 23:48:33 GMT; Max-Age=14400; HttpOnly
set-cookie: akavpau_vp1=1600199613~id=e7fe49a63b1b3a288ca667678ee6ac06; Path=/; Secure; SameSite=None
set-cookie: _ga=GA1.2.583949880.1600199313; expires=Thu, 15-Sep-2022 19:48:33 GMT; path=/; domain=.healthcare.gov; secure
etag: "8c1b6916778f08b97cfdc6f4fcb48d7b:1598289246.911478"
x-frame-options: SAMEORIGIN
x-permitted-cross-domain-policies: master-only
x-xss-protection: 1; mode=block
strict-transport-security: max-age=31536000 ; preload
vary: Accept-Encoding
content-encoding: gzip
cache-control: max-age=60867
date: Tue, 15 Sep 2020 19:48:33 GMT
content-length: 11193
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments