FEEDLY.COM feedly


feedly.com website information.

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

feedly.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 feedly.com domain:

  • anna.ns.cloudflare.com
  • sid.ns.cloudflare.com

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

According to Alexa traffic rank the highest website feedly.com position was 167 (in the world). The lowest Alexa rank position was 514. Now website feedly.com ranked in Alexa database as number 476 (in the world).

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

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

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

Weekly Rank Report

DateRankChange
Apr-23-2018 476-77
Apr-22-2018 3991
Apr-21-2018 400-7
Apr-20-2018 393-2
Apr-19-2018 391-13
Apr-18-2018 37891
Apr-17-2018 469-20

Advertisement

feedly.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.


feedly.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: feedly.com
Registry Domain ID: 1479671101_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.gandi.net
Registrar URL: http://www.gandi.net
Updated Date: 2014-10-10T05:08:14Z
Creation Date: 2008-05-25T10:15:38Z
Registrar Registration Expiration Date: 2019-05-25T10:15:38Z
Registrar: GANDI SAS
Registrar IANA ID: 81
Registrar Abuse Contact Email: abuse@support.gandi.net
Registrar Abuse Contact Phone: +33.170377661
Reseller:
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status:
Domain Status:
Domain Status:
Domain Status:
Registry Registrant ID:
Registrant Name: Edwin Khodabakchian
Registrant Organization: DevHD Inc.
Registrant Street: 41 McCormick Lane
Registrant City: Atherthon
Registrant State/Province:
Registrant Postal Code: 94027
Registrant Country: US
Registrant Phone: +1.6505048118
Registrant Phone Ext:
Registrant Fax: +1.6508380708
Registrant Fax Ext:
Registrant Email: 43a5d71e4b5c56a61f906af9b5ad334f-1145542@contact.gandi.net
Registry Admin ID:
Admin Name: Edwin Khodabakchian
Admin Organization: Edwin Khodabakchian (edwink@devhd.com)
Admin Street: 41 McCormick Lane
Admin City: Atherton
Admin State/Province: California
Admin Postal Code: 94027
Admin Country: US
Admin Phone: +1.6505048118
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: cbb08a68aeef18bf88b7707d2075d0d7-853237@contact.gandi.net
Registry Tech ID:
Tech Name: Olivier Devaux
Tech Organization:
Tech Street: Obfuscated whois Gandi-63-65 boulevard Massena
Tech City: Obfuscated whois Gandi-Paris
Tech State/Province:
Tech Postal Code: 75013
Tech Country: FR
Tech Phone: +33.170377666
Tech Phone Ext:
Tech Fax: +33.143730576
Tech Fax Ext:
Tech Email: 5b3bb5d9b314f8e619da2688e23b3de7-400673@contact.gandi.net
Name Server: ANNA.NS.CLOUDFLARE.COM
Name Server: SID.NS.CLOUDFLARE.COM
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
DNSSEC: Unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2015-05-11T06:27:03Z

feedly.com server information

Servers Location

feedly.com desktop page speed rank

Last tested: 2016-06-12


Desktop Speed Medium
74/100

feedly.com Desktop Speed Test Quick Summary


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

Your page has 2 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:

http://s3.feedly.com/web/30.0.1177/js/web-main-bundle.js
http://s3.feedly.com/web/30.0.1177/js/web-templates-bundle.js

Optimize CSS Delivery of the following:

http://s3.feedly.com/web/30.0.1177/fx/feedly-fx.css

priority - 13 Optimize images

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

Optimize the following images to reduce their size by 126.4KiB (25% reduction).

