food.blog Food.blog

   
Food.blog – Get your subdomain of food.blog

Domain Summary

What is the traffic rank for Food.blog?

• Food.blog ranks #1,667,685 globally on HypeStat.

What percent of global Internet users visit Food.blog?

• 7.2E-5% of global Internet users visit Food.blog

How many people visit Food.blog each day?

• Food.blog receives approximately 3.6K visitors and 7,099 page impressions per day.

Which countries does Food.blog receive most of its visitors from?

• Food.blog is mostly visited by people located in India,United States,Indonesia.

How much Food.blog can earn?

• Food.blog should earn about $22.44/day from advertising revenue.

What is Food.blog estimated value?

• Estimated value of Food.blog is $22,176.37.

What IP addresses does Food.blog resolve to?

• Food.blog resolves to the IP addresses 192.0.78.30.

Where are Food.blog servers located in?

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

food.blog Profile

Title:Food.blog – Get your subdomain of food.blog
Description:Artwork by Tony Ruth Site by Automattic Design
Edit Site Info

What technologies does food.blog use?

These are the technologies used at food.blog. food.blog has a total of 6 technologies installed in 8 different categories.
Font Scripts
Google Font API Google Font API
Web Servers
Nginx Nginx
Reverse proxies
Nginx Nginx
JavaScript Frameworks
Prototype Prototype
CMS
WordPress WordPress
Blogs
WordPress WordPress
Programming Languages
PHP PHP
Databases
MySQL MySQL

food.blog Traffic Analysis

Food.blog is ranked #1,667,685 in the world. This website is viewed by an estimated 3.6K visitors daily, generating a total of 7.1K pageviews. This equates to about 107.6K monthly visitors.
Daily Visitors3.6K
Monthly Visits107.6K
Pages per Visit2.00
Visit duration07:49
Bounce Rate60.46%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
3,550
Monthly Visits:
107,565
Pages per Visit:
2.00
Daily Pageviews:
7,099
Avg. visit duration:
07:49
Bounce rate:
60.46%
Global Reach:
7.2E-5%
HypeRank:
1,667,685
SEMrush Rank:
603,661
*All traffic values are estimates only.

Traffic sources

Direct:
80.71%
Referral:
14.11%
Search:
2.06%
Social:
3.12%
Paid:
0%

Visitors by country

Country
Users%
 
India 29.3%
 
United States 21.2%
 
Indonesia 4.9%

Where do visitors go on food.blog?

 
Reach%Pageviews%PerUser
onlinecake.food.blog
15.90%10.73%1
lisa.food.blog
2.83%1.53%1
OTHER
0%88.31%0
Last update was 1868 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with food.blog 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:
  food.blog
Rank:
(Rank based on keywords, cost and organic traffic)
  603,661
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 $22.4 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $673.2 and annual gross revenue of approximately $8.2K. Based on these figures, the site's net worth is estimated at around $22.2K.

How much would food.blog make?

Daily Revenue:
$22.44
Monthly Revenue:
$673.20
Yearly Revenue:
$8,190.60
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 1,633$7.89
 
India 1,846$0.70
 
Indonesia 142$0.02

Loss of money due to Adblock?

Daily Revenue Loss:
$1.62
Monthly Revenue Loss:
$48.75
Yearly Revenue Loss:
$593.12
Daily Pageviews Blocked:
893
Monthly Pageviews Blocked:
26,792
Yearly Pageviews Blocked:
325,965

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 294$1.42
 
India 517$0.20
 
Indonesia 82$0.01

How much is food.blog worth?

Website Value:
$22.2K

Ad Experience Report ▼

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

Mobile summary

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

Food.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.30
ASN:
AS2635 
ISP:
Automattic, Inc 
Server Location:
San Francisco
California, CA
94110
United States, US
 

Other sites hosted on 192.0.78.30

How fast does food.blog load? ▼

The average loading time of food.blog is 3035 ms. The Desktop speed index is 70 and mobile speed index is 100.
Average Load Time:
3035 ms

Page Speed (Google PageSpeed Insights) - Desktop

70
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


Page Speed (Google PageSpeed Insights) - Mobile

100
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

Does food.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 food.blog are reduced by %.
food.blog does not use compression.
Original size: n/a
Compressed size: n/a
File reduced by: (%)

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

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. food.blog supports HTTPS.
 food.blog supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: tls.automattic.com
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Apr 2 23:23:49 2019 GMT
Valid until: Jul 1 23:23:49 2019 GMT
Authority:
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.
 food.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. 
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Sun, 07 Apr 2019 11:57:04 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://www.food.blog/
X-ac: 3.ord _dca
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Sun, 07 Apr 2019 11:57:04 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Strict-Transport-Security: max-age=86400
Location: https://food.blog/
X-ac: 3.ord _dca
HTTP/1.1 200 OK
Server: nginx
Date: Sun, 07 Apr 2019 11:57:05 GMT
Content-Type: text/html; charset=UTF-8
Connection: close
Strict-Transport-Security: max-age=86400
Vary: Accept-Encoding
Last-Modified: Sun, 07 Apr 2019 11:57:04 GMT
Cache-Control: max-age=299, must-revalidate
X-nananana: Batcache
Vary: Cookie
X-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header.
X-Frame-Options: SAMEORIGIN
Link: <https://wp.me/P83xja-c>; rel=shortlink
X-ac: 3.ord _dca

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 v=spf1 -all 3589
SOA 3589
Mname ns1.automattic.com
Rname hostmaster.automattic.com
Serial Number 2016111112
Refresh 28800
Retry 7200
Expire 604800
Minimum TTL 86400
A 192.0.78.30 589
A 192.0.78.31 589
NS ns2.automattic.com 3589
NS ns3.automattic.com 3589
NS ns4.automattic.com 3589
NS ns1.automattic.com 3589

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 October 10, 2016 and will expire on May 18, 2024 if not renewed. This website is now assigned through the registrar . The WHOIS data for this website's domain was last updated on May 18, 2024.
Domain Created:
2016-10-10
Domain Age:
7 years 7 months 8 days
WhoIs:
 

whois lookup at whois.nic.blog...Domain Name: FOOD.BLOG
Registry Domain ID: D_0000E3A4_52BA8ED820B24E05BA2D8B7FBF800088_000001469E2A0088-BLOG
Registrar WHOIS Server: whois.nic.blog
Registrar URL: http://www.nic.blog
Updated Date: 2018-10-10T15:42:09Z
Creation Date: 2016-10-10T15:41:21Z
Registry Expiry Date: 2019-10-10T15:41:21Z
Registrar: blog Internal Billing Registrar
Registrar IANA ID: 9998
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +44.1865332482
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: CA
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns3.automattic.com.
Name Server: ns1.automattic.com.
Name Server: ns2.automattic.com.
Name Server: ns4.automattic.com.
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2019-04-07T11:57:13Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

This WHOIS information is provided for free by Nominet UK, the central registry for .blog domain names. This information and the .blog WHOIS are:

Copyright Nominet UK 2019.

You may not access the .blog WHOIS or use any data from it except as permitted by the terms of use available in full at http://www.nominet.org.uk/whois, which includes restrictions on: (A) use of the data for advertising, or its repackaging, recompilation, redistribution or reuse (B) obscuring, removing or hiding any or all of this notice and (C) exceeding query rate or volume limits. The data is provided on an 'as-is' basis and may lag behind the register. No guarantee is given as to the accuracy of the data provided. Access may be withdrawn or restricted at any time.