cururu.jp Cururu.jp

   
くるる | 恋愛/婚活マッチングアプリ

Domain Summary

What is the traffic rank for Cururu.jp?

• Cururu.jp ranks #697,538 globally on HypeStat.

What percent of global Internet users visit Cururu.jp?

0.00035% of global Internet users visit Cururu.jp

How many people visit Cururu.jp each day?

• Cururu.jp receives approximately 17.3K visitors and 24,157 page impressions per day.

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

• Cururu.jp is mostly visited by people located in Taiwan,Philippines,Japan.

How much Cururu.jp can earn?

• Cururu.jp should earn about $116.36/day from advertising revenue.

What is Cururu.jp estimated value?

• Estimated value of Cururu.jp is $92,168.46.

What IP addresses does Cururu.jp resolve to?

• Cururu.jp resolves to the IP addresses 13.32.145.90.

Where are Cururu.jp servers located in?

• Cururu.jp has servers located in Tokyo, Tokyo, 102-0082, United States.

cururu.jp Profile

Title:くるる | 恋愛/婚活マッチングアプリ
Tags:
About: CURURU(クルル)は、ブログとSNS両方の機能を備えた次世代コミュニティサイトです。会員登録は無料。完全招待制ではないので誰でも参加できます。 Edit Site Info

What technologies does cururu.jp use?

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

cururu.jp Traffic Analysis

Cururu.jp is ranked #697,538 in the world. This website is viewed by an estimated 17.3K visitors daily, generating a total of 24.2K pageviews. This equates to about 522.8K monthly visitors.
Daily Visitors17.3K
Monthly Visits522.8K
Pages per Visit n/a
Visit duration n/a
Bounce Rate n/a
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
17,255
Monthly Visits:
522,827
Pages per Visit:
n/a
Daily Pageviews:
24,157
Avg. visit duration:
n/a
Bounce rate:
n/a
Global Reach:
0.00035%
HypeRank:
697,538
*All traffic values are estimates only.

Traffic sources

Direct:
0%
Referral:
37.49%
Search:
62.51%
Social:
0%
Paid:
0%

Visitors by country

Country
Users%
 
Taiwan 44.50%
 
Philippines 43.07%
 
Japan 12.44%

Where do visitors go on cururu.jp?

 
Reach%Pageviews%PerUser
cururu.jp
100.00%100.00%1.4
Last update was 61 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with cururu.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:
4
Bing Index:
17

 

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:
  cururu.jp
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
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 $116.4 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $3.5K and annual gross revenue of approximately $42.5K. Based on these figures, the site's net worth is estimated at around $92.2K.

How much would cururu.jp make?

Daily Revenue:
$116.36
Monthly Revenue:
$3,490.80
Yearly Revenue:
$42,471.40
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Taiwan 10,749$2.47
 
Philippines 10,403$2.08
 
Japan 3,005$1.08

Loss of money due to Adblock?

Daily Revenue Loss:
$0.57
Monthly Revenue Loss:
$17.21
Yearly Revenue Loss:
$209.39
Daily Pageviews Blocked:
2,538
Monthly Pageviews Blocked:
76,146
Yearly Pageviews Blocked:
926,449

Daily revenue loss by country

 
CountryBlockedLost Money
 
Taiwan 1,720$0.40
 
Philippines 728$0.15
 
Japan 90$0.03

How much is cururu.jp worth?

Website Value:
$92.2K

Ad Experience Report

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

Mobile summary

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

Cururu.jp may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
13.32.145.90
ASN:
AS16509 
ISP:
Amazon.com, Inc. 
Server Location:
Tokyo
Tokyo, 13
102-0082
United States, US
 

Other sites hosted on 13.32.145.90

There are no other sites hosted on this IP

How fast does cururu.jp load?

The average loading time of cururu.jp is 803 ms. The Desktop speed index is 73 and mobile speed index is 30.
Average Load Time:
803 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 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)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
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%

Origin Data

All pages served from this origin have an 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)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
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%

Lab Data

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 Contentful Paint 1.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Time to Interactive 2.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
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
Total Blocking Time 10 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
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
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
Speed Index 1.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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
First Meaningful Paint 1.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint 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
Efficiently encode images  
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images
Serve images in next-gen formats  
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats
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

Page Speed (Google PageSpeed Insights) - Mobile

30
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
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%

Origin Data

