FOODGAWKER.COM foodgawker | feed your eyes


foodgawker.com website information.

foodgawker.com website servers are located in United States and are responding from following IP address 66.55.84.236. Check the full list of most visited websites located in United States.

foodgawker.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.

Following name servers are specified for foodgawker.com domain:

  • ns76.domaincontrol.com
  • ns75.domaincontrol.com

and probably website foodgawker.com is hosted by domaincontrol.com web hosting company. Check the complete list of other most popular websites hosted by domaincontrol.com hosting company.

According to Alexa traffic rank the highest website foodgawker.com position was 12921 (in the world). The lowest Alexa rank position was 134135. Now website foodgawker.com ranked in Alexa database as number 35994 (in the world).

Website foodgawker.com Desktop speed measurement score (45/100) is better than the results of 14.84% of other sites shows that the page desktop performance can be improved.

foodgawker.com Mobile usability score (99/100) is better than the results of 87.11% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of foodgawker.com (61/100) is better than the results of 57.07% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
May-20-2019 35,99423,085
May-19-2019 59,0797,639
May-18-2019 66,71852,065
May-17-2019 118,783-76,588
May-16-2019 42,1956,874
May-15-2019 49,069-11,759
May-14-2019 37,31011,866

Advertisement

foodgawker.com 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.


foodgawker.com 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.


Domain Name: FOODGAWKER.COM
Registry Domain ID: 1492828484_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Update Date: 2012-06-13T16:08:59Z
Creation Date: 2008-06-13T03:59:02Z
Registrar Registration Expiration Date: 2018-06-13T03:59:02Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited http://www.icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited http://www.icann.org/epp#clientDeleteProhibited
Registry Registrant ID:
Registrant Name: T. Lai
Registrant Organization: gawkerverse
Registrant Street: P.O. Box 29477
Registrant City: San Francisco
Registrant State/Province: California
Registrant Postal Code: 94129-0477
Registrant Country: United States
Registrant Phone: +1.4153554580
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: support@gawkerverse.com
Registry Admin ID:
Admin Name: T. Lai
Admin Organization: gawkerverse
Admin Street: P.O. Box 29477
Admin City: San Francisco
Admin State/Province: California
Admin Postal Code: 94129
Admin Country: United States
Admin Phone: +1.4153554580
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: support@gawkerverse.com
Registry Tech ID:
Tech Name: T. Lai
Tech Organization: gawkerverse
Tech Street: P.O. Box 29477
Tech City: San Francisco
Tech State/Province: California
Tech Postal Code: 94129
Tech Country: United States
Tech Phone: +1.4153554580
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: support@gawkerverse.com
Name Server: NS1.FOODGAWKER.COM
Name Server: NS2.FOODGAWKER.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2015-06-13T08:00:00Z

foodgawker.com server information

Servers Location

foodgawker.com desktop page speed rank

Last tested: 2016-07-11


Desktop Speed Bad
45/100

foodgawker.com Desktop Speed Test Quick Summary


priority - 116 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 1.1MiB (72% reduction).

