Apy.vision Site Title
DeFi liquidity pool analytics yield farming rewards tracker
Apy.vision Meta Description
Find the most profitable liquidity pools, calculate liquidity pool performance, impermanent losses and track yield farming rewards in one place
Apy.vision Test Results
Apy.vision Mobile Performance: 15/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Preload key requests. Potential savings of 5,130 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Remove unused JavaScript. Potential savings of 834 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Eliminate render-blocking resources. Potential savings of 4,710 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 761 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 180 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.
Properly size images. Potential savings of 164 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Defer offscreen images. Potential savings of 53 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Minimize main-thread work
7.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Serve static assets with an efficient cache policy
6 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Reduce JavaScript execution time
2.7 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 3,406 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Avoid long main-thread tasks
8 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Avoid large layout shifts
2 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests
5 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.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Keep request counts low and transfer sizes small
19 requests • 3,406 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Apy.vision Mobile SEO: 77/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more. Description text is empty.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
Apy.vision Mobile Best Practices: 79/100
Quick overview:
General
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more.
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Trust and Safety
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
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.
Apy.vision Mobile Progressive Web App: 36/100
Quick overview:
PWA Optimized
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.
Content is not sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more. The viewport size of 376px does not match the window size of 360px.
Fast and reliable
Page load is not fast enough on mobile networks
Interactive at 16.1 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.
`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. The start_url did respond, but not via a service worker.
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.
Installable
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.
Apy.vision Mobile Accessibility: 71/100
Quick overview:
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. 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.apy.com
www.apy.net
www.apy.org
www.apy.info
www.apy.biz
www.apy.us
www.apy.mobi
www.py.vision
www.apy.vision
www.qpy.vision
www.aqpy.vision
www.qapy.vision
www.wpy.vision
www.awpy.vision
www.wapy.vision
www.spy.vision
www.aspy.vision
www.sapy.vision
www.zpy.vision
www.azpy.vision
www.zapy.vision
www.ay.vision
www.aoy.vision
www.apoy.vision
www.aopy.vision
www.aly.vision
www.aply.vision
www.alpy.vision
www.ap.vision
www.apt.vision
www.apyt.vision
www.apty.vision
www.apg.vision
www.apyg.vision
www.apgy.vision
www.aph.vision
www.apyh.vision
www.aphy.vision
www.apu.vision
www.apyu.vision
www.apuy.vision
www.apy.net
www.apy.org
www.apy.info
www.apy.biz
www.apy.us
www.apy.mobi
www.py.vision
www.apy.vision
www.qpy.vision
www.aqpy.vision
www.qapy.vision
www.wpy.vision
www.awpy.vision
www.wapy.vision
www.spy.vision
www.aspy.vision
www.sapy.vision
www.zpy.vision
www.azpy.vision
www.zapy.vision
www.ay.vision
www.aoy.vision
www.apoy.vision
www.aopy.vision
www.aly.vision
www.aply.vision
www.alpy.vision
www.ap.vision
www.apt.vision
www.apyt.vision
www.apty.vision
www.apg.vision
www.apyg.vision
www.apgy.vision
www.aph.vision
www.apyh.vision
www.aphy.vision
www.apu.vision
www.apyu.vision
www.apuy.vision