polygonhealth.app Polygonhealth.app

   
Polygon Health | Welcome to Patient Connect!

Domain Summary

What percent of global Internet users visit Polygonhealth.app?

1.3E-6% of global Internet users visit Polygonhealth.app

How many people visit Polygonhealth.app each day?

• Polygonhealth.app receives approximately 65 visitors and 129 page impressions per day.

Which countries does Polygonhealth.app receive most of its visitors from?

• Polygonhealth.app is mostly visited by people located in United States.

How much Polygonhealth.app can earn?

• Polygonhealth.app should earn about $0.63/day from advertising revenue.

What is Polygonhealth.app estimated value?

• Estimated value of Polygonhealth.app is $539.76.

What IP addresses does Polygonhealth.app resolve to?

• Polygonhealth.app resolves to the IP addresses 185.230.63.171.

Where are Polygonhealth.app servers located in?

• Polygonhealth.app has servers located in Ashburn, Virginia, 20147, United States.

polygonhealth.app Profile

Title:Polygon Health | Welcome to Patient Connect! Description:Polygon Health's Patient Connect platform helps connect you with multiple myeloma patients and resources

What technologies does polygonhealth.app use?

These are the technologies used at polygonhealth.app. polygonhealth.app has a total of 9 technologies installed in 8 different categories.

polygonhealth.app Traffic Analysis

This website is viewed by an estimated 65 visitors daily, generating a total of 129 pageviews. This equates to about 2K monthly visitors. Polygonhealth.app traffic has increased by 10.6% compared to last month.
Daily Visitors65
10.6%
Monthly Visits2K
10.6%
Pages per Visit2.00
Visit duration00:52
Bounce Rate39.92%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
65
Monthly Visits:
1,970
Pages per Visit:
2.00
Daily Pageviews:
129
Avg. visit duration:
00:52
Bounce rate:
39.92%
Global Reach:
1.3E-6%
Monthly Visits (SEMrush):
678
Monthly Unique Visitors (SEMrush):
678
Monthly Visits (SimilarWeb):
1,966
HypeRank:
n/a
SEMrush Rank:
413,846
SimilarWeb Rank:
6,729,893
*All traffic values are estimates only.

Traffic sources

Direct:
44.84%
Referral:
0%
Search:
55.16%
Social:
0%
Paid:
0%

Desktop vs Mobile

Desktop:
100.00%
Mobile:
0%

Total Visits Last 3 Months

1.3K
JAN
1.8K
FEB
2K
MAR

Visitors by country

Country
Users%
 
United States 100.00%
Last update was 56 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with polygonhealth.app in any way. Only publicly available statistics data are displayed.

Search Engine Indexes

Search engine indexes are huge databases or collections of net pages that search engines like google like google and yahoo use to retrieve applicable facts while customers carry out searches. These indexes are created through search engines like google and yahoo through crawling and indexing net pages from throughout the internet.
Google Index:
85

 

SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.
SemRushSemRush
Domain:
  polygonhealth.app
Rank:
(Rank based on keywords, cost and organic traffic)
  413,846
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  1,828
Organic Traffic:
(Number of visitors coming from top 20 search results)
  3,662
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $5,292.00

Revenue report

Google.com would generate approximately $0.6 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $18.9 and annual gross revenue of approximately $230. Based on these figures, the site's net worth is estimated at around $539.8.

How much would polygonhealth.app make?

Daily Revenue:
$0.63
Monthly Revenue:
$18.90
Yearly Revenue:
$229.95
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 129$0.62

Loss of money due to Adblock?

Daily Revenue Loss:
$0.11
Monthly Revenue Loss:
$3.36
Yearly Revenue Loss:
$40.94
Daily Pageviews Blocked:
23
Monthly Pageviews Blocked:
697
Yearly Pageviews Blocked:
8,475

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 23$0.11

How much is polygonhealth.app worth?

Website Value:
$539.8

Ad Experience Report

Summary of the ad experience rating of a website for a specific platform.

Mobile summary

Root domain:
polygonhealth.app
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Desktop summary

Root domain:
polygonhealth.app
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Abusive Experience Report

Summary of the abusive experience rating of a website.
Root domain:
polygonhealth.app
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

Where is polygonhealth.app hosted?

Polygonhealth.app may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
185.230.63.171
ASN:
AS58182 
ISP:
Wix.com Ltd. 
Server Location:
Ashburn
Virginia, VA
20147
United States, US
 

Other sites hosted on 185.230.63.171

How fast does polygonhealth.app load?

The average loading time of polygonhealth.app is 237 ms. The Desktop speed index is 96 and mobile speed index is 0.
Average Load Time:
237 ms

Page Speed (Google PageSpeed Insights) - Desktop

96
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a FAST speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Cumulative Layout Shift (CLS)0ms 91% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 91% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 6% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 6%
Time To First Byte (TTFB)552ms 82% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 82% 10% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 10% 6% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 6%
First Contentful Paint (FCP)739ms 94% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 94% 4% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 4% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)30ms 100% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 100% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.6s 89% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 89% 6% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 6% 4% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 4%

Origin Data

All pages served from this origin have an FAST speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Cumulative Layout Shift (CLS)0ms 91% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 91% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 6% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 6%
Time To First Byte (TTFB)552ms 82% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 82% 10% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 10% 6% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 6%
First Contentful Paint (FCP)739ms 94% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 94% 4% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 4% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)30ms 100% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 100% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.6s 89% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 89% 6% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 6% 4% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 4%

Lab Data

INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Time to Interactive 2.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Max Potential First Input Delay 70 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Duplicated JavaScript  
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Render blocking requests  
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
Improve image delivery  
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Legacy JavaScript  
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Largest Contentful Paint 1.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides

Does polygonhealth.app use compression?

Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on polygonhealth.app are reduced by 80%.
polygonhealth.app use br compression.
Original size: 619.41 KB
Compressed size: 121.32 KB
File reduced by: 498.09 KB (80%)

Google Safe Browsing

Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.
This site is not currently listed as suspicious

MyWot.com Reputation Ratings

MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites.
Status:
  SAFE

SSL Checker - SSL Certificate Verify

An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. polygonhealth.app supports HTTPS.
 polygonhealth.app supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: polygonhealth.app
Organization:
Location:
Issuer: R10
Valid from: Mar 22 09:06:19 2025 GMT
Valid until: Jun 20 09:06:18 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R10
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 GMT
Authority: CA:TRUE
Keysize: 2048 Bits

Verify HTTP/2 Support

HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency.
 polygonhealth.app supports HTTP/2
     
Verifying HTTP/2.0 Support. Please wait...

Http Header

HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server.
date: Fri, 02 May 2025 05:42:42 GMT
content-length: 0
location: https://www.polygonhealth.app/
x-wix-cache-control: public, max-age=86400
strict-transport-security: max-age=86400
x-wix-request-id: 1746164562.158234541208262079369
age: 0
server-timing: cache;desc=miss, varnish;desc=miss, dc;desc=virginia-pub
x-seen-by: wmgbEcS9zOENaefw7bU4YWUB9sr6xQv+MzGcyOXtFso=,jKB0KR2wTEE1MYSdxvKSbciHE4dbw+wewoJ5nvKoyjE=,m0j2EEknGIVUW/liY8BLLg0TQyIller79a4xC6tIM1+aplD64utOnGn2VMGhl2y8,2d58ifebGbosy5xc+FRaljW7ZhAVoiyo6/JMCIbLq/1c4RJsWhuwJQYReCt6/4KcsAt9udUmqWaCzTvPKq0rgg==,2UNV7KOq4oGjA5+PKsX47PWghLBqcpSK3BFeBq7nOthBgoOYGa1MpluGPPjG4/Tb,/B3VgDtICCNDWQOEWfZmMg4rLs27TOFqpHvvoJIEi8E=,/j+AjfLiOiE0Vc9NsP8sK/q+wIV0bl3vk+xiPGzmxM0j6r0AZAMucqm4C7kwBEyacv5PI8lECx50wtxrzHsaHA==
cache-control: no-cache
x-wix-request-id: 1746164562.158234541208262079369
x-content-type-options: nosniff
server: Pepyaka

HTTP/2 200 
content-type: text/html; charset=UTF-8
link: <https://static.parastorage.com/>; rel=preconnect; crossorigin;,<https://static.parastorage.com/>; rel=preconnect;,<https://static.wixstatic.com/>; rel=preconnect; crossorigin;,<https://static.wixstatic.com/>; rel=preconnect;,<https://siteassets.parastorage.com>; rel=preconnect; crossorigin;,
html-cacheable: true
etag: W/"7140ab4458f0ad680db9a443e25158ac"
content-language: en-US
strict-transport-security: max-age=86400
age: 29526
x-wix-request-id: 1746164562.262234464328232469206
set-cookie: XSRF-TOKEN=1746164562|-bmB8Hm44u2e; Path=/; Domain=www.polygonhealth.app; Secure; SameSite=None
set-cookie: ssr-caching=cache#desc=hit#varnish=hit_miss#dc#desc=fastly_virginia-pub_g; max-age=20
cache-control: private,max-age=0,must-revalidate
server: Pepyaka
x-content-type-options: nosniff
content-encoding: br
accept-ranges: bytes
date: Fri, 02 May 2025 05:42:42 GMT
x-served-by: cache-chi-klot8100137-CHI
x-cache: MISS
vary: Accept-Encoding
server-timing: cache;desc=hit, varnish;desc=hit_miss, dc;desc=fastly_virginia-pub_g
x-seen-by: yvSunuo/8ld62ehjr5B7kA==,vmPhUNXuQemvc7fjBI8NWewfbs+7qUVAqsIx00yI78k=,jKB0KR2wTEE1MYSdxvKSbciHE4dbw+wewoJ5nvKoyjE=,m0j2EEknGIVUW/liY8BLLn0tqvC/G/r4Z0m/HuWouneaplD64utOnGn2VMGhl2y8,2d58ifebGbosy5xc+FRalsdfXXO+OdjAKNJk/XlVUKb10Y1LhOUjsRCuIeFdtQe7S35TcgUpT1dD31J+Xsx53g==,2UNV7KOq4oGjA5+PKsX47NY8658Y1/RiE4fCUvLbJAsxwy5Yb789UDkEfaJNWrtQ
via: 1.1 google
glb-x-seen-by: bS8wRlGzu0Hc+WrYuHB8QIg44yfcdCMJRkBoQ1h6Vjc=
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000

DNS Lookup

DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.
Type Ip Target/Txt TTL
SOA 3600
Mname ns2.wixdns.net
Rname support.wix.com
Serial Number 2022081023
Refresh 10800
Retry 3600
Expire 1209600
Minimum TTL 3600
A 185.230.63.107 3513
A 185.230.63.186 3513
A 185.230.63.171 3513
NS ns3.wixdns.net 10713
NS ns2.wixdns.net 10713