ilovewhisky.blog Ilovewhisky.blog

   
Ilovewhisky | whisky thoughts and other things…

Domain Summary

What is the traffic rank for Ilovewhisky.blog?

• Ilovewhisky.blog ranks #6,501,297 globally on HypeStat.

What percent of global Internet users visit Ilovewhisky.blog?

1.0E-7% of global Internet users visit Ilovewhisky.blog

How many people visit Ilovewhisky.blog each day?

• Ilovewhisky.blog receives approximately 5 visitors and 5 page impressions per day.

How much Ilovewhisky.blog can earn?

• Ilovewhisky.blog should earn about $0.02/day from advertising revenue.

What is Ilovewhisky.blog estimated value?

• Estimated value of Ilovewhisky.blog is $16.64.

What IP addresses does Ilovewhisky.blog resolve to?

• Ilovewhisky.blog resolves to the IP addresses 192.0.78.25.

Where are Ilovewhisky.blog servers located in?

• Ilovewhisky.blog has servers located in San Francisco, California, 94110, United States.

ilovewhisky.blog Profile

Title:ilovewhisky | whisky thoughts and other things…
Description:whisky thoughts and other things...

What technologies does ilovewhisky.blog use?

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

ilovewhisky.blog Traffic Analysis

Ilovewhisky.blog is ranked #6,501,297 in the world. This website is viewed by an estimated 5 visitors daily, generating a total of 5 pageviews. This equates to about 151.5 monthly visitors.
Daily Visitors5
Monthly Visits151.5
Pages per Visit1.00
Visit duration07:46
Bounce Rate n/a
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
5
Monthly Visits:
152
Pages per Visit:
1.00
Daily Pageviews:
5
Avg. visit duration:
07:46
Bounce rate:
n/a
Global Reach:
1.0E-7%
Monthly Visits (SEMrush):
138
Monthly Unique Visitors (SEMrush):
138
HypeRank:
6,501,297
SEMrush Rank:
16,407,105
*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%
Last update was 244 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with ilovewhisky.blog 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:
610
Bing Index:
199
Baidu Index:
1

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 ilovewhisky.blog is 14.
Domain Authority:
  14
Page Authority:
  17
MozRank:
  2

 

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:
  ilovewhisky.blog
Rank:
(Rank based on keywords, cost and organic traffic)
  16,407,105
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  1
Organic Traffic:
(Number of visitors coming from top 20 search results)
  8
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $1.00

Revenue report

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

How much would ilovewhisky.blog make?

Daily Revenue:
$0.02
Monthly Revenue:
$0.60
Yearly Revenue:
$7.30
*All earnings values are estimates only.

How much is ilovewhisky.blog worth?

Website Value:
$16.6

Ad Experience Report

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

Mobile summary

Root domain:
ilovewhisky.blog
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:
ilovewhisky.blog
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:
ilovewhisky.blog
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 ilovewhisky.blog hosted?

Ilovewhisky.blog may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
192.0.78.25
ASN:
AS2635 
ISP:
Automattic, Inc 
Server Location:
San Francisco
California, CA
94110
United States, US
 

Other sites hosted on 192.0.78.25

How fast does ilovewhisky.blog load?

The average loading time of ilovewhisky.blog is 359 ms. The Desktop speed index is 63 and mobile speed index is 26.
Average Load Time:
359 ms

Page Speed (Google PageSpeed Insights) - Desktop

63
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

First Meaningful Paint 0.7 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
Time to Interactive 4.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Max Potential First Input Delay 380 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. 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
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
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
Total Blocking Time 960 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 0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
Speed Index 1.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Largest Contentful Paint 1.1 s
Largest Contentful Paint marks the time at which the largest 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

Page Speed (Google PageSpeed Insights) - Mobile

26
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

First Contentful Paint 3.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
Max Potential First Input Delay 480 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
First Contentful Paint (3G) 7920 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. 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
First Meaningful Paint 3.9 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
Total Blocking Time 1,400 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. 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
Speed Index 10.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Largest Contentful Paint 6.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Time to Interactive 26.5 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
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

Does ilovewhisky.blog 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 ilovewhisky.blog are reduced by 72%.
ilovewhisky.blog use br compression.
Original size: 118.4 KB
Compressed size: 32.95 KB
File reduced by: 85.45 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.
Status:
  UNKNOWN

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. ilovewhisky.blog supports HTTPS.
 ilovewhisky.blog supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: *.wordpress.com
