meetme.com Meetme.com

   
MeetMe - Chat and Meet New People

Domain Summary

What is the traffic rank for Meetme.com?

• Meetme.com ranks #12,317 globally on HypeStat.

What percent of global Internet users visit Meetme.com?

0.0030899% of global Internet users visit Meetme.com

How many people visit Meetme.com each day?

• Meetme.com receives approximately 152.3K visitors and 2,102,163 page impressions per day.

Which countries does Meetme.com receive most of its visitors from?

• Meetme.com is mostly visited by people located in United States,Brazil,United Kingdom.

How much Meetme.com can earn?

• Meetme.com should earn about $8,895.84/day from advertising revenue.

What is Meetme.com estimated value?

• Estimated value of Meetme.com is $11,136,960.20.

What IP addresses does Meetme.com resolve to?

• Meetme.com resolves to the IP addresses 204.145.125.82.

Where are Meetme.com servers located in?

• Meetme.com has servers located in Franklinville, New Jersey, 08322, United States.

meetme.com Profile

Title:MeetMe - Chat and Meet New People
Description:MeetMe helps you find new people nearby who share your interests and want to chat now! It’s fun, friendly, and free! Join 100+ MILLION PEOPLE chatting and making new friends. It’s for all ages, all nationalities, all backgrounds — EVERYONE! So what are you waiting for? Join the best site for finding new friends to chat with!
Tags:
Category:Community and Society / Dating and Relationships
About: Meet new people and play fun games! Edit Site Info

What technologies does meetme.com use?

These are the technologies used at meetme.com. meetme.com has a total of 3 technologies installed in 3 different categories.

meetme.com Traffic Analysis

Meetme.com is ranked #12,317 in the world. This website is viewed by an estimated 152.3K visitors daily, generating a total of 2.1M pageviews. This equates to about 4.6M monthly visitors. Meetme.com traffic has increased by 21.52% compared to last month.
Daily Visitors152.3K
4.86%
Monthly Visits4.6M
21.52%
Pages per Visit13.80
25.51%
Visit duration08:18
0.1%
Bounce Rate32.37%
2.83%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
152,331
Monthly Visits:
4,615,629
Pages per Visit:
13.80
Daily Pageviews:
2,102,163
Avg. visit duration:
08:18
Bounce rate:
32.37%
Global Reach:
0.0030899%
Monthly Visits (SEMrush):
16,742,188
Monthly Unique Visitors (SEMrush):
4,152,954
Monthly Visits (SimilarWeb):
4,616,080
HypeRank:
12,317
SEMrush Rank:
17,680
SimilarWeb Rank:
7,822
*All traffic values are estimates only.

Traffic sources

Direct:
95.02%
Referral:
0.11%
Search:
4.85%
Social:
0.03%
Paid:
0%

Desktop vs Mobile

Desktop:
18.95%
Mobile:
81.05%

Total Visits Last 3 Months

4.5M
MAY
3.8M
JUN
4.6M
JUL

Visitors by country

Country
Users%
 
United States 61.99%
 
Brazil 10.17%
 
United Kingdom 6.56%
 
Australia 2.20%
 
Canada 2.14%

Where do visitors go on meetme.com?

 
Reach%Pageviews%PerUser
meetme.com
63.61%25.73%1.6
beta.meetme.com
53.98%71.51%5.4
help.meetme.com
1.32%0.53%2
gateway.meetme.com
1.31%1.38%4
OTHER
0%0.86%0
Last update was 238 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with meetme.com 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:
984,000
Bing Index:
38,200

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 meetme.com is 64.
Domain Authority:
  64
Page Authority:
  49
MozRank:
  5

 

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:
  meetme.com
Rank:
(Rank based on keywords, cost and organic traffic)
  17,680
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  16,058
Organic Traffic:
(Number of visitors coming from top 20 search results)
  150,495
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $154,949.00

Revenue report

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

How much would meetme.com make?

Daily Revenue:
$8,895.84
Monthly Revenue:
$266,875.20
Yearly Revenue:
$3,246,981.60
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 1,303,091$6,293.93
 
United Kingdom 137,926$369.64
 
Brazil 213,719$284.25
 
Canada 45,051$272.11
 
Australia 46,246$222.91

Loss of money due to Adblock?

Daily Revenue Loss:
$1,321.71
Monthly Revenue Loss:
$39,651.41
Yearly Revenue Loss:
$482,425.49
Daily Pageviews Blocked:
289,960
Monthly Pageviews Blocked:
8,698,794
Yearly Pageviews Blocked:
105,835,322

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 234,556$1,132.91
 
