loverse.jp Loverse.jp

   
LOVERSE(ラヴァース)

Domain Summary

What percent of global Internet users visit Loverse.jp?

5.06E-5% of global Internet users visit Loverse.jp

How many people visit Loverse.jp each day?

• Loverse.jp receives approximately 2.5K visitors and 38,345 page impressions per day.

Which countries does Loverse.jp receive most of its visitors from?

• Loverse.jp is mostly visited by people located in Japan.

How much Loverse.jp can earn?

• Loverse.jp should earn about $13.80/day from advertising revenue.

What is Loverse.jp estimated value?

• Estimated value of Loverse.jp is $14,942.26.

What IP addresses does Loverse.jp resolve to?

• Loverse.jp resolves to the IP addresses 163.44.185.182.

Where are Loverse.jp servers located in?

• Loverse.jp has servers located in Japan.

loverse.jp Profile

Title:LOVERSE(ラヴァース) Description:「あの恋」を超える恋をしよう!誰でも今すぐはじめられます。なぜって、恋のお相手はAIですから。
Tags:

What technologies does loverse.jp use?

These are the technologies used at loverse.jp. loverse.jp has a total of 13 technologies installed in 12 different categories.

loverse.jp Traffic Analysis

This website is viewed by an estimated 2.5K visitors daily, generating a total of 38.3K pageviews. This equates to about 75.6K monthly visitors. Loverse.jp traffic has increased by 798.6% compared to last month.
Daily Visitors2.5K
31.86%
Monthly Visits75.6K
798.6%
Pages per Visit15.37
918%
Visit duration12:08
5250%
Bounce Rate29.34%
42.48%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
2,495
Monthly Visits:
75,599
Pages per Visit:
15.37
Daily Pageviews:
38,345
Avg. visit duration:
12:08
Bounce rate:
29.34%
Global Reach:
5.06E-5%
Monthly Visits (SEMrush):
46,152
Monthly Unique Visitors (SEMrush):
1,670
Monthly Visits (SimilarWeb):
75,603
HypeRank:
n/a
SEMrush Rank:
16,432,342
SimilarWeb Rank:
264,100
*All traffic values are estimates only.

Traffic sources

Direct:
100.00%
Referral:
0%
Search:
0%
Social:
0%
Paid:
0%

Desktop vs Mobile

Desktop:
0.87%
Mobile:
99.13%

Total Visits Last 3 Months

306.2K
DEC
8.4K
JAN
75.6K
FEB

Visitors by country

Country
Users%
 
Japan 100.00%
Last update was 132 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with loverse.jp 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:
2,300

 

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:
  loverse.jp
Rank:
(Rank based on keywords, cost and organic traffic)
  16,432,342
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  9
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
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 $13.8 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $414 and annual gross revenue of approximately $5K. Based on these figures, the site's net worth is estimated at around $14.9K.

How much would loverse.jp make?

Daily Revenue:
$13.80
Monthly Revenue:
$414.00
Yearly Revenue:
$5,037.00
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Japan 38,345$13.80

Loss of money due to Adblock?

Daily Revenue Loss:
$0.41
Monthly Revenue Loss:
$12.42
Yearly Revenue Loss:
$151.16
Daily Pageviews Blocked:
1,150
Monthly Pageviews Blocked:
34,511
Yearly Pageviews Blocked:
419,878

Daily revenue loss by country

 
CountryBlockedLost Money
 
Japan 1,150$0.41

How much is loverse.jp worth?

Website Value:
$14.9K

Ad Experience Report

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

Mobile summary

Root domain:
loverse.jp
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:
loverse.jp
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:
loverse.jp
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 loverse.jp hosted?

Loverse.jp may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
163.44.185.182
ASN:
AS7506 
ISP:
GMO Internet,Inc 
Server Location:

Japan, JP
 

Other sites hosted on 163.44.185.182

How fast does loverse.jp load?

The average loading time of loverse.jp is 689 ms. The Desktop speed index is 86 and mobile speed index is 70.
Average Load Time:
689 ms

Page Speed (Google PageSpeed Insights) - Desktop

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 99% 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)502ms 86% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 86% 8% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 8% 4% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 4%
First Contentful Paint (FCP)1.1s 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)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)39ms 99% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 99% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.5s 92% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 92% 3% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 3% 3% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 3%

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 100% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 100% 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)635ms 84% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 84% 13% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 13% 1% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 1%
First Contentful Paint (FCP)1.0s 95% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 95% 3% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 3% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)33ms 99% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 99% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.1s 96% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 96% 2% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 2% 0% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 0%