Organization:
Location:
Issuer: Sectigo ECC Domain Validation Secure Server CA
Valid from: Nov 23 00:00:00 2022 GMT
Valid until: Dec 24 23:59:59 2023 GMT
Authority: CA:FALSE
Keysize:
Common Name: Sectigo ECC Domain Validation Secure Server CA
Organization: Sectigo Limited
Location: Salford, Greater Manchester, GB
Issuer: USERTrust ECC Certification Authority
Valid from: Nov 2 00:00:00 2018 GMT
Valid until: Dec 31 23:59:59 2030 GMT
Authority: CA:TRUE
Keysize:
Common Name: USERTrust ECC 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:

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.
 ilovewhisky.blog 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: nginx
date: Wed, 21 Jun 2023 21:57:05 GMT
content-type: text/html; charset=utf-8
location: https://ilovewhisky.wordpress.com/
strict-transport-security: max-age=31536000
vary: Cookie
x-ac: 2.mdw _dca MISS

HTTP/2 200 
server: nginx
date: Wed, 21 Jun 2023 21:57:06 GMT
content-type: text/html; charset=UTF-8
vary: Accept-Encoding
x-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header.
host-header: WordPress.com
vary: accept, content-type, cookie
link: <https://wp.me/7XvxY>; rel=shortlink
content-encoding: br
x-ac: 1.mdw _dca MISS
strict-transport-security: max-age=31536000

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 ns1.wordpress.com
Rname hostmaster.wordpress.com
Serial Number 2005071858
Refresh 14400
Retry 7200
Expire 604800
Minimum TTL 300
A 192.0.78.24 300
A 192.0.78.25 300
NS ns1.wordpress.com 3600
NS ns2.wordpress.com 3600
NS ns3.wordpress.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 January 5, 2018 and will expire on January 5, 2024 if not renewed. This website is now assigned through the registrar Automattic Inc.. The WHOIS data for this website's domain was last updated on March 14, 2023.
Domain Created:
2018-01-05
Domain Expires:
2024-01-05
Domain Updated:
2023-03-14
Domain Age:
6 years 1 months 16 days
Domain Registrar:
Automattic Inc.
Domain Owner:
Knock Knock WHOIS Not There, LLC
WhoIs:
 

Domain Name: ilovewhisky.blog
Registry Domain ID: D120409966-CNIC
Registrar WHOIS Server: whois.sawbuck.com
Registrar URL: http://www.automattic.com/
Updated Date: 2023-03-14T18:09:28Z
Creation Date: 2018-01-05T11:21:21Z
Registrar Registration Expiration Date: 2024-01-05T23:59:59Z
Registrar: Automattic Inc.
Registrar IANA ID: 1531
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.8772733049
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Private Whois 
Registrant Organization: Knock Knock WHOIS Not There, LLC
Registrant Street: 9450 SW Gemini Dr #63259
Registrant City: Beaverton
Registrant State/Province: 
Registrant Postal Code: 97008-7105
Registrant Country: US
Registrant Phone: +1.8772738550
Registrant Phone Ext: 
Registrant Fax: 
Registrant Fax Ext: 
Registrant Email: email
Registry Admin ID: Not Available From Registry
Admin Name: Private Whois 
Admin Organization: Knock Knock WHOIS Not There, LLC
Admin Street: 9450 SW Gemini Dr #63259
Admin City: Beaverton
Admin State/Province: 
Admin Postal Code: 97008-7105
Admin Country: US
Admin Phone: +1.8772738550
Admin Phone Ext: 
Admin Fax: 
Admin Fax Ext: 
Admin Email: email
Registry Tech ID: Not Available From Registry
Tech Name: Private Whois 
Tech Organization: Knock Knock WHOIS Not There, LLC
Tech Street: 9450 SW Gemini Dr #63259
Tech City: Beaverton
Tech State/Province: 
Tech Postal Code: 97008-7105
Tech Country: US
Tech Phone: +1.8772738550
Tech Phone Ext: 
Tech Fax: 
Tech Fax Ext: 
Tech Email: email
Registry Billing ID: Not Available From Registry
Billing Name: Private Whois 
Billing Organization: Knock Knock WHOIS Not There, LLC
Billing Street: 9450 SW Gemini Dr #63259
Billing City: Beaverton
Billing State/Province: 
Billing Postal Code: 97008-7105
Billing Country: US
Billing Phone: +1.8772738550
Billing Phone Ext: 
Billing Fax: 
Billing Fax Ext: 
Billing Email: email
Name Server: ns1.wordpress.com 
Name Server: ns2.wordpress.com 
Name Server: ns3.wordpress.com 
DNSSEC: unsigned
Whoisprivacy: 5
URL of the ICANN WHOIS Data Problem Reporting System: https://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-06-21T21:57:58Z