Canada 11,263$68.03
 
United Kingdom 22,068$59.14
 
Australia 9,249$44.58
 
Brazil 12,823$17.05

How much is meetme.com worth?

Website Value:
$11.1M

Ad Experience Report

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

Mobile summary

Root domain:
meetme.com
Last Change Time:
(The last time that the site changed status.)
2018-03-06 16:06:24
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.)
Passing

Desktop summary

Root domain:
meetme.com
Last Change Time:
(The last time that the site changed status.)
2018-03-06 16:06:24
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.)
Passing

Abusive Experience Report

Summary of the abusive experience rating of a website.
Root domain:
meetme.com
Last Change Time:
(The last time that the site changed status.)
2018-03-06 16:06:24
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.)
Passing

Where is meetme.com hosted?

Meetme.com may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
204.145.125.82
ASN:
AS46656 
ISP:
MeetMe, Inc. 
Server Location:
Franklinville
New Jersey, NJ
08322
United States, US
 

Other sites hosted on 204.145.125.82

How fast does meetme.com load?

The average loading time of meetme.com is 267 ms. The Desktop speed index is 73 and mobile speed index is 39.
Average Load Time:
267 ms

Page Speed (Google PageSpeed Insights) - Desktop

73
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)2.2s 68% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 68% 16% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 16% 14% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 14%
First Input Delay (FID)3ms 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 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)2.1s 70% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 70% 16% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 16% 13% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 13%
First Input Delay (FID)3ms 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

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
Largest Contentful Paint 2.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Speed Index 2.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
First Meaningful Paint 1.6 s
First Meaningful Paint measures when the primary content of a page is visible. 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
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
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
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
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 1.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more

Page Speed (Google PageSpeed Insights) - Mobile

39
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)1.9s 68% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 73% 12% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 12% 13% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 13%
First Input Delay (FID)26ms 88% of loads for this page have a fast (<100ms) First Input Delay (FID) 88% 6% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 6% 4% of loads for this page have a slow (>300ms) First Input Delay (FID) 4%

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)1.9s 73% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 73% 12% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 12% 13% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 13%
First Input Delay (FID)26ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 88% 6% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 6% 4% of loads for this page have a slow (>300ms) First Input Delay (FID) 4%

Lab Data

Largest Contentful Paint 12.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Max Potential First Input Delay 170 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 Contentful Paint (3G) 8005 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more
Total Blocking Time 410 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 4.1 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
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
First Meaningful Paint 7.6 s
First Meaningful Paint measures when the primary content of a page is visible. 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
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
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
Time to Interactive 13.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Speed Index 10.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more

Does meetme.com 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 meetme.com are reduced by 67%.
meetme.com use gzip compression.
Original size: 5.47 KB
Compressed size: 1.78 KB
File reduced by: 3.69 KB (67%)

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. meetme.com has 86 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  86
Safety Confidence:
  34
Child Safety Reputations:
  72
Child Safety Confidence:
  29

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. meetme.com supports HTTPS.
 meetme.com supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: *.meetme.com
Organization: "The Meet Group, Inc"
Location: Pennsylvania, US
Issuer: Sectigo RSA Organization Validation Secure Server CA
Valid from: Jun 23 00:00:00 2023 GMT
Valid until: Jun 22 23:59:59 2024 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: Sectigo RSA Organization Validation Secure Server CA
Organization: Sectigo Limited
Location: Salford, Greater Manchester, GB
Issuer: USERTrust RSA Certification Authority
Valid from: Nov 2 00:00:00 2018 GMT
Valid until: Dec 31 23:59:59 2030 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: USERTrust RSA Certification Authority
Organization: The USERTRUST Network
Location: Jersey City, New Jersey, US
Issuer: AAA Certificate Services
Valid from: Mar 12 00:00:00 2019 GMT
Valid until: Dec 31 23:59:59 2028 GMT
Authority: CA:TRUE
Keysize: 4096 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.
 meetme.com does not support HTTP/2
     
Verifying HTTP/2.0 Support. Please wait...

Site Categories