Compressing and resizing https://photo2.foodgawker.com/wp-content/uploads/2016/07/2713023.jpg could save 99.4KiB (82% reduction).
Compressing and resizing https://photo2.foodgawker.com/wp-content/uploads/2016/07/2713001.jpg could save 66KiB (79% reduction).
Compressing and resizing https://photo.foodgawker.com/wp-content/uploads/2016/07/2713019.jpg could save 65.6KiB (77% reduction).
Compressing and resizing https://photo2.foodgawker.com/wp-content/uploads/2016/07/2713209.jpg could save 62.4KiB (76% reduction).
Compressing and resizing https://photo.foodgawker.com/wp-content/uploads/2016/07/2712997.jpg could save 59KiB (77% reduction).
Compressing and resizing https://photo.foodgawker.com/wp-content/uploads/2016/07/2712945.jpg could save 54.3KiB (75% reduction).
Compressing and resizing https://photo.foodgawker.com/wp-content/uploads/2016/07/2713091.jpg could save 53KiB (77% reduction).
Compressing and resizing https://photo2.foodgawker.com/wp-content/uploads/2016/07/2713037.jpg could save 52.9KiB (77% reduction).
Compressing and resizing https://photo.foodgawker.com/wp-content/uploads/2016/07/2713221.jpg could save 52.3KiB (78% reduction).
Compressing and resizing https://photo2.foodgawker.com/wp-content/uploads/2016/07/2713081.jpg could save 47.4KiB (79% reduction).
Compressing and resizing https://photo2.foodgawker.com/wp-content/uploads/2016/07/2713181.jpg could save 46.3KiB (75% reduction).
Compressing and resizing https://photo.foodgawker.com/wp-content/uploads/2016/07/2712937.jpg could save 46.2KiB (78% reduction).
Losslessly compressing https://tpc.googlesyndication.com/simgad/6255816879302618772 could save 45.2KiB (35% reduction).
Compressing and resizing https://photo2.foodgawker.com/wp-content/uploads/2016/07/2713115.jpg could save 42.9KiB (75% reduction).
Compressing and resizing https://photo.foodgawker.com/wp-content/uploads/2016/07/2713147.jpg could save 42.2KiB (76% reduction).
Compressing and resizing https://photo.foodgawker.com/wp-content/uploads/2016/07/2713195.jpg could save 41.3KiB (77% reduction).
Compressing and resizing https://photo.foodgawker.com/wp-content/uploads/2016/07/2713013.jpg could save 41.2KiB (76% reduction).
Compressing and resizing https://photo2.foodgawker.com/wp-content/uploads/2016/07/2713201.jpg could save 37.9KiB (78% reduction).
Compressing and resizing https://photo.foodgawker.com/wp-content/uploads/2016/07/2713243.jpg could save 36KiB (73% reduction).
Compressing and resizing https://photo2.foodgawker.com/wp-content/uploads/2016/07/2712951.jpg could save 34.5KiB (77% reduction).
Compressing and resizing https://photo2.foodgawker.com/wp-content/uploads/2016/07/2712895.jpg could save 33.9KiB (78% reduction).
Compressing and resizing https://photo.foodgawker.com/wp-content/uploads/2016/07/2712955.jpg could save 33.6KiB (78% reduction).
Compressing and resizing https://photo2.foodgawker.com/wp-content/uploads/2016/07/2713223.jpg could save 30.5KiB (75% reduction).
Losslessly compressing https://tpc.googlesyndication.com/simgad/11437303881467094308 could save 3.7KiB (19% reduction).
Losslessly compressing https://static.foodgawker.com/wp-content/themes/Fo…ogo_6-7-13.png?ver=2.3 could save 1.9KiB (46% reduction).
Losslessly compressing https://tpc.googlesyndication.com/sadbundle/166345…2/images/lentintet.png could save 1.5KiB (44% reduction).
Losslessly compressing https://static.foodgawker.com/wp-content/themes/Fo…/img/addthis-blank.gif could save 1,011B (91% reduction).
Losslessly compressing https://static.foodgawker.com/wp-content/themes/Fo…-bar-texture.jpg?ver=4 could save 908B (73% reduction).
Losslessly compressing https://static.foodgawker.com/wp-content/themes/Fo…oter-texture.jpg?ver=4 could save 908B (65% reduction).
Losslessly compressing https://static.foodgawker.com/wp-content/themes/Fo…epeat_6-7-13.jpg?ver=4 could save 904B (25% reduction).
Losslessly compressing https://static.foodgawker.com/wp-content/themes/Fo…rd-hover-top.png?ver=4 could save 893B (88% reduction).
Losslessly compressing https://static.foodgawker.com/wp-content/themes/Fo…rd-hover-btm.png?ver=4 could save 831B (88% reduction).

priority - 14 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking script resources and 1 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://static.foodgawker.com/wp-content/cfconcat-…065ac859f.js?ver=4.2.2

Optimize CSS Delivery of the following:

https://static.foodgawker.com/wp-content/cfconcat-…27b7b62d.css?ver=4.2.2

