Fredfood.Org - Info fredfood.org

fredfood.org receives about 25 unique visitors and 25 (1.00 per visitor) page views per day which should earn about $0.11/day from advertising revenue. Estimated site value is $46.59. According to Alexa Traffic Rank fredfood.org is ranked number 5,787,317 in the world and 5.0E-6% of global Internet users visit it. Site is hosted in Mountain View, CA, 94043, United States and links to network IP address 23.236.62.147. This server doesn't support HTTPS and doesn't support HTTP/2.

About - fredfood.org

How popular is fredfood.org?

Daily Unique Visitors:
25
Monthly Unique Visitors:
750
Daily Pageviews:
25 (1.00 per visitor)
Alexa Rank:
5,787,317 visit alexa
Alexa Reach:
5.0E-6% (Percent of global Internet users)
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush fredfood.org
Domain:
  fredfood.org
Rank:
  1,021,046
Organic Keywords:
  745
Organic Traffic:
  518
Organic Cost:
  $147.00
Adwords Keywords:
  3
Adwords Traffic:
  25
Adwords Cost:
  $4.00

Data

Domain Authority:
  40
Page Authority:
  49
MozRank:
  5

Backlinks Report

Total Sites Linking In (Alexa):
38
Total Backlinks:
  262
Follow Links:
  210
Nofollow Links:
  52
Referring Domains:
  81
Referring IPs:
  93

How socially engaged is fredfood.org?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  400
Buffer:
  1
Pins:
  0

How much fredfood.org can earn?

Daily Revenue:
$0.11
Monthly Revenue:
$3.30
Yearly Revenue:
$40.15
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do fredfood.org lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is fredfood.org worth?

Website Value:
$46.59

Where is fredfood.org hosted?

Server location
Server IP:
23.236.62.147
ASN:
AS15169 
ISP:
Google Inc. 
Server Location:
Mountain View
CA
94043
United States
 

Other sites hosted on 23.236.62.147

How fast does fredfood.org load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights)

Suggestions Summary

Optimize images

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

Optimize the following images to reduce their size by 215.4KiB (29% reduction).

Compressing https://static.wixstatic.com/media/fe7c63d6306ec3f076aabdef5a19bfaf.jpg/v1/fill/w_845,h_564,al_c,q_85,usm_0.66_1.00_0.01/fe7c63d6306ec3f076aabdef5a19bfaf.jpg could save 45.8KiB (22% reduction).
Compressing https://static.wixstatic.com/media/db3c73b799674733bbcc01e12a2ab7e4.jpg/v1/fill/w_942,h_564,al_c,q_85,usm_0.66_1.00_0.01/db3c73b799674733bbcc01e12a2ab7e4.jpg could save 36.7KiB (24% reduction).
Compressing https://static.wixstatic.com/media/c3c730_7c7650dd2a7e4231aaac2b84c44b7ef0~mv2.jpg/v1/fill/w_840,h_215,al_c,q_80,usm_0.66_1.00_0.01/c3c730_7c7650dd2a7e4231aaac2b84c44b7ef0~mv2.jpg could save 21.9KiB (35% reduction).
Compressing https://static.wixstatic.com/media/c3c730_56d35e***16dd404794974f29631950e3~mv2.jpg/v1/fill/w_840,h_215,al_c,q_80,usm_0.66_1.00_0.01/c3c730_56d35e***16dd404794974f29631950e3~mv2.jpg could save 20.9KiB (35% reduction).
Compressing https://static.wixstatic.com/media/c3c730_e897f8ccf19b49ff816a13736e1f8ab3~mv2.jpg/v1/fill/w_840,h_215,al_c,q_80,usm_0.66_1.00_0.01/c3c730_e897f8ccf19b49ff816a13736e1f8ab3~mv2.jpg could save 20.3KiB (35% reduction).
Compressing https://static.wixstatic.com/media/c3c730_f438e28b02be4f64b4c6a7fa2e94ba7d~mv2.jpg/v1/fill/w_840,h_215,al_c,q_80,usm_0.66_1.00_0.01/c3c730_f438e28b02be4f64b4c6a7fa2e94ba7d~mv2.jpg could save 19.5KiB (33% reduction).
Compressing https://static.wixstatic.com/media/c3c730_76f8ea95a62142f9b1a7a9207aaee40c~mv2.jpg/v1/fill/w_840,h_215,al_c,q_80,usm_0.66_1.00_0.01/c3c730_76f8ea95a62142f9b1a7a9207aaee40c~mv2.jpg could save 14.3KiB (35% reduction).
Compressing https://static.wixstatic.com/media/c3c730_de2f82b5d8a041a5808557320ce61b55~mv2.jpg/v1/fill/w_840,h_215,al_c,q_80,usm_0.66_1.00_0.01/c3c730_de2f82b5d8a041a5808557320ce61b55~mv2.jpg could save 11.4KiB (46% reduction).
Compressing https://static.wixstatic.com/media/b91e20a5e6bbc5d0862d5d76ddff73a5.jpg/v1/fill/w_322,h_215,al_c,q_80,usm_0.66_1.00_0.01/b91e20a5e6bbc5d0862d5d76ddff73a5.jpg could save 7KiB (27% reduction).
Compressing https://static.wixstatic.com/media/c3c730_f1c5817a3c324126b5d18da12c68fe78.png/v1/fill/w_346,h_149,al_c,lg_1/c3c730_f1c5817a3c324126b5d18da12c68fe78.png could save 5.6KiB (16% reduction).
Compressing https://static.wixstatic.com/media/b1cd13f9d4dfb1450bbb325285106177.png/v1/fill/w_92,h_92,al_c,usm_0.66_1.00_0.01/b1cd13f9d4dfb1450bbb325285106177.png could save 3.4KiB (65% reduction).
Compressing https://static.wixstatic.com/media/806f5f56d9a7b8849f2f2ea71ff5c0cc.png/v1/fill/w_92,h_92,al_c,usm_0.66_1.00_0.01/806f5f56d9a7b8849f2f2ea71ff5c0cc.png could save 2.9KiB (37% reduction).
Compressing https://static.wixstatic.com/media/c090bd2***d424abf8f035befe86158de.png/v1/fill/w_92,h_92,al_c,usm_0.66_1.00_0.01/c090bd2***d424abf8f035befe86158de.png could save 2KiB (44% reduction).
Compressing https://static.wixstatic.com/media/01113281ebb7dfb57a8dc2a02eb1cb92.png/v1/fill/w_92,h_92,al_c,usm_0.66_1.00_0.01/01113281ebb7dfb57a8dc2a02eb1cb92.png could save 1.7KiB (40% reduction).
Compressing https://static.wixstatic.com/media/a1b09fe8b7f04378a9fe076748ad4a6a.png/v1/fill/w_92,h_92,al_c,usm_0.66_1.00_0.01/a1b09fe8b7f04378a9fe076748ad4a6a.png could save 1.2KiB (26% reduction).
Compressing http://static.parastorage.com/services/skins/2.1229.63/images/wysiwyg/core/themes/base/bevel_300.png could save 770B (78% reduction).

Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

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