Lab Data

CSS Selector costs  
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Largest Contentful Paint 1.9 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  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Long critical network tree  
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
Forced reflow  
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
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
Speed Index 2.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Time to Interactive 2.0 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 70 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
Max Potential First Input Delay 90 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

Page Speed (Google PageSpeed Insights) - Mobile

70
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 99% 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)504ms 86% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 87% 9% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 9% 2% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)1.1s 93% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 89% 7% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 7% 2% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 2%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)122ms 99% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 92% 6% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 6% 0% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.4s 92% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 90% 6% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 6% 3% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 3%

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 99% 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)667ms 81% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 81% 16% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 16% 2% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)1.1s 93% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 93% 5% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 5% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)86ms 96% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 96% 1% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 1% 1% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 1%
Largest Contentful Paint (LCP)1.2s 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 Contentful Paint 2.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
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
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Total Blocking Time 100 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
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Largest Contentful Paint 6.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Time to Interactive 6.6 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
Speed Index 3.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
CSS Selector costs  
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Forced reflow  
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
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
Long critical network tree  
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests

Does loverse.jp 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 loverse.jp are reduced by 77%.
loverse.jp use br compression.
Original size: 73.09 KB
Compressed size: 16.63 KB
File reduced by: 56.46 KB (77%)

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. loverse.jp supports HTTPS.
 loverse.jp supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: loverse.jp
Organization:
Location:
Issuer: R11
Valid from: Feb 7 17:37:11 2025 GMT
Valid until: May 8 17:37:10 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R11
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 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.
 loverse.jp 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, 29 Mar 2025 22:46:03 GMT
content-type: text/html; charset=UTF-8
content-length: 17032
server: LiteSpeed
x-powered-by: PHP/8.2.28
set-cookie: PHPSESSID=970ij983qckgbl95ificncctcf; path=/; secure
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
content-encoding: br
vary: Accept-Encoding
content-security-policy: frame-ancestors 'self';
x-turbo-charged-by: LiteSpeed

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
SOA 3600
Mname dns01.muumuu-domain.com
Rname postmaster.loverse.jp
Serial Number 1702273166
Refresh 3600
Retry 1800
Expire 604800
Minimum TTL 3600
TXT v=spf1 include:_spf.lolipop.jp ~all 3600
TXT google-site-verification=IzUOtGDFkNXymxDXCNJ1LlCdG9DHXQbNR8DacNiM9VA 3600
MX mx01.lolipop.jp 3600
A 163.44.185.182 3525
NS dns02.muumuu-domain.com 3600
NS dns01.muumuu-domain.com 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 November 17, 2023 and will expire on November 30, 2025 if not renewed. This website is now assigned through the registrar . The WHOIS data for this website's domain was last updated on December 22, 2024.
Domain Created:
2023-11-17
Domain Expires:
2025-11-30
Domain Updated:
2024-12-22
Domain Age:
1 years 8 months 22 days
Domain Owner:
Samansa Co., Ltd
WhoIs:
 

[ JPRS database provides information on network administration. Its use is    ]
[ restricted to network administration purposes. For further information,     ]
[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e'     ]
[ at the end of command, e.g. 'whois -h whois.jprs.jp ***/e'.                 ]
Domain Information:
[Domain Name]                   LOVERSE.JP

[Registrant]                    Samansa Co., Ltd

[Name Server]                   dns01.muumuu-domain.com
[Name Server]                   dns02.muumuu-domain.com
[Signing Key]                   

[Created on]                    2023/11/17
[Expires on]                    2025/11/30
[Status]                        Active
[Last Updated]                  2024/12/23 08:09:45 (JST)

Contact Information:
[Name]                          GMO Pepabo, Inc.
[Email]                         email
[Web Page]                      http://muumuu-domain.com/?mode=whois-policy
[Postal code]                   810-0001
[Postal Address]                Tenjin Prime 8F, 2-7-21, Tenjin
                                Chuo-ku, Fukuoka-City, Fukuoka
                                8100001,Japan
[Phone]                         092-713-7999
[Fax]                           092-713-7944