github.io Github.io - Xtls.github.io

   
Project X

Domain Summary

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

• Xtls.github.io ranks #511,771 globally on HypeStat.

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

0.0001% of global Internet users visit Xtls.github.io

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

• Xtls.github.io receives approximately 4.9K visitors and 9,860 page impressions per day.

How much Xtls.github.io can earn?

• Xtls.github.io should earn about $40.23/day from advertising revenue.

What is Xtls.github.io estimated value?

• Estimated value of Xtls.github.io is $35,328.00.

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

• Xtls.github.io resolves to the IP addresses 185.199.111.153.

Where are Xtls.github.io servers located in?

• Xtls.github.io has servers located in California, United States.

xtls.github.io Profile

Title:Project X
Description:Xray 官方文档

What technologies does xtls.github.io use?

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

xtls.github.io Traffic Analysis

Xtls.github.io is ranked #511,771 in the world. This website is viewed by an estimated 4.9K visitors daily, generating a total of 9.9K pageviews. This equates to about 149.4K monthly visitors.
Daily Visitors4.9K
Monthly Visits149.4K
Pages per Visit2.00
Visit duration n/a
Bounce Rate n/a
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
4,930
Monthly Visits:
149,379
Pages per Visit:
2.00
Daily Pageviews:
9,860
Avg. visit duration:
n/a
Bounce rate:
n/a
Global Reach:
0.0001%
HypeRank:
511,771
SEMrush Rank:
1,968,949
*All traffic values are estimates only.
Last update was 1009 days ago
     
This can take up to 60 seconds. Please wait...

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

 

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

Revenue report

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

How much would xtls.github.io make?

Daily Revenue:
$40.23
Monthly Revenue:
$1,206.90
Yearly Revenue:
$14,683.95
*All earnings values are estimates only.

How much is xtls.github.io worth?

Website Value:
$35.3K

Ad Experience Report

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

Mobile summary

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

Xtls.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:
185.199.111.153
ASN:
AS54113 
ISP:
Fastly 
Server Location:
California, CA
United States, US
 

Other sites hosted on 185.199.111.153

How fast does xtls.github.io load?

The average loading time of xtls.github.io is n/a ms. The Desktop speed index is 100 and mobile speed index is 83.
Average Load Time:
n/a ms

Page Speed (Google PageSpeed Insights) - Desktop

100
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.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)2.1s 65% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 65% 24% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 24% 10% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 10%
First Input Delay (FID)2ms 100% of loads for this page have a fast (<100ms) First Input Delay (FID) 100% 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%
Interaction To Next Paint (INP)0 0% of loads for this page have a fast (<0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>0ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0ms) Largest Contentful Paint (LCP) 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.

Cumulative Layout Shift (CLS)7ms 88% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 88% 5% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 5% 5% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 5%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)2.0s 68% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 68% 21% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 21% 9% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 9%
First Input Delay (FID)2ms 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%
Interaction To Next Paint (INP)0 0% of loads for this page have a fast (<0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>0ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.3s 79% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 79% 13% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 13% 6% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 6%

Lab Data

Speed Index 0.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Minimize third-party usage  
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. Learn more
Max Potential First Input Delay 100 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
Largest Contentful Paint 0.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
Avoids `unload` event listeners  
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. 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
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
Time to Interactive 0.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
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
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 more
First Meaningful Paint 0.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
First Contentful Paint 0.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more

Page Speed (Google PageSpeed Insights) - Mobile

83
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.

Cumulative Layout Shift (CLS)0ms 0% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 86% 9% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 9% 3% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 3%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)2.1s 65% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 65% 22% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 22% 11% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 11%
First Input Delay (FID)11ms 96% of loads for this page have a fast (<100ms) First Input Delay (FID) 96% 2% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 2% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)0 0% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.3s 0% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 79% 14% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 14% 6% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 6%

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.

Cumulative Layout Shift (CLS)0ms 86% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 86% 9% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 9% 3% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 3%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)2.1s 65% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 65% 22% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 22% 11% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 11%
First Input Delay (FID)11ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 96% 2% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 2% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)0 0% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.3s 79% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 79% 14% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 14% 6% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 6%

Lab Data

Avoids `unload` event listeners  
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
Time to Interactive 3.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
First Meaningful Paint 2.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
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
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 more
Max Potential First Input Delay 340 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
Largest Contentful Paint 3.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
First Contentful Paint 2.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
Speed Index 2.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
Total Blocking Time 340 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more
First Contentful Paint (3G) 3971 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more
Minimize third-party usage  
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. 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

Does xtls.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 xtls.github.io are reduced by 74%.
xtls.github.io use gzip compression.
Original size: 16.95 KB
Compressed size: 4.27 KB
File reduced by: 12.69 KB (74%)

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. xtls.github.io supports HTTPS.
 xtls.github.io supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: www.github.com
Organization: GitHub, Inc.
Location: San Francisco, California, US
Issuer: DigiCert SHA2 High Assurance Server CA
Valid from: May 6 00:00:00 2020 GMT
Valid until: Apr 14 12:00:00 2022 GMT
Authority: Is not a CA
Keysize:
Common Name: DigiCert SHA2 High Assurance Server CA
Organization: DigiCert Inc, OU=www.digicert.com
Location: US
Issuer: DigiCert High Assurance EV Root CA
Valid from: Oct 22 12:00:00 2013 GMT
Valid until: Oct 22 12:00:00 2028 GMT
Authority: Is a CA
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.
 xtls.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
permissions-policy: interest-cohort=()
Location: https://xtls.github.io/
X-GitHub-Request-Id: C49E:6423:11E80DF:252F01F:622C843B
Content-Length: 162
Accept-Ranges: bytes
Date: Sat, 12 Mar 2022 11:30:03 GMT
Via: 1.1 varnish
Age: 0
Connection: keep-alive
X-Served-By: cache-pwk4966-PWK
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1647084604.729494,VS0,VE25
Vary: Accept-Encoding
X-Fastly-Request-ID: 8f33cf5fd7d646b3044480ac343e2e55cee589a4

HTTP/2 200 
server: GitHub.com
content-type: text/html; charset=utf-8
permissions-policy: interest-cohort=()
last-modified: Mon, 25 Oct 2021 18:41:33 GMT
access-control-allow-origin: *
strict-transport-security: max-age=31556952
etag: W/"6176fa5d-43d0"
expires: Sat, 12 Mar 2022 11:40:03 GMT
cache-control: max-age=600
content-encoding: gzip
x-proxy-cache: MISS
x-github-request-id: A2F4:4A58:14FAF81:2E360D0:622C843B
accept-ranges: bytes
date: Sat, 12 Mar 2022 11:30:03 GMT
via: 1.1 varnish
age: 0
x-served-by: cache-pwk4970-PWK
x-cache: MISS
x-cache-hits: 0
x-timer: S1647084604.880814,VS0,VE26
vary: Accept-Encoding
x-fastly-request-id: d527e23c844dc2ba3be7be301d419cfe04674087
content-length: 4370

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
A 185.199.111.153 3498
A 185.199.110.153 3498
A 185.199.109.153 3498
A 185.199.108.153 3498