Losslessly compressing http://s3.feedly.com/production/head/images/landing/screenshot-web.jpg could save 42.9KiB (13% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/landing/photo-tina-bw@2x.png could save 7.1KiB (36% reduction).
Losslessly compressing http://s3.feedly.com/img/oops.png could save 6.3KiB (65% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/landing/photo-brad-bw@2x.png could save 6.3KiB (37% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/landin…page-brandlogos-v2.png could save 5.8KiB (48% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/landing/photo-zendesk-bw@2x.png could save 4.8KiB (26% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/feedly-logo-black.png could save 4.5KiB (62% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/icon-action-overview-6@2x.png could save 4KiB (97% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/landing/photo-caa-bw@2x.png could save 3.7KiB (29% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/landing/photo-jason-bw@2x.png could save 3.5KiB (28% reduction).
Compressing and resizing http://s3.feedly.com/img/feedly-full-black.png could save 2.9KiB (62% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/landing/photo-mit-bw@2x.png could save 2.8KiB (19% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/icon-addshortcut.png could save 2.8KiB (96% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/icon-editshortcut.png could save 2.8KiB (96% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/icon-action-customize.png could save 2.8KiB (79% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/icon-action-next.png could save 2.7KiB (88% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/icon-action-overview-4@2x.png could save 2.7KiB (94% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/icon-action-overview-0@2x.png could save 2.7KiB (95% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/icon-action-overview-100@2x.png could save 2.7KiB (95% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/icon-feedly.png could save 2.7KiB (95% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/icon-action-refresh.png could save 2.7KiB (80% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/icon-action-markasread.png could save 2.7KiB (84% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/icon-action-backtotop.png could save 2.7KiB (88% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/tab-first.png could save 1,005B (52% reduction).
Losslessly compressing http://s3.feedly.com/production/head/images/tab-second.png could save 902B (50% reduction).

priority - 2 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://apis.google.com/js/platform.js?e=PlatformE…equestNowAuthorization (30 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://s3.feedly.com/essentials/essentials_en-US.json?ck=1465681854812 (4.2 days)
http://s3.feedly.com/img/feedly-full-black.png (4.2 days)
http://s3.feedly.com/img/oops.png (4.2 days)

priority - 2 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.

None of the final above-the-fold content could be rendered even with the full HTML response.

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 997B (28% reduction).

Minifying http://feedly.com/ could save 997B (28% reduction) after compression.

feedly.com Desktop Resources

Total Resources61
Number of Hosts10
Static Resources51
JavaScript Resources7
CSS Resources2

feedly.com Desktop Resource Breakdown

feedly.com mobile page speed rank

Last tested: 2017-08-01


Mobile Speed Bad
37/100

feedly.com Mobile Speed Test Quick Summary


priority - 98 Optimize images

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

Optimize the following images to reduce their size by 957KiB (91% reduction).

Compressing and resizing https://s3.feedly.com/production/head/images/landing/screenshot-web@2x.png could save 919.7KiB (94% reduction).
Compressing https://s3.feedly.com/img/oops.png could save 5.1KiB (52% reduction).
Compressing https://s3.feedly.com/production/head/images/icon-action-overview-6@2x.png could save 3.9KiB (95% reduction).
Compressing https://s3.feedly.com/production/head/images/icon-action-customize.png could save 2.8KiB (80% reduction).
Compressing https://s3.feedly.com/production/head/images/icon-action-refresh.png could save 2.8KiB (83% reduction).
Compressing https://s3.feedly.com/production/head/images/icon-action-markasread.png could save 2.7KiB (86% reduction).
Compressing https://s3.feedly.com/production/head/images/icon-action-next.png could save 2.7KiB (89% reduction).
Compressing https://s3.feedly.com/production/head/images/icon-action-backtotop.png could save 2.7KiB (89% reduction).
Compressing https://s3.feedly.com/production/head/images/icon-…on-overview-100@2x.png could save 2.7KiB (94% reduction).
Compressing https://s3.feedly.com/production/head/images/icon-action-overview-4@2x.png could save 2.7KiB (93% reduction).
Compressing https://s3.feedly.com/production/head/images/icon-action-overview-0@2x.png could save 2.7KiB (94% reduction).
Compressing https://s3.feedly.com/production/head/images/icon-feedly.png could save 2.7KiB (94% reduction).
Compressing https://s3.feedly.com/production/head/images/landing/photo-tina-bw@2x.png could save 2.3KiB (12% reduction).
Compressing https://s3.feedly.com/production/head/images/tab-second@2x.png could save 849B (33% reduction).
Compressing https://s3.feedly.com/production/head/images/tab-first@2x.png could save 833B (32% reduction).

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