priority - 3 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://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://www.googletagservices.com/tag/js/gpt_mobile.js (15 minutes)
https://pagead2.googlesyndication.com/pagead/expan…ed.js?source=safeframe (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/show_ads.js (60 minutes)
https://ssl.google-analytics.com/ga.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 3 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 26.7KiB (25% reduction).

Minifying https://static.foodgawker.com/wp-content/cfconcat-…065ac859f.js?ver=4.2.2 could save 26.7KiB (25% reduction) after compression.

foodgawker.com Desktop Resources

Total Resources120
Number of Hosts21
Static Resources77
JavaScript Resources32
CSS Resources2

foodgawker.com Desktop Resource Breakdown

foodgawker.com mobile page speed rank

Last tested: 2016-07-11


Mobile Speed Bad
61/100

foodgawker.com Mobile Speed Test Quick Summary


priority - 56 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking script resources and 1 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://static.foodgawker.com/wp-content/cfconcat-…065ac859f.js?ver=4.2.2

Optimize CSS Delivery of the following:

https://static.foodgawker.com/wp-content/cfconcat-…27b7b62d.css?ver=4.2.2

priority - 5 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 46.6KiB (33% reduction).

Losslessly compressing https://tpc.googlesyndication.com/simgad/13545383525133675107 could save 30.9KiB (30% reduction).
Losslessly compressing https://static.foodgawker.com/wp-content/themes/Fo…etina_6-7-13.jpg?ver=4 could save 8.8KiB (40% reduction).
Losslessly compressing https://static.foodgawker.com/wp-content/themes/Fo…-sm_6-7-13.png?ver=2.3 could save 1.5KiB (49% reduction).
Losslessly compressing https://static.foodgawker.com/wp-content/themes/Fo…/img/addthis-blank.gif could save 1,011B (91% reduction).
Losslessly compressing https://static.foodgawker.com/wp-content/themes/Fo…-bar-texture.jpg?ver=4 could save 908B (73% reduction).
Losslessly compressing https://static.foodgawker.com/wp-content/themes/Fo…oter-texture.jpg?ver=4 could save 908B (65% reduction).
Losslessly compressing https://static.foodgawker.com/wp-content/themes/Fo…epeat_6-7-13.jpg?ver=4 could save 904B (25% reduction).
Losslessly compressing https://static.foodgawker.com/wp-content/themes/Fo…rd-hover-top.png?ver=4 could save 893B (88% reduction).
Losslessly compressing https://static.foodgawker.com/wp-content/themes/Fo…rd-hover-btm.png?ver=4 could save 831B (88% reduction).

priority - 4 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://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://www.googletagservices.com/tag/js/gpt_mobile.js (15 minutes)
https://pagead2.googlesyndication.com/pagead/expan…ed.js?source=safeframe (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/show_ads.js (60 minutes)
https://ssl.google-analytics.com/ga.js (2 hours)

priority - 3 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 26.7KiB (25% reduction).

Minifying https://static.foodgawker.com/wp-content/cfconcat-…065ac859f.js?ver=4.2.2 could save 26.7KiB (25% reduction) after compression.

foodgawker.com Mobile Resources

Total Resources95
Number of Hosts20
Static Resources57
JavaScript Resources23
CSS Resources1

foodgawker.com Mobile Resource Breakdown

foodgawker.com mobile page usability

Last tested: 2016-07-11


Mobile Usability Good
99/100

foodgawker.com Mobile Usability Test Quick Summary


priority - 0 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="/advertise/" class="gv-advert-link">advertisement</a> and 1 others are close to other tap targets.
The tap target <div id="abgcp" class="abgcp">AdChoices</div> is close to 1 other tap targets.
The tap target <div id="abgcp" class="abgcp">AdChoices</div> is close to 1 other tap targets.

foodgawker.com Mobile Resources

Total Resources95
Number of Hosts20
Static Resources57
JavaScript Resources23
CSS Resources1

foodgawker.com Mobile Resource Breakdown

foodgawker.com similar domains

Similar domains:
www.foodgawker.com
www.foodgawker.net
www.foodgawker.org
www.foodgawker.info
www.foodgawker.biz
www.foodgawker.us
www.foodgawker.mobi
www.oodgawker.com
www.foodgawker.com
www.coodgawker.com
www.fcoodgawker.com
www.cfoodgawker.com
www.doodgawker.com
www.fdoodgawker.com
www.dfoodgawker.com
www.roodgawker.com
www.froodgawker.com
www.rfoodgawker.com
www.toodgawker.com
www.ftoodgawker.com
www.tfoodgawker.com
www.goodgawker.com
www.fgoodgawker.com
www.gfoodgawker.com
www.voodgawker.com
www.fvoodgawker.com
www.vfoodgawker.com
www.fodgawker.com
www.fiodgawker.com
www.foiodgawker.com
www.fioodgawker.com
www.fkodgawker.com
www.fokodgawker.com
www.fkoodgawker.com
www.flodgawker.com
www.folodgawker.com
www.floodgawker.com
www.fpodgawker.com
www.fopodgawker.com
www.fpoodgawker.com
www.foidgawker.com
www.fooidgawker.com
www.fokdgawker.com
www.fookdgawker.com
www.foldgawker.com
www.fooldgawker.com
www.fopdgawker.com
www.foopdgawker.com
www.foogawker.com
www.fooxgawker.com
www.foodxgawker.com
www.fooxdgawker.com
www.foosgawker.com
www.foodsgawker.com
www.foosdgawker.com
www.fooegawker.com
www.foodegawker.com
www.fooedgawker.com
www.foorgawker.com
www.foodrgawker.com
www.foordgawker.com
www.foofgawker.com
www.foodfgawker.com
www.foofdgawker.com
www.foocgawker.com
www.foodcgawker.com
www.foocdgawker.com
www.foodawker.com
www.foodfawker.com
www.foodgfawker.com
www.foodvawker.com
www.foodgvawker.com
www.foodvgawker.com
www.foodtawker.com
www.foodgtawker.com
www.foodtgawker.com
www.foodbawker.com
www.foodgbawker.com
www.foodbgawker.com
www.foodyawker.com
www.foodgyawker.com
www.foodygawker.com
www.foodhawker.com
www.foodghawker.com
www.foodhgawker.com
www.foodgwker.com
www.foodgqwker.com
www.foodgaqwker.com
www.foodgqawker.com
www.foodgwwker.com
www.foodgawwker.com
www.foodgwawker.com
www.foodgswker.com
www.foodgaswker.com
www.foodgsawker.com
www.foodgzwker.com
www.foodgazwker.com
www.foodgzawker.com
www.foodgaker.com
www.foodgaqker.com
www.foodgawqker.com
www.foodgaaker.com
www.foodgawaker.com
www.foodgaawker.com
www.foodgasker.com
www.foodgawsker.com
www.foodgaeker.com
www.foodgaweker.com
www.foodgaewker.com
www.foodgawer.com
www.foodgawjer.com
www.foodgawkjer.com
www.foodgawjker.com
www.foodgawier.com
www.foodgawkier.com
www.foodgawiker.com
www.foodgawmer.com
www.foodgawkmer.com
www.foodgawmker.com
www.foodgawler.com
www.foodgawkler.com
www.foodgawlker.com
www.foodgawoer.com
www.foodgawkoer.com
www.foodgawoker.com
www.foodgawkr.com
www.foodgawkwr.com
www.foodgawkewr.com
www.foodgawkwer.com
www.foodgawksr.com
www.foodgawkesr.com
www.foodgawkser.com
www.foodgawkdr.com
www.foodgawkedr.com
www.foodgawkder.com
www.foodgawkrr.com
www.foodgawkerr.com
www.foodgawkrer.com
www.foodgawke.com
www.foodgawkee.com
www.foodgawkere.com
www.foodgawkeer.com
www.foodgawked.com
www.foodgawkerd.com
www.foodgawkef.com
www.foodgawkerf.com
www.foodgawkefr.com
www.foodgawket.com
www.foodgawkert.com
www.foodgawketr.com
www.foodgawker.con

foodgawker.com 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.


foodgawker.com 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.