Your page has 2 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.Optimize CSS Delivery of the following:

https://static.parastorage.com/services/santa-resources/resources/viewer/user-site-fonts/v3/languages.css
http://fonts.googleapis.com/css?family=Anton:n,b,i,bi|Basic:n,b,i,bi|Caudex:n,b,i,bi|Chelsea+Market:n,b,i,bi|Corben:n,b,i,bi|EB+Garamond:n,b,i,bi|Enriqueta:n,b,i,bi|Forum:n,b,i,bi|Fredericka+the+Great:n,b,i,bi|Jockey+One:n,b,i,bi|Josefin+Slab:n,b,i,bi|Jura:n,b,i,bi|Kelly+Slab:n,b,i,bi|Marck+Script:n,b,i,bi|Lobster:n,b,i,bi|Mr+De+Haviland:n,b,i,bi|Niconne:n,b,i,bi|Noticia+Text:n,b,i,bi|Overlock:n,b,i,bi|Patrick+Hand:n,b,i,bi|Play:n,b,i,bi|Sarina:n,b,i,bi|Signika:n,b,i,bi|Spinnaker:n,b,i,bi|Monoton:n,b,i,bi|Sacramento:n,b,i,bi|Cookie:n,b,i,bi|Raleway:n,b,i,bi|Open+Sans+Condensed:300:n,b,i,bi|Amatic+SC:n,b,i,bi|Cinzel:n,b,i,bi|Sail:n,b,i,bi|Playfair+Display:n,b,i,bi|Libre+Baskerville:n,b,i,bi|&subset=latin-ext,cyrillic,japanese,korean,arabic,hebrew,latin

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://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-P6NTJRP (15 minutes)
http://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/178714015878685?v=2.7.16 (20 minutes)
http://www.google-***ytics.com/***ytics.js (2 hours)

Configure the viewport

Your page specifies a fixed-width mobile viewport. Consider using a responsive viewport to allow your page to render properly on all devices.

Configuring a viewport specifying width=device-width instead of width=320 will allow your page to adapt for devices of various widths. This may require additional work if the styling on your page relies on a fixed-width layout.

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="https://www.yo…?v=dxzeyB3D5eY" class="ytp-watermark…ix-sessionlink"></a> is close to 1 other tap targets.
The tap target <a href="tel:5403717***" class="auto-generated-link">(540) 371-7***</a> and 1 others are close to other tap targets.
The tap target <a href="http://www.fre…privacy-policy">Privacy Policy</a> and 2 others are close to other tap targets.

Minify JavaScript

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

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

Minifying https://static.parastorage.com/services/third-party/jquery-easing/1.3/jquery.easing.min.js could save 998B (53% reduction) after compression.
Minifying https://static.parastorage.com/services/santa/1.2335.5/galleries/lib/js/utils.js could save 915B (20% reduction) after compression.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Enable compression
You have compression enabled. Learn more about enabling compression.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Download optimized image, JavaScript, and CSS resources for this page.

Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

SSL Checker - SSL Certificate Verify

fredfood.org does not support HTTPS
loader
Verifying SSL Support. Please wait...

Verify HTTP/2 Support

