homis.jp Homis.jp

   
Homis

Domain Summary

What is the traffic rank for Homis.jp?

• Homis.jp ranks #604,238 globally on HypeStat.

What percent of global Internet users visit Homis.jp?

• 3.41E-5% of global Internet users visit Homis.jp

How many people visit Homis.jp each day?

• Homis.jp receives approximately 1.7K visitors and 13,113 page impressions per day.

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

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

How much Homis.jp can earn?

• Homis.jp should earn about $4.72/day from advertising revenue.

What is Homis.jp estimated value?

• Estimated value of Homis.jp is $4,923.21.

What IP addresses does Homis.jp resolve to?

• Homis.jp resolves to the IP addresses 153.120.24.230.

Where are Homis.jp servers located in?

• Homis.jp has servers located in Japan.

homis.jp Profile

Title:homis
Category:Health / Medicine
Edit Site Info

What technologies does homis.jp use?

These are the technologies used at homis.jp. homis.jp has a total of 3 technologies installed in 3 different categories.
Web Servers
Apache HTTP Server Apache HTTP Server
Programming Languages
PHP PHP
Operating Systems
Ubuntu Ubuntu

homis.jp Traffic Analysis

Homis.jp is ranked #604,238 in the world. This website is viewed by an estimated 1.7K visitors daily, generating a total of 13.1K pageviews. This equates to about 51K monthly visitors. Homis.jp traffic has decreased by 55.37% compared to last month.
Daily Visitors1.7K
79.69%
Monthly Visits51K
55.37%
Pages per Visit7.80
19.46%
Visit duration06:56
24.96%
Bounce Rate58.39%
44.22%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
1,682
Monthly Visits:
50,965
Pages per Visit:
7.80
Daily Pageviews:
13,113
Avg. visit duration:
06:56
Bounce rate:
58.39%
Global Reach:
3.41E-5%
Monthly Visits (SEMrush):
77,653
Monthly Unique Visitors (SEMrush):
836
Monthly Visits (SimilarWeb):
49,964
HypeRank:
604,238
SimilarWeb Rank:
604,238
*All traffic values are estimates only.

Traffic sources

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

Desktop vs Mobile

Desktop:
100.00%
Mobile:
0%

Total Visits Last 3 Months

11.1K
JAN
114.2K
FEB
51K
MAR

Visitors by country

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

*HypeStat.com is not promoting or affiliated with homis.jp 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:
  homis.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
Full SEMrush Report >>

Revenue report ▼

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

How much would homis.jp make?

Daily Revenue:
$4.72
Monthly Revenue:
$141.60
Yearly Revenue:
$1,722.80
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Japan 13,113$4.72

Loss of money due to Adblock?

Daily Revenue Loss:
$0.14
Monthly Revenue Loss:
$4.25
Yearly Revenue Loss:
$51.69
Daily Pageviews Blocked:
393
Monthly Pageviews Blocked:
11,802
Yearly Pageviews Blocked:
143,587

Daily revenue loss by country

 
CountryBlockedLost Money
 
Japan 393$0.14

How much is homis.jp worth?

Website Value:
$4.9K

Ad Experience Report ▼

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

Mobile summary

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

Homis.jp may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
153.120.24.230
ASN:
AS7684 
ISP:
SAKURA Internet Inc. 
Server Location:

Japan, JP
 

Other sites hosted on 153.120.24.230

There are no other sites hosted on this IP

How fast does homis.jp load? ▼

The average loading time of homis.jp is 1306 ms. The Desktop speed index is 77 and mobile speed index is 90.
Average Load Time:
1306 ms

Page Speed (Google PageSpeed Insights) - Desktop

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

First Contentful Paint (FCP)880ms 92% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 92% 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)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 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.

First Contentful Paint (FCP)983ms 90% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 90% 6% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 6% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
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%

Lab Data

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
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
Time to Interactive 1.7 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
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
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
Does not have 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
First Contentful Paint 1.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Meaningful Paint 1.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
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 about the Total Blocking Time metric
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 how to minimize third-party impact
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
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

Page Speed (Google PageSpeed Insights) - Mobile

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

First Contentful Paint (FCP)1.5s 92% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 84% 10% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 10% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
First Input Delay (FID)225ms 58% of loads for this page have a fast (<100ms) First Input Delay (FID) 58% 39% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 39% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 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.

First Contentful Paint (FCP)1.7s 77% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 77% 8% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 8% 14% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 14%
First Input Delay (FID)229ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 48% 49% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 49% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%

Lab Data

Time to Interactive 2.5 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
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
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 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
Speed Index 5.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Largest Contentful Paint 2.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest 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
Does not have 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
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
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 how to minimize third-party impact
First Meaningful Paint 2.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Contentful Paint 2.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful 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

Does homis.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 homis.jp are reduced by 61%.
homis.jp use gzip compression.
Original size: 4.53 KB
Compressed size: 1.77 KB
File reduced by: 2.77 KB (61%)

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. homis.jp supports HTTPS.
 homis.jp supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: *.homis.jp
Organization:
Location:
Issuer: FujiSSL Public Validation Authority - G3
Valid from: Nov 17 06:42:30 2023 GMT
Valid until: Nov 29 14:59:59 2024 GMT
Authority:
Keysize: 2048 Bits
Common Name: FujiSSL Public Validation Authority - G3
Organization: "SECOM Trust Systems CO.,LTD."
Location: JP
Issuer:
Valid from: Aug 22 07:41:02 2018 GMT
Valid until: Aug 22 07:41:02 2028 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name:
Organization: "SECOM Trust Systems CO.,LTD.", OU = Security Communication RootC
Location: JP
Issuer:
Valid from: May 29 05:00:39 2009 GMT
Valid until: May 29 05:00:39 2029 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.
 homis.jp does not support 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: Fri, 19 Apr 2024 19:24:03 GMT
Server: Apache/2.4.18 (Ubuntu)
Location: https://homis.jp/homic/
Content-Length: 282
Content-Type: text/html; charset=iso-8859-1

HTTP/1.1 302 Found
Date: Fri, 19 Apr 2024 19:24:03 GMT
Server: Apache/2.4.18 (Ubuntu)
Set-Cookie: PHPSESSID=u24pa587bi3tghgrrj8aedb2s0; path=/; domain=.homis.jp
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Location: ./login.php?jaddr=%2Fhomic%2F
Content-Length: 0
Content-Type: text/html; charset=UTF-8

HTTP/1.1 200 OK
Date: Fri, 19 Apr 2024 19:24:03 GMT
Server: Apache/2.4.18 (Ubuntu)
Set-Cookie: PHPSESSID=pfjsnq2dkps7fu7b14hb430pm7; path=/; domain=.homis.jp
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 1809
Content-Type: text/html; charset=UTF-8

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 master.dns.ne.jp
Rname tech.sakura.ad.jp
Serial Number 2024041701
Refresh 3600
Retry 900
Expire 3600000
Minimum TTL 3600
TXT firebase=homis-production 3600
TXT 20221117182104CDFEAB60EF04FF68E304191E04C354F11F7B5A6AFA900E8AB8316C7CB46A3735 3600
TXT 20231117144604EEBAAC1079202393CE0008B434A8E850159A1F348BC0A5C1602308E78BB88E13 3600
TXT v=spf1 include:_spf.firebasemail.com ~all 3600
TXT v=spf1 a:www2932.sakura.ne.jp a:faq.homis.jp mx ~all 3600
MX hmi.sakura.ne.jp 3600
A 153.120.24.230 28
NS ns1.dns.ne.jp 3600
NS ns2.dns.ne.jp 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 March 24, 2014 and will expire on March 31, 2025 if not renewed. This website is now assigned through the registrar . The WHOIS data for this website's domain was last updated on March 31, 2024.
Domain Created:
2014-03-24
Domain Expires:
2025-03-31
Domain Updated:
2024-03-31
Domain Age:
10 years 1 months 9 days
Domain Owner:
HOME MEDICAL INFORMATION SYSTEM
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]                   HOMIS.JP

[Registrant]                    HOME MEDICAL INFORMATION SYSTEM

[Name Server]                   ns1.dns.ne.jp
[Name Server]                   ns2.dns.ne.jp
[Signing Key]                   

[Created on]                    2014/03/24
[Expires on]                    2025/03/31
[Status]                        Active
[Last Updated]                  2024/04/01 01:05:04 (JST)

Contact Information:
[Name]                          SAKURA internet Inc.
[Email]                         email
[Web Page]                       
[Postal code]                   530-0001
[Postal Address]                Osaka
                                Osaka
                                11F,1-12-12,Umeda,Kita-ku
[Phone]                         06-6476-8790
[Fax]