Your page has 2 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://s3.feedly.com/web/30.0.1350/js/web-main-bundle.js
https://s3.feedly.com/web/30.0.1350/js/web-templates-bundle.js

Optimize CSS Delivery of the following:

https://s3.feedly.com/web/30.0.1350/fx/feedly-fx.css

priority - 8 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.

None of the final above-the-fold content could be rendered even with the full HTML response.

priority - 5 Reduce server response time

In our test, your server responded in 0.51 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

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://js.stripe.com/v2/ (5 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://s3.feedly.com/essentials/essentials_en-US.json?ck=1501641105573 (4.2 days)
https://s3.feedly.com/img/oops.png (4.2 days)

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 (33% reduction).

Minifying https://feedly.com/ could save 1.5KiB (33% reduction) after compression.

feedly.com Mobile Resources

Total Resources40
Number of Hosts10
Static Resources26
JavaScript Resources8
CSS Resources2

feedly.com Mobile Resource Breakdown

feedly.com mobile page usability

Last tested: 2017-08-01


Mobile Usability Good
89/100

feedly.com Mobile Usability Test Quick Summary


priority - 11 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 <input id="" type="text"> is close to 1 other tap targets.

The tap target <div id="feedlyTabsHolder">Make Feedly yo…Version 30.0</div> is close to 1 other tap targets.

The tap target <a href="https://play.g…m.devhd.feedly" class="button primary loud start-now">Get Feedly for Android</a> is close to 1 other tap targets.

feedly.com Mobile Resources

Total Resources40
Number of Hosts10
Static Resources26
JavaScript Resources8
CSS Resources2

feedly.com Mobile Resource Breakdown

feedly.com similar domains

Similar domains:
www.feedly.com
www.feedly.net
www.feedly.org
www.feedly.info
www.feedly.biz
www.feedly.us
www.feedly.mobi
www.eedly.com
www.feedly.com
www.ceedly.com
www.fceedly.com
www.cfeedly.com
www.deedly.com
www.fdeedly.com
www.dfeedly.com
www.reedly.com
www.freedly.com
www.rfeedly.com
www.teedly.com
www.fteedly.com
www.tfeedly.com
www.geedly.com
www.fgeedly.com
www.gfeedly.com
www.veedly.com
www.fveedly.com
www.vfeedly.com
www.fedly.com
www.fwedly.com
www.fewedly.com
www.fweedly.com
www.fsedly.com
www.fesedly.com
www.fseedly.com
www.fdedly.com
www.fededly.com
www.fredly.com
www.feredly.com
www.fewdly.com
www.feewdly.com
www.fesdly.com
www.feesdly.com
www.feddly.com
www.feeddly.com
www.ferdly.com
www.feerdly.com
www.feely.com
www.feexly.com
www.feedxly.com
www.feexdly.com
www.feesly.com
www.feedsly.com
www.feeely.com
www.feedely.com
www.feeedly.com
www.feerly.com
www.feedrly.com
www.feefly.com
www.feedfly.com
www.feefdly.com
www.feecly.com
www.feedcly.com
www.feecdly.com
www.feedy.com
www.feedpy.com
www.feedlpy.com
www.feedply.com
www.feedoy.com
www.feedloy.com
www.feedoly.com
www.feedky.com
www.feedlky.com
www.feedkly.com
www.feedl.com
www.feedlt.com
www.feedlyt.com
www.feedlty.com
www.feedlg.com
www.feedlyg.com
www.feedlgy.com
www.feedlh.com
www.feedlyh.com
www.feedlhy.com
www.feedlu.com
www.feedlyu.com
www.feedluy.com
www.feedly.con

feedly.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.


feedly.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.