fredfood.org does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

Site Categories (dmoz)

Currently Not Available

What sites are related to fredfood.org?

Http Header

HTTP/1.1 200 OK
Cache-Control: no-cache
Content-Language: en
Content-Type: text/html;ch***t=utf-8
Date: Tue, 03 Oct 2017 08:51:45 GMT
ETag: 72311a044f22ddfb93029f16000e8f14
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Expires: -1
Pragma: no-cache
Server: Pepyaka/1.11.3
Set-Cookie: hs=1819610354;Path=/;Domain=www.fredfood.org;HttpOnly
Set-Cookie: svSession=e9***44247e4108228c83d0725a9e945e15cc6e3905c429dd48b8d9b19416c49227c238f556c03763f5f9f2a8158df2bd1e60994d53964e647acf431e4f798bcdc1321b5c68ca14bd918edd6e36c2ad64f6a490e2c8***18adf8b7adb17791e35b;Path=/;Domain=www.fredfood.org;Expires=Mon, 03-Oct-2022 08:51:44 GMT
Set-Cookie: hs=1819610354;Path=/;Domain=www.fredfood.org;HttpOnly
Set-Cookie: svSession=e9***44247e4108228c83d0725a9e945e15cc6e3905c429dd48b8d9b19416c49227c238f556c03763f5f9f2a8158df2bd1e60994d53964e647acf431e4f798bcdc1321b5c68ca14bd918edd6e36c2ad64f6a490e2c8***18adf8b7adb17791e35b;Path=/;Domain=www.fredfood.org;Expires=Mon, 03-Oct-2022 08:51:44 GMT
Vary: User-Agent
X-Seen-By: BTnOiHJfychu5uLth4+AW0wRbsdIWDN0tP6JZFZxPe0=,1wy2ILu/S4rlWT/R4rqCra8SNXPY5sBEJ7bEwi/yTUg=,LwsIp90Tma5sliyMxJYVEu+fvIZbVasaJ0BlEb1vZtI=,I2ZOrNA1LIowGTY6Ll7mx8gcgo3Y4fTjdcQ2s8gVRU4=,1wy2ILu/S4rlWT/R4rqCrSXwA8+Y/z9zKrsNB9o7heQ=,Tw2AanFDQ+Wwo8***k6ZL7rHKeAJXtkPxqn+uc4aMlODHc3xfoVLyHwPjrGWSg2P8KjCWKapddFlOEEDxcGowaw==
X-Wix-Renderer-Server: app-jvm-12-181.96.wixprod.net
X-Wix-Request-Id: 1507020705.1012845840847142713
Connection: Close

DNS Lookup

Type Ip Target TTL
TXT 3600
MX aspmx3.googlemail.com 3600
MX aspmx.l.google.com 3600
MX alt1.aspmx.l.google.com 3600
MX alt2.aspmx.l.google.com 3600
MX aspmx2.googlemail.com 3600
SOA 3600
Mname ns14.wixdns.net
Rname support.wix.com
Serial Number 2015010528
Refresh 10800
Retry 3600
Expire 604800
Minimum TTL 0
A 23.236.62.147 1800
NS ns15.wixdns.net 3600
NS ns14.wixdns.net 3600

Whois Lookup

Domain Created:
2005-01-07
Domain Age:
12 years 8 months 27 days  
WhoIs:
 

whois lookup at whois.pir.org...
Domain Name: FREDFOOD.ORG
Registry Domain ID: D105538343-LROR
Registrar WHOIS Server:
Registrar URL: http://www.networksolutions.com
Updated Date: 2015-03-26T13:24:29Z
Creation Date: 2005-01-07T20:59:36Z
Registry Expiry Date: 2019-01-07T20:59:36Z
Registrar Registration Expiration Date:
Registrar: Network Solutions, LLC
Registrar IANA ID: 2
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: C158153914-LROR
Registrant Name: Atiye Chappell
Registrant Organization: Fredericksburg Area Food Bank
Registrant Street: 3631 Lee Hill Dr
Registrant City: Fredericksburg
Registrant State/Province: VA
Registrant Postal Code: 22408
Registrant Country: US
Registrant Phone: +1.5403717***
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: email
Registry Admin ID: C158153914-LROR
Admin Name: Atiye Chappell
Admin Organization: Fredericksburg Area Food Bank
Admin Street: 3631 Lee Hill Dr
Admin City: Fredericksburg
Admin State/Province: VA
Admin Postal Code: 22408
Admin Country: US
Admin Phone: +1.5403717***
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: email
Registry Tech ID: C158153914-LROR
Tech Name: Atiye Chappell
Tech Organization: Fredericksburg Area Food Bank
Tech Street: 3631 Lee Hill Dr
Tech City: Fredericksburg
Tech State/Province: VA
Tech Postal Code: 22408
Tech Country: US
Tech Phone: +1.5403717***
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: email
Name Server: NS14.WIXDNS.NET
Name Server: NS15.WIXDNS.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2017-10-03T08:50:56Z <<<

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

Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no cir***stances will you use this data to: (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
Last update was 46 days ago
loader
This can take up to 60 seconds. Please wait...

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
fredfood.org widget