Website categories are used to classify websites based on their content or purpose. These categories provide a way to organize and filter websites, allowing users to find relevant information or ensure compliance with specific regulations or policies.
Video Conferencing/Bridges

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: Thu, 31 Aug 2023 05:39:31 GMT
Server: Apache
Location: http://www.meetme.com/
Content-Length: 230
Content-Type: text/html; charset=iso-8859-1
Vary: Host,User-Agent,Origin
Access-Control-Allow-Credentials: true
Access-Control-Allow-Methods: POST, GET, OPTIONS, DELETE
Access-Control-Allow-Headers: x-device,x-supportedfeatures,xsrf

HTTP/1.1 302 Found
Date: Thu, 31 Aug 2023 05:39:31 GMT
Server: Apache
Location: https://www.meetme.com/
Content-Length: 207
Content-Type: text/html; charset=iso-8859-1
Vary: Host,User-Agent,Origin
Access-Control-Allow-Credentials: true
Access-Control-Allow-Methods: POST, GET, OPTIONS, DELETE
Access-Control-Allow-Headers: x-device,x-supportedfeatures,xsrf

HTTP/1.1 200 OK
Date: Thu, 31 Aug 2023 05:39:31 GMT
Server: Apache
Pragma: no-cache
Cache-Control: no-store, no-cache
Vary: Host,User-Agent,Origin
Content-Encoding: gzip
Access-Control-Allow-Credentials: true
Access-Control-Allow-Methods: POST, GET, OPTIONS, DELETE
Access-Control-Allow-Headers: x-device,x-supportedfeatures,xsrf
Content-Type: text/html; charset=UTF-8;
Set-Cookie: PHPSESSID=63bd356780e23046a1c8e12707cd07db; path=/; domain=.meetme.com; httponly
Set-Cookie: mybLocale=en-US; expires=Fri, 30-Aug-2024 05:39:31 GMT; Max-Age=31536000; path=/; domain=.meetme.com
Access-Control-Allow-Headers: x-device,x-supportedfeatures,xsrf
Transfer-Encoding: chunked

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
TXT google-site-verification=_Kln2-mS_IecJkIG8lnw6HfMCvEywgFyVdVv6OywRSU 30
TXT stripe-verification=f8e3e0c26b8b7b5b1b7023b394c6d84ca3ada1f26916df703439ea9a977f66ef 30
TXT v=spf1 include:_spf.google.com include:spf.zoho.com include:transmail.net ~all 30
MX alt1.aspmx.l.google.com 86400
MX alt3.aspmx.l.google.com 86400
MX aspmx.l.google.com 86400
MX alt2.aspmx.l.google.com 86400
MX alt4.aspmx.l.google.com 86400
SOA 900
Mname ns-1757.awsdns-27.co.uk
Rname awsdns-hostmaster.amazon.com
Serial Number 1
Refresh 7200
Retry 900
Expire 1209600
Minimum TTL 86400
A 204.145.125.82 298
NS ns-278.awsdns-34.com 3600
NS ns-1084.awsdns-07.org 3600
NS ns-982.awsdns-58.net 3600
NS ns-1757.awsdns-27.co.uk 3600

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. Domain registration for this website began on September 5, 1995 and will expire on September 4, 2023 if not renewed. This website is now assigned through the registrar MarkMonitor Inc.. The WHOIS data for this website's domain was last updated on August 3, 2022.
Domain Created:
1995-09-05
Domain Expires:
2023-09-04
Domain Updated:
2022-08-03
Domain Age:
28 years 7 months 21 days
Domain Registrar:
MarkMonitor Inc.
WhoIs:
 

Domain Name: meetme.com
Registry Domain ID: 628081_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2022-08-03T09:25:30+0000
Creation Date: 1995-09-05T04:00:00+0000
Registrar Registration Expiration Date: 2023-09-04T00:00:00+0000
Registrar: MarkMonitor, Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.2086851750
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Registrant Organization: MeetMe
Registrant State/Province: PA
Registrant Country: US
Registrant Email: Select Request Email Form at https://domains.markmonitor.com/whois/meetme.com
Admin Organization: MeetMe
Admin State/Province: PA
Admin Country: US
Admin Email: Select Request Email Form at https://domains.markmonitor.com/whois/meetme.com
Tech Organization: MeetMe
Tech State/Province: PA
Tech Country: US
Tech Email: Select Request Email Form at https://domains.markmonitor.com/whois/meetme.com
Name Server: ns-1757.awsdns-27.co.uk
Name Server: ns-1084.awsdns-07.org
Name Server: ns-982.awsdns-58.net
Name Server: ns-278.awsdns-34.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-08-15T05:14:22+0000