food.ee website information.
food.ee domain name is registered by .EE top-level domain registry. See the other sites registred in .EE domain zone.
No name server records were found.
and probably website food.ee is hosted by INFOSPHERE NTT PC Communications, Inc., JP web hosting company. Check the complete list of other most popular websites hosted by INFOSPHERE NTT PC Communications, Inc., JP hosting company.
According to Alexa traffic rank the highest website food.ee position was 6359 (in the world). The lowest Alexa rank position was 997298. Now website food.ee ranked in Alexa database as number 494334 (in the world).
Website food.ee Desktop speed measurement score (77/100) is better than the results of 63.93% of other sites shows that the page desktop performance can be improved.
food.ee Mobile usability score (100/100) is better than the results of 100% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of food.ee (63/100) is better than the results of 61.76% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
| Date | Rank | Change |
|---|---|---|
| Nov-18-2024 | 494,334 | 3,255 |
| Nov-17-2024 | 497,589 | -5,574 |
| Nov-16-2024 | 492,015 | -5,481 |
| Nov-15-2024 | 486,534 | 15,947 |
| Nov-14-2024 | 502,481 | -16,889 |
| Nov-13-2024 | 485,592 | 0 |
| Nov-12-2024 | 485,592 | 0 |
Advertisement
food.ee Rank History
Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.
food.ee whois
WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.
Search results may not be used for commercial, advertising, recompilation,
repackaging, redistribution, reuse, obscuring or other similar activities.
Estonia .ee Top Level Domain WHOIS server
Domain:
name: food.ee
status: ok (paid and in zone)
registered: 2010-07-04 05:46:10 +03:00
changed: 2024-08-13 08:59:10 +03:00
expire: 2025-09-06
outzone:
delete:
Registrant:
name: Private Person
email: Not Disclosed - Visit www.internet.ee for webbased WHOIS
phone: Not Disclosed - Visit www.internet.ee for webbased WHOIS
changed: Not Disclosed
Administrative contact:
name: Not Disclosed
email: Not Disclosed - Visit www.internet.ee for webbased WHOIS
changed: Not Disclosed
Technical contact:
name: Not Disclosed
email: Not Disclosed - Visit www.internet.ee for webbased WHOIS
changed: Not Disclosed
Registrar:
name: Name SRS AB
url: https://www.namesrs.com
phone: +46.313011220
changed: 2023-12-15 12:41:40 +02:00
Name servers:
nserver: ns-1417.awsdns-49.org
nserver: ns-1749.awsdns-26.co.uk
nserver: ns-274.awsdns-34.com
nserver: ns-535.awsdns-02.net
changed: 2013-05-16 09:58:47 +03:00
Estonia .ee Top Level Domain WHOIS server
More information at http://internet.ee
food.ee server information
Servers Location
| IP Address |
|---|
| Country |
|---|
food.ee desktop page speed rank
Last tested: 2018-07-02
food.ee Desktop Speed Test Quick Summary
priority - 10 Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://fancyfox-cdn.food.ee/global-assets/logo-drop-shadow.png (expiration not specified)
https://fancyfox-cdn.food.ee/global-assets/logo-eatwell.svg (expiration not specified)
https://s3.amazonaws.com/fancy-fox-cdn/content/upl…017/04/scroll-icon.svg (expiration not specified)
https://js.hs-scripts.com/2116999.js (60 seconds)
https://static.hotjar.com/c/hotjar-433224.js?sv=5 (60 seconds)
https://js.hs-analytics.net/analytics/1530529800000/2116999.js (5 minutes)
https://js.hsadspixel.net/fb.js (10 minutes)
https://js.hscollectedforms.net/collectedforms.js (10 minutes)
https://js.hsforms.net/forms/v2.js (10 minutes)
https://js.hsleadflows.net/leadflows.js (10 minutes)
https://www.google-analytics.com/gtm/js?id=GTM-T2G…d=526013879.1530529764 (15 minutes)
https://www.googletagmanager.com/gtag/js?id=AW-944514028 (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-KQ35XQC (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/295927…2143?v=2.8.18&r=stable (20 minutes)
https://bat.bing.com/bat.js (30 minutes)
https://maps.googleapis.com/maps/api/js?v=3.29&key…raries=geometry,places (30 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://js-agent.newrelic.com/nr-1071.min.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 10 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 2 blocking script resources and 7 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
https://food.ee/wp-content/themes/foodeeTheme/js/jquery.geocomplete.min.js
Optimize CSS Delivery of the following:
https://food.ee/wp-content/themes/foodeeTheme/css/style.min.css?ver=6
https://food.ee/wp-content/themes/foodeeTheme/css/…query.maximage.min.css
https://cdnjs.cloudflare.com/ajax/libs/motion-ui/1.1.1/motion-ui.min.css
https://fonts.googleapis.com/css?family=Lato%3A300…bset=latin%2Clatin-ext
https://www.food.ee/wp-content/themes/foodeeTheme/…nericons.css?ver=3.0.3
https://www.food.ee/wp-content/plugins/wp-paginate…paginate.css?ver=1.3.1
priority - 7 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 65.9KiB (41% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…/logo-01%402x1-EY2.png could save 14.5KiB (88% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/uploads/2017/04/mid-sec.jpg could save 7.5KiB (48% reduction).
Compressing and resizing https://fancyfox-cdn.food.ee/global-assets/logo-drop-shadow.png could save 5.7KiB (58% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…5%402x1-mailchimp1.png could save 2.9KiB (27% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…-02%402x1-comcast1.png could save 2.5KiB (37% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…-01%402x1-aritzia1.png could save 2KiB (19% reduction).
Compressing https://www.food.ee/wp-content/themes/foodeeTheme/images/logo-red.png could save 1.4KiB (22% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…x1-morgan-stanley1.png could save 1.4KiB (26% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…o-01%402x1-diapad1.png could save 1.3KiB (18% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…1%402x1-hootsuite1.png could save 1.3KiB (19% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…ogo-01%402x1-uber1.png could save 1.2KiB (15% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…1%402x1-atlassian1.png could save 1.1KiB (24% reduction).
Compressing https://www.food.ee/wp-content/themes/foodeeTheme/images/mobilelogo.png could save 1.1KiB (29% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…logo-01%402x1-EA11.png could save 993B (44% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…o-01%402x1-amazon1.png could save 990B (22% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…x1-weatherchannel1.png could save 962B (23% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…01%402x1-deloitte1.png could save 932B (27% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…1%402x1-microsoft1.png could save 883B (22% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…01%402x1-facebook1.png could save 868B (24% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…ogo-01%402x1-visa1.png could save 855B (24% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…ogo-01%402x1-kpmg1.png could save 835B (23% reduction).
Compressing https://fancy-fox.s3.amazonaws.com/btn-chat.png could save 610B (33% reduction).
priority - 1 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 6.4KiB (67% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…017/04/scroll-icon.svg could save 695B (50% reduction).
priority - 0 Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 1.5KiB (12% reduction).
priority - 0 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 164B (36% reduction).
food.ee Desktop Resources
| Total Resources | 117 |
| Number of Hosts | 37 |
| Static Resources | 79 |
| JavaScript Resources | 39 |
| CSS Resources | 7 |
food.ee Desktop Resource Breakdown
food.ee mobile page speed rank
Last tested: 2018-06-30
food.ee Mobile Speed Test Quick Summary
priority - 40 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 2 blocking script resources and 7 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
https://food.ee/wp-content/themes/foodeeTheme/js/jquery.geocomplete.min.js
Optimize CSS Delivery of the following:
https://food.ee/wp-content/themes/foodeeTheme/css/style.min.css?ver=6
https://food.ee/wp-content/themes/foodeeTheme/css/…query.maximage.min.css
https://cdnjs.cloudflare.com/ajax/libs/motion-ui/1.1.1/motion-ui.min.css
https://fonts.googleapis.com/css?family=Lato%3A300…bset=latin%2Clatin-ext
https://www.food.ee/wp-content/themes/foodeeTheme/…nericons.css?ver=3.0.3
https://www.food.ee/wp-content/plugins/wp-paginate…paginate.css?ver=1.3.1
priority - 15 Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://fancyfox-cdn.food.ee/global-assets/logo-drop-shadow.png (expiration not specified)
https://fancyfox-cdn.food.ee/global-assets/logo-eatwell.svg (expiration not specified)
https://s3.amazonaws.com/fancy-fox-cdn/content/upl…017/04/scroll-icon.svg (expiration not specified)
https://js.hs-scripts.com/2116999.js (60 seconds)
https://static.hotjar.com/c/hotjar-433224.js?sv=5 (60 seconds)
https://js.hs-analytics.net/analytics/1530382500000/2116999.js (5 minutes)
https://js.hsadspixel.net/fb.js (10 minutes)
https://js.hscollectedforms.net/collectedforms.js (10 minutes)
https://js.hsforms.net/forms/v2.js (10 minutes)
https://js.hsleadflows.net/leadflows.js (10 minutes)
https://www.google-analytics.com/gtm/js?id=GTM-T2G…d=496122529.1530382239 (15 minutes)
https://www.googletagmanager.com/gtag/js?id=AW-944514028 (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-KQ35XQC (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/295927…2143?v=2.8.18&r=stable (20 minutes)
https://bat.bing.com/bat.js (30 minutes)
https://maps.googleapis.com/maps/api/js?v=3.29&key…raries=geometry,places (30 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://js-agent.newrelic.com/nr-1071.min.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)
https://sjs.bizographics.com/insight.min.js (11.5 hours)
priority - 6 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 61.6KiB (39% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…/logo-01%402x1-EY2.png could save 14.5KiB (88% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/uploads/2017/04/mid-sec.jpg could save 7.5KiB (48% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…5%402x1-mailchimp1.png could save 2.9KiB (27% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…-02%402x1-comcast1.png could save 2.5KiB (37% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…-01%402x1-aritzia1.png could save 2KiB (19% reduction).
Compressing https://www.food.ee/wp-content/themes/foodeeTheme/images/logo-red.png could save 1.4KiB (22% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…x1-morgan-stanley1.png could save 1.4KiB (26% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…o-01%402x1-diapad1.png could save 1.3KiB (18% reduction).
Compressing https://fancyfox-cdn.food.ee/global-assets/logo-drop-shadow.png could save 1.3KiB (14% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…1%402x1-hootsuite1.png could save 1.3KiB (19% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…ogo-01%402x1-uber1.png could save 1.2KiB (15% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…1%402x1-atlassian1.png could save 1.1KiB (24% reduction).
Compressing https://www.food.ee/wp-content/themes/foodeeTheme/images/mobilelogo.png could save 1.1KiB (29% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…logo-01%402x1-EA11.png could save 993B (44% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…o-01%402x1-amazon1.png could save 990B (22% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…x1-weatherchannel1.png could save 962B (23% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…01%402x1-deloitte1.png could save 932B (27% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…1%402x1-microsoft1.png could save 883B (22% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…01%402x1-facebook1.png could save 868B (24% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…ogo-01%402x1-visa1.png could save 855B (24% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…ogo-01%402x1-kpmg1.png could save 835B (23% reduction).
Compressing https://fancy-fox.s3.amazonaws.com/btn-chat.png could save 610B (33% reduction).
priority - 1 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 6.4KiB (67% reduction).
Compressing https://s3.amazonaws.com/fancy-fox-cdn/content/upl…017/04/scroll-icon.svg could save 695B (50% reduction).
priority - 0 Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 1.5KiB (12% reduction).
priority - 0 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 164B (36% reduction).
food.ee Mobile Resources
| Total Resources | 111 |
| Number of Hosts | 37 |
| Static Resources | 79 |
| JavaScript Resources | 39 |
| CSS Resources | 7 |
food.ee Mobile Resource Breakdown
food.ee mobile page usability
Last tested: 2018-06-30
food.ee similar domains
www.food.net
www.food.org
www.food.info
www.food.biz
www.food.us
www.food.mobi
www.ood.ee
www.food.ee
www.cood.ee
www.fcood.ee
www.cfood.ee
www.dood.ee
www.fdood.ee
www.dfood.ee
www.rood.ee
www.frood.ee
www.rfood.ee
www.tood.ee
www.ftood.ee
www.tfood.ee
www.good.ee
www.fgood.ee
www.gfood.ee
www.vood.ee
www.fvood.ee
www.vfood.ee
www.fod.ee
www.fiod.ee
www.foiod.ee
www.fiood.ee
www.fkod.ee
www.fokod.ee
www.fkood.ee
www.flod.ee
www.folod.ee
www.flood.ee
www.fpod.ee
www.fopod.ee
www.fpood.ee
www.foid.ee
www.fooid.ee
www.fokd.ee
www.fookd.ee
www.fold.ee
www.foold.ee
www.fopd.ee
www.foopd.ee
www.foo.ee
www.foox.ee
www.foodx.ee
www.fooxd.ee
www.foos.ee
www.foods.ee
www.foosd.ee
www.fooe.ee
www.foode.ee
www.fooed.ee
www.foor.ee
www.foodr.ee
www.foord.ee
www.foof.ee
www.foodf.ee
www.foofd.ee
www.fooc.ee
www.foodc.ee
www.foocd.ee
food.ee Ping
Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.
food.ee TRACEROUTE
Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.