near.org Near.org - Explorer.near.org

   
NEAR Explorer | Dashboard

Domain Summary

What is the traffic rank for Explorer.near.org?

• Explorer.near.org ranks #10,836 globally on HypeStat.

What percent of global Internet users visit Explorer.near.org?

• 0.00723% of global Internet users visit Explorer.near.org

How many people visit Explorer.near.org each day?

• Explorer.near.org receives approximately 356.4K visitors and 1,140,588 page impressions per day.

Which countries does Explorer.near.org receive most of its visitors from?

• Explorer.near.org is mostly visited by people located in India,United States,Viet Nam.

How much Explorer.near.org can earn?

• Explorer.near.org should earn about $2,203.42/day from advertising revenue.

What is Explorer.near.org estimated value?

• Estimated value of Explorer.near.org is $1,898,027.99.

What IP addresses does Explorer.near.org resolve to?

• Explorer.near.org resolves to the IP addresses 216.24.57.3.

Where are Explorer.near.org servers located in?

• Explorer.near.org has servers located in United States.

explorer.near.org Profile

Title:NEAR Explorer | Dashboard
Edit Site Info

What technologies does explorer.near.org use?

These are the technologies used at explorer.near.org. explorer.near.org has a total of 6 technologies installed in 7 different categories.
CDN
CloudFlare CloudFlare
Analytics
Google Analytics Google Analytics
Web Frameworks
Next.js Next.js
Web Servers
Next.js Next.js
JavaScript Frameworks
React React
Miscellaneous
webpack webpack
Programming Languages
Node.js Node.js

explorer.near.org Traffic Analysis

Explorer.near.org is ranked #10,836 in the world. This website is viewed by an estimated 356.4K visitors daily, generating a total of 1.1M pageviews. This equates to about 10.8M monthly visitors.
Daily Visitors356.4K
Monthly Visits10.8M
Pages per Visit3.20
Visit duration n/a
Bounce Rate n/a
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
356,434
Monthly Visits:
10,799,950
Pages per Visit:
3.20
Daily Pageviews:
1,140,588
Avg. visit duration:
n/a
Bounce rate:
n/a
Global Reach:
0.00723%
HypeRank:
10,836
SEMrush Rank:
111,637
*All traffic values are estimates only.

Visitors by country

Country
Users%
 
India 22.9%
 
United States 17.0%
 
Viet Nam 9.3%
 
Mexico 7.8%
 
Argentina 6.8%

Where do visitors go on explorer.near.org?

 
Reach%Pageviews%PerUser
near.org
68.37%43.11%1.5
wallet.near.org
34.33%45.17%3.2
mainnet.near.org
3.24%2.30%1.7
explorer.near.org
2.73%2.93%2.6
testnet.near.org
2.38%3.38%3.4
Last update was 852 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with near.org 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:
986
Bing Index:
1

  ▼

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:
  explorer.near.org
Rank:
(Rank based on keywords, cost and organic traffic)
  111,637
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  1,788
Organic Traffic:
(Number of visitors coming from top 20 search results)
  20,411
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $16,044.00
Full SEMrush Report >>

Revenue report ▼

Google.com would generate approximately $2.2K per day if the source of income were advertisements, which equates to an estimated monthly revenue of $66.1K and annual gross revenue of approximately $804.2K. Based on these figures, the site's net worth is estimated at around $1.9M.

How much would explorer.near.org make?

Daily Revenue:
$2,203.42
Monthly Revenue:
$66,102.60
Yearly Revenue:
$804,248.30
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Singapore 57,029$107.22
 
Viet Nam 148,276$69.69
 
India 182,494$69.35
 
Egypt 11,406$1.60
 
Indonesia 0$0.00

Loss of money due to Adblock?

Daily Revenue Loss:
$308.62
Monthly Revenue Loss:
$9,258.47
Yearly Revenue Loss:
$112,644.74
Daily Pageviews Blocked:
146,451
Monthly Pageviews Blocked:
4,393,545
Yearly Pageviews Blocked:
53,454,797

