Feedly.com Site Title

Stay ahead of the curve with Feedly AI

Feedly.com Meta Description

Welcome to Feedly — the platform where businesses and curious minds stay ahead of the curve! We're passionate about helping teams track competitors, discover new trends, and research emerging security threats. Feedly AI is a collection of machine learning models that automatically collect, analyze, and help you share actionable insights from millions of sources in real-time.

Feedly.com Test Results

Feedly.com Mobile Performance: 8/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript. Potential savings of 1,083 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Use video formats for animated content. Potential savings of 1,056 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more
Properly size images. Potential savings of 1,109 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Eliminate render-blocking resources. Potential savings of 4,350 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Remove unused CSS. Potential savings of 725 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Serve images in next-gen formats. Potential savings of 268 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Minimize main-thread work
34.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,260 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Avoid an excessive DOM size
3,811 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Reduce JavaScript execution time
17.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid enormous network payloads
Total size was 6,316 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Serve static assets with an efficient cache policy
30 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Keep request counts low and transfer sizes small
49 requests • 6,316 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid large layout shifts
2 elements found
These DOM elements contribute most to the CLS of the page.
Avoid long main-thread tasks
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid chaining critical requests
3 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Feedly.com Mobile SEO: 100/100
Quick overview:

Feedly.com Mobile Best Practices: 85/100
Quick overview:
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
Feedly.com Mobile Progressive Web App: 21/100
Quick overview:
PWA Optimized
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Installable
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Page load is not fast enough on mobile networks
Interactive at 29.4 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
Feedly.com Mobile Accessibility: 88/100
Quick overview:
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Similar sites
Similar tests
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
Last Tested: