dizhi91.github.io Dizhi91.github.io

   
Site not found · GitHub Pages

Domain Summary

What is the traffic rank for Dizhi91.github.io?

• Dizhi91.github.io ranks #3,831,589 globally on HypeStat.

What percent of global Internet users visit Dizhi91.github.io?

5.64E-5% of global Internet users visit Dizhi91.github.io

How many people visit Dizhi91.github.io each day?

• Dizhi91.github.io receives approximately 2.8K visitors and 4,606 page impressions per day.

Which countries does Dizhi91.github.io receive most of its visitors from?

• Dizhi91.github.io is mostly visited by people located in China,Hong Kong,United States.

How much Dizhi91.github.io can earn?

• Dizhi91.github.io should earn about $2.93/day from advertising revenue.

What is Dizhi91.github.io estimated value?

• Estimated value of Dizhi91.github.io is $2,599.73.

What IP addresses does Dizhi91.github.io resolve to?

• Dizhi91.github.io resolves to the IP addresses 2606:50c0:8002::153, 185.199.110.153.

Where are Dizhi91.github.io servers located in?

• Dizhi91.github.io has servers located in San Francisco, California, 94107, United States.

dizhi91.github.io Profile

Title:Site not found · GitHub Pages
Description:欢迎访问九色视频|91porny地址发布页,为您提供九色视频最新地址。
Tags:
Category:Computers Electronics and Technology / Search Engines
About: dizhi91.github.io is a website created by a software engineer from China. It is a blog with a focus on computer science, programming and web development. The blog contains articles related to various topics such as React, JavaScript, Node.js, HTML, CSS, Git, and more. It also contains tutorials and explanations of programming concepts. Additionally, dizhi91.github.io provides tools and resources for developers to help them in their projects.
*This text is generated by artificial intelligence and may not be accurate. Edit Site Info

What technologies does dizhi91.github.io use?

These are the technologies used at dizhi91.github.io. dizhi91.github.io has a total of 3 technologies installed in 3 different categories.

dizhi91.github.io Traffic Analysis

Dizhi91.github.io is ranked #3,831,589 in the world. This website is viewed by an estimated 2.8K visitors daily, generating a total of 4.6K pageviews. This equates to about 84.2K monthly visitors. Dizhi91.github.io traffic has decreased by 14.36% compared to last month.
Daily Visitors2.8K
9.23%
Monthly Visits84.2K
14.36%
Pages per Visit1.66
4.12%
Visit duration00:41
3.12%
Bounce Rate75.83%
0.18%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
2,779
Monthly Visits:
84,204
Pages per Visit:
1.66
Daily Pageviews:
4,606
Avg. visit duration:
00:41
Bounce rate:
75.83%
Global Reach:
5.64E-5%
Monthly Visits (SEMrush):
209,652,492
Monthly Unique Visitors (SEMrush):
81,038,057
Monthly Visits (SimilarWeb):
81,745
HypeRank:
3,831,589
SEMrush Rank:
730,984
SimilarWeb Rank:
670,364
*All traffic values are estimates only.

Traffic sources

Direct:
51.42%
Referral:
10.93%
Search:
29.88%
Social:
7.77%
Paid:
0%

Desktop vs Mobile

Desktop:
34.81%
Mobile:
65.19%

Total Visits Last 3 Months

221.6K
JUN
98.3K
JUL
84.2K
AUG

Visitors by country

Country
Users%
 
China 80.09%
 
Hong Kong 3.70%
 
United States 3.70%
 
Singapore 3.09%
 
Taiwan 2.75%

Where do visitors go on dizhi91.github.io?

 
Reach%Pageviews%PerUser
dizhi91.github.io
100.00%100.00%1.0
Last update was 184 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with dizhi91.github.io 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.
Bing Index:
2

Moz Data

Domain Authority (DA) is a metric developed by Moz. DA is a score that predicts the ranking potential of a website on search engine result pages (SERPs). Moz calculates Domain Authority on a logarithmic scale from 1 to 100, with higher scores indicating a greater likelihood of ranking well in search results. Moz Domain Authority of dizhi91.github.io is 3.
Domain Authority:
  3
Page Authority:
  37
MozRank:
  4

 

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:
  dizhi91.github.io
Rank:
(Rank based on keywords, cost and organic traffic)
  730,984
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  87
Organic Traffic:
(Number of visitors coming from top 20 search results)
  1,376
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00

Revenue report

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

How much would dizhi91.github.io make?

