r-roms.github.io R-roms.github.io

   
/r/Roms Megathread

Domain Summary

What is the traffic rank for R-roms.github.io?

• R-roms.github.io ranks #440,246 globally on HypeStat.

What percent of global Internet users visit R-roms.github.io?

0.00045% of global Internet users visit R-roms.github.io

How many people visit R-roms.github.io each day?

• R-roms.github.io receives approximately 22.2K visitors and 44,369 page impressions per day.

How much R-roms.github.io can earn?

• R-roms.github.io should earn about $181.03/day from advertising revenue.

What is R-roms.github.io estimated value?

• Estimated value of R-roms.github.io is $160,971.47.

What IP addresses does R-roms.github.io resolve to?

• R-roms.github.io resolves to the IP addresses 185.199.109.153.

Where are R-roms.github.io servers located in?

• R-roms.github.io has servers located in San Francisco, California, 94107, United States.

r-roms.github.io Profile

Title:/r/Roms Megathread
Description:None

What technologies does r-roms.github.io use?

These are the technologies used at r-roms.github.io. r-roms.github.io has a total of 8 technologies installed in 7 different categories.

r-roms.github.io Traffic Analysis

R-roms.github.io is ranked #440,246 in the world. This website is viewed by an estimated 22.2K visitors daily, generating a total of 44.4K pageviews. This equates to about 672.2K monthly visitors.
Daily Visitors22.2K
Monthly Visits672.2K
Pages per Visit2.00
Visit duration n/a
Bounce Rate n/a
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
22,185
Monthly Visits:
672,206
Pages per Visit:
2.00
Daily Pageviews:
44,369
Avg. visit duration:
n/a
Bounce rate:
n/a
Global Reach:
0.00045%
HypeRank:
440,246
SEMrush Rank:
589,326
*All traffic values are estimates only.
Last update was 502 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with r-roms.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:
  r-roms.github.io
Rank:
(Rank based on keywords, cost and organic traffic)
  589,326
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  870
Organic Traffic:
(Number of visitors coming from top 20 search results)
  2,328
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 $181 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $5.4K and annual gross revenue of approximately $66.1K. Based on these figures, the site's net worth is estimated at around $161K.

How much would r-roms.github.io make?

Daily Revenue:
$181.03
Monthly Revenue:
$5,430.90
Yearly Revenue:
$66,075.95
*All earnings values are estimates only.

How much is r-roms.github.io worth?

Website Value:
$161K

Ad Experience Report

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

Mobile summary

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

R-roms.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.109.153
ASN:
AS54113 
ISP:
Fastly 
Server Location:
San Francisco
California, CA
94107
United States, US
 

Other sites hosted on 185.199.109.153

How fast does r-roms.github.io load?

The average loading time of r-roms.github.io is 149 ms. The Desktop speed index is 99 and mobile speed index is 86.
Average Load Time:
149 ms

Page Speed (Google PageSpeed Insights) - Desktop

99
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)1ms 98% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 98% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) 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)747ms 94% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 94% 3% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 3% 2% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 2%
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%
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)871ms 96% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 96% 1% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 1% 1% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 1%

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)18ms 64% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 64% 13% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 13% 21% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 21%
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)468ms 97% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 97% 1% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 1% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
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%
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)544ms 98% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 98% 1% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 1% 0% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 0%

Lab Data

Time to Interactive 0.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Speed Index 0.8 s
Speed Index shows how quickly the contents of a page are visibly populated. 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
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted. 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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
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
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible. 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 0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more

Page Speed (Google PageSpeed Insights) - Mobile

86
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 98% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) 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)1.2s 94% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 88% 7% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 7% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
First Input Delay (FID)10ms 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%
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)1.3s 96% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 94% 3% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 3% 2% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 2%

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 84% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 84% 7% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 7% 7% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 7%
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)804ms 93% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 93% 4% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 4% 2% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 2%
First Input Delay (FID)12ms 99% 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%
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)887ms 96% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 96% 2% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 2% 0% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 0%

Lab Data

First Meaningful Paint 3.1 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
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
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 3.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
First Contentful Paint 2.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
Total Blocking Time 30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
Speed Index 2.9 s
Speed Index shows how quickly the contents of a page are visibly populated. 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 3.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. 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 Contentful Paint (3G) 6090 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more

Does r-roms.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 r-roms.github.io are reduced by 72%.
r-roms.github.io use gzip compression.
Original size: 14.5 KB
Compressed size: 4.04 KB
File reduced by: 10.46 KB (72%)

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. r-roms.github.io has 80 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  80
Safety Confidence:
  51

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. r-roms.github.io supports HTTPS.
 r-roms.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.
 r-roms.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=()
last-modified: Tue, 25 Jul 2023 23:02:56 GMT
access-control-allow-origin: *
strict-transport-security: max-age=31556952
etag: W/"64c054a0-3a02"
expires: Tue, 25 Jul 2023 23:13:34 GMT
cache-control: max-age=600
content-encoding: gzip
x-proxy-cache: HIT
x-github-request-id: 6CEA:895E:61F68D:94A6F1:64C0557E
accept-ranges: bytes
date: Thu, 27 Jul 2023 18:27:33 GMT
via: 1.1 varnish
age: 250
x-served-by: cache-chi-klot8100178-CHI
x-cache: HIT
x-cache-hits: 1
x-timer: S1690482453.083683,VS0,VE3
vary: Accept-Encoding
x-fastly-request-id: a94bb65234da8aca5685944e1e4f155718e99388
content-length: 4137

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.108.153 3599
A 185.199.110.153 3599
A 185.199.111.153 3599
A 185.199.109.153 3599