Daily revenue loss by country

 
CountryBlockedLost Money
 
Singapore 16,539$31.09
 
India 51,098$19.42
 
Viet Nam 5,931$2.79
 
Egypt 570$0.08
 
Indonesia 0$0.00

How much is explorer.near.org worth?

Website Value:
$1.9M

Ad Experience Report ▼

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

Mobile summary

Root domain:
near.org
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:
near.org
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:
near.org
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 explorer.near.org hosted? ▼

Explorer.near.org may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
216.24.57.3
ASN:
AS397273 
ISP:
Render  
Server Location:

United States, US
 

Other sites hosted on 216.24.57.3

How fast does explorer.near.org load? ▼

The average loading time of explorer.near.org is 1438 ms. The Desktop speed index is 87 and mobile speed index is 61.
Average Load Time:
1438 ms

Page Speed (Google PageSpeed Insights) - Desktop

87
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE 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.

First Contentful Paint (FCP)2.0s 42% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 42% 46% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 46% 11% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 11%
First Input Delay (FID)4ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 1% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an AVERAGE 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.

First Contentful Paint (FCP)2.0s 42% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 42% 46% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 46% 11% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 11%
First Input Delay (FID)4ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 1% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

Time to Interactive 1.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
First Contentful Paint 1.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
Avoid non-composited animations  
Animations which are not composited can be janky and increase CLS. Learn more
Timing budget  
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more
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. Learn more
Max Potential First Input Delay 50 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
Largest Contentful Paint 1.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
First CPU Idle 1.3 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. . Learn more
First Meaningful Paint 1.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more

Page Speed (Google PageSpeed Insights) - Mobile

61
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE 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.

First Contentful Paint (FCP)2.2s 42% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 36% 53% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 53% 10% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 10%
First Input Delay (FID)33ms 87% of loads for this page have a fast (<100ms) First Input Delay (FID) 87% 12% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 12% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an AVERAGE 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.

First Contentful Paint (FCP)2.2s 36% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 36% 53% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 53% 10% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 10%
First Input Delay (FID)33ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 87% 12% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 12% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

First Meaningful Paint 3.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
First Contentful Paint 3.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
First Contentful Paint (3G) 7035 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
Estimated Input Latency 20 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. Learn more
Total Blocking Time 280 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more
First CPU Idle 5.9 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. . Learn more
Speed Index 3.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Max Potential First Input Delay 370 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
Avoid non-composited animations  
Animations which are not composited can be janky and increase CLS. Learn more
Time to Interactive 7.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Timing budget  
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more
Largest Contentful Paint 5.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More

Does explorer.near.org 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 explorer.near.org are reduced by 82%.
explorer.near.org use gzip compression.
Original size: 43.27 KB
Compressed size: 7.53 KB
File reduced by: 35.73 KB (82%)

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

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. explorer.near.org supports HTTPS.
 explorer.near.org supports HTTPS
     
Verifying SSL Support. Please wait...

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.
 explorer.near.org 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: Sat, 25 Dec 2021 03:16:10 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 61
Connection: keep-alive
Location: https://explorer.near.org/
CF-Cache-Status: DYNAMIC
Server: cloudflare
CF-RAY: 6c2ee8ba58432c1d-ORD
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400, h3-28=":443"; ma=86400, h3-27=":443"; ma=86400

HTTP/2 200 
date: Sat, 25 Dec 2021 03:16:10 GMT
content-type: text/html; charset=utf-8
cache-control: private, no-cache, no-store, max-age=0, must-revalidate
content-encoding: gzip
etag: "ad12-FWdODSWE6c3q3BB1s/3BjlKirv4"
vary: Accept-Encoding
x-powered-by: Next.js
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 6c2ee8bb7faa8137-ORD
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400, h3-28=":443"; ma=86400, h3-27=":443"; ma=86400

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
CNAME near-explorer-frontend-with-indexer.onrender.com 3559