Daily Revenue:
$2.93
Monthly Revenue:
$87.90
Yearly Revenue:
$1,069.45
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 171$0.82
 
China 3,689$0.37
 
Singapore 142$0.27
 
Hong Kong 171$0.19
 
Taiwan 127$0.03

Loss of money due to Adblock?

Daily Revenue Loss:
$0.30
Monthly Revenue Loss:
$8.92
Yearly Revenue Loss:
$108.53
Daily Pageviews Blocked:
589
Monthly Pageviews Blocked:
17,668
Yearly Pageviews Blocked:
214,956

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 31$0.15
 
Singapore 41$0.08
 
China 480$0.05
 
Hong Kong 17$0.02
 
Taiwan 20$0.00

How much is dizhi91.github.io worth?

Website Value:
$2.6K

Ad Experience Report

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

Mobile summary

Root domain:
dizhi91.github.io
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:
dizhi91.github.io
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:
dizhi91.github.io
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 dizhi91.github.io hosted?

Dizhi91.github.io may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
2606:50c0:8002::153, 185.199.110.153
ASN:
AS54113 
ISP:
Fastly 
Server Location:
San Francisco
California, CA
94107
United States, US
 

Other sites hosted on 185.199.110.153

How fast does dizhi91.github.io load?

The average loading time of dizhi91.github.io is 52 ms. The Desktop speed index is 97 and mobile speed index is 81.
Average Load Time:
52 ms

Page Speed (Google PageSpeed Insights) - Desktop

97
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.5s 58% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 58% 23% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 23% 18% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 18%
First Input Delay (FID)1ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 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.5s 58% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 58% 23% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 23% 18% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 18%
First Input Delay (FID)1ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

Has a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
First Contentful Paint 0.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Speed Index 1.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Largest Contentful Paint 1.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
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 about performance budgets
Time to Interactive 0.9 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
Max Potential First Input Delay 120 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
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
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
Total Blocking Time 80 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
First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric

Page Speed (Google PageSpeed Insights) - Mobile

81
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW 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)3.4s 58% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 48% 23% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 23% 28% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 28%
First Input Delay (FID)12ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 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 SLOW 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)3.4s 48% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 48% 23% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 23% 28% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 28%
First Input Delay (FID)12ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Time to Interactive 3.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
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 about the Total Blocking Time metric
Has a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
First Contentful Paint 1.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Max Potential First Input Delay 220 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
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 about performance budgets
Largest Contentful Paint 4.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
First Meaningful Paint 2.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Speed Index 2.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
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

Does dizhi91.github.io 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 dizhi91.github.io are reduced by 43%.
dizhi91.github.io use gzip compression.
Original size: 8.9 KB
Compressed size: 5.02 KB
File reduced by: 3.88 KB (43%)

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. dizhi91.github.io supports HTTPS.
 dizhi91.github.io supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: *.github.io
Organization: "GitHub, Inc."
Location: San Francisco, California, US
Issuer: DigiCert TLS RSA SHA256 2020 CA1
Valid from: Feb 21 00:00:00 2023 GMT
Valid until: Mar 20 23:59:59 2024 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: DigiCert TLS RSA SHA256 2020 CA1
Organization: DigiCert Inc
Location: US
Issuer: DigiCert Global Root CA
Valid from: Apr 14 00:00:00 2021 GMT
Valid until: Apr 13 23:59:59 2031 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.
 dizhi91.github.io 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.
server: GitHub.com
content-type: text/html; charset=utf-8
permissions-policy: interest-cohort=()
etag: W/"65020b3f-239b"
content-security-policy: default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'
content-encoding: gzip
x-github-request-id: 8940:2C1E:197602:23E265:6512E205
accept-ranges: bytes
date: Tue, 26 Sep 2023 13:52:05 GMT
via: 1.1 varnish
age: 0
x-served-by: cache-chi-klot8100100-CHI
x-cache: MISS
x-cache-hits: 0
x-timer: S1695736325.281717,VS0,VE31
vary: Accept-Encoding
x-fastly-request-id: d585a6f3794f21a0d1d75e73466a8a9372138653
content-length: 5142

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
AAAA 2606:50c0:8001::153 3571
AAAA 2606:50c0:8000::153 3571
AAAA 2606:50c0:8003::153 3571
AAAA 2606:50c0:8002::153 3571
A 185.199.109.153 3571
A 185.199.108.153 3571
A 185.199.111.153 3571
A 185.199.110.153 3571

Whois Lookup

Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information.
WhoIs:
 

Malformed request.
>>> Last update of WHOIS database: 2023-09-26T13:52:34Z