FEEDLY.COM Stay ahead of the curve with Feedly AI

feedly.com Website Information

Daily Unique Visits: 1,672,740

Daily Page Views: 13,381,920

Income Per Day: $13,382

Estimated Value: $14,452,560

This website is located in United States and is using following IP address 104.20.59.241. See the complete list of popular websites hosted in United States.

feedly.com is registered under .COM top-level domain. Please check other sites in .COM zone.

Website feedly.com is using the following name servers:

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

and is probably hosted by CLOUDFLARENET - Cloudflare, Inc., US. See the full list of other websites hosted by CLOUDFLARENET - Cloudflare, Inc., US.

The highest website feedly.com position in Alexa rank database was 911 and the lowest rank position was 949. Current position of feedly.com in Alexa rank database is 911.

Desktop speed score of feedly.com (52/100) is better than the results of 25.95% of other sites and shows that the page desktop performance can be improved.

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

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

Advertisement

feedly.com Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


feedly.com whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


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: 2021-02-19T01:20:00Z
Creation Date: 2008-05-25T10:15:38Z
Registry Expiry Date: 2030-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
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: ANNA.NS.CLOUDFLARE.COM
Name Server: SID.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-08-12T17:39:04Z

feedly.com server information

Servers Location

feedly.com desktop page speed rank

Last tested: 2019-12-02


Desktop Speed Bad
52/100

feedly.com Desktop Speed Test Quick Summary


priority - 79Optimize images

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

Optimize the following images to reduce their size by 769.9KiB (75% reduction).

Compressing and resizing https://s5.feedly.com/images/landing/screenshot-web@2x.png could save 760.6KiB (77% reduction).
Compressing https://s5.feedly.com/images/oops.png could save 5.1KiB (52% reduction).
Compressing https://s5.feedly.com/images/landing/photo-tina-bw@2x.png could save 2.3KiB (12% reduction).
Compressing https://s5.feedly.com/images/landing/photo-brad-bw@2x.png could save 1.9KiB (11% reduction).

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

Your page has 1 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://s5.feedly.com/web/master/boot.4a17f83fdfbbfd0b3c03.js

Optimize CSS Delivery of the following:

https://s5.feedly.com/web/master/vendors.d5e9dfb1b1fa2c30668a.css
https://s5.feedly.com/web/master/main.8cc7531cccd2635cdafc.css

priority - 2Prioritize 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 - 2Leverage 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/v3/ (5 minutes)
https://syndication.twitter.com/settings (10 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

feedly.com Desktop Resource Breakdown

Total Resources27
Number of Hosts8
Static Resources17
JavaScript Resources7
CSS Resources2

feedly.com mobile page speed rank

Last tested: 2017-08-01


Mobile Speed Bad
37/100

feedly.com Mobile Speed Test Quick Summary


priority - 98Optimize 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 - 72Eliminate 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.

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 - 8Prioritize 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 - 5Reduce server response time

priority - 3Leverage 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 - 0Minify 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 Resource Breakdown

Total Resources40
Number of Hosts10
Static Resources26
JavaScript Resources8
CSS Resources2

feedly.com mobile page usability

Last tested: 2017-08-01


Mobile Usability Good
89/100

feedly.com Mobile Usability Test Quick Summary


priority - 11Size 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 HTML validation

Warnings

Consider avoiding viewport values that prevent users from resizing documents.

Line: 1 Column: 2250 - 2350
"...0430121"/><meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1,user-scalable=no"/><scrip..."

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 computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


feedly.com TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.