All pages served from this origin have an 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)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
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%

Lab Data

Largest Contentful Paint 21.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
First Contentful Paint 4.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
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
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 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
Total Blocking Time 1,790 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
Serve images in next-gen formats  
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
Efficiently encode images  
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images
Speed Index 8.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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 5.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint 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
Time to Interactive 15.1 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

Does cururu.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 cururu.jp are reduced by -16%.
cururu.jp use gzip compression.
Original size: 9.71 KB
Compressed size: 11.25 KB
File reduced by: 1.55 KB (-16%)

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. cururu.jp has 70 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  70
Safety Confidence:
  10

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. cururu.jp supports HTTPS.
 cururu.jp supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: cururu.jp
Organization:
Location:
Issuer: Amazon RSA 2048 M03
Valid from: Aug 15 00:00:00 2023 GMT
Valid until: Sep 12 23:59:59 2024 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: Amazon RSA 2048 M03
Organization: Amazon
Location: US
Issuer: Amazon Root CA 1
Valid from: Aug 23 22:26:04 2022 GMT
Valid until: Aug 23 22:26:04 2030 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: Amazon Root CA 1
Organization: Amazon
Location: US
Issuer: Starfield Services Root Certificate Authority - G2
Valid from: May 25 12:00:00 2015 GMT
Valid until: Dec 31 01:00:00 2037 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: Starfield Services Root Certificate Authority - G2
Organization: "Starfield Technologies, Inc."
Location: Scottsdale, Arizona, US
Issuer:
Valid from: Sep 2 00:00:00 2009 GMT
Valid until: Jun 28 17:39:16 2034 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.
 cururu.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.
content-type: text/html; charset=UTF-8
server: nginx/1.24.0
date: Sun, 28 Jan 2024 06:16:20 GMT
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
set-cookie: PHPSESSID=fsjjm2qs8j05h3el8lf308bd50; path=/; secure; HttpOnly
x-cache: Miss from cloudfront
via: 1.1 28f110beed532776cb7e7d4f319b2230.cloudfront.net (CloudFront)
x-amz-cf-pop: CDG50-C2
alt-svc: h3=":443"; ma=86400
x-amz-cf-id: 8UteHdhotwcUyQlnW26sJtxYk24GLVYUIDM-X3H8mJ86JTLrHX9nTQ==

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=XXcnrBDBOeSPz8QDqtqSbO1-aqADwsdkanM1vmFj5aQ 300
MX aspmx.l.google.com 300
MX alt3.aspmx.l.google.com 300
MX alt4.aspmx.l.google.com 300
MX alt1.aspmx.l.google.com 300
MX alt2.aspmx.l.google.com 300
SOA 900
Mname ns-349.awsdns-43.com
Rname awsdns-hostmaster.amazon.com
Serial Number 1
Refresh 7200
Retry 900
Expire 1209600
Minimum TTL 86400
A 13.32.145.32 2
A 13.32.145.113 2
A 13.32.145.106 2
A 13.32.145.90 2
NS ns-1554.awsdns-02.co.uk 86342
NS ns-1122.awsdns-12.org 86342
NS ns-349.awsdns-43.com 86342
NS ns-638.awsdns-15.net 86342

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 May 1, 2018 and will expire on May 31, 2024 if not renewed. This website is now assigned through the registrar . The WHOIS data for this website's domain was last updated on October 19, 2023.
Domain Created:
2018-05-01
Domain Expires:
2024-05-31
Domain Updated:
2023-10-19
Domain Age:
5 years 10 months 28 days
Domain Owner:
Uchiumi Shunsuke
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]                   CURURU.JP

[Registrant]                    Uchiumi Shunsuke

[Name Server]                   ns-349.awsdns-43.com
[Name Server]                   ns-1122.awsdns-12.org
[Name Server]                   ns-638.awsdns-15.net
[Name Server]                   ns-1554.awsdns-02.co.uk
[Signing Key]                   

[Created on]                    2018/05/01
[Expires on]                    2024/05/31
[Status]                        Active
[Last Updated]                  2023/10/19 12:51:54 (JST)

Contact Information:
[Name]                          Uchiumi Shunsuke
[Email]                         email
[Web Page]                       
[Postal code]                   273-0025
[Postal Address]                Chiba funabashishi innaicho 623-5-203
[Phone]                         +81.9036800371
[Fax]