Fish.audio Test Results
Fish.audio Mobile Performance: 40/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce unused CSS
Est savings of 27 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Avoid an excessive DOM size
3,685 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Reduce JavaScript execution time
2.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Largest Contentful Paint element
19,910 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Eliminate render-blocking resources
Est savings of 290 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Minimize main-thread work
4.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Avoid multiple page redirects
Est savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Avoid serving legacy JavaScript to modern browsers
Est savings of 32 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
Reduce unused JavaScript
Est savings of 312 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Avoid enormous network payloads
Total size was 3,707 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Serve static assets with an efficient cache policy
79 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Serve images in next-gen formats
Est savings of 73 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Properly size images
Est savings of 20 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Document request latency
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Improve image delivery
Est savings of 60 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about forced reflow and its mitigations.
Optimize DOM size
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size.
Legacy JavaScript
Est savings of 102 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
Duplicated JavaScript
Est savings of 12 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Use efficient cache lifetimes
Est savings of 5,519 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Render blocking requests
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Max Potential First Input Delay
730 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Time to Interactive
19.9 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Fish.audio Mobile SEO: 100/100
Quick overview:
Fish.audio Mobile Best Practices: 83/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 about source maps.
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 served over 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 about HTTPS.
Fish.audio Mobile Accessibility: 77/100
Quick overview:
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[aria-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
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.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
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 about the viewport meta tag.
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 about heading order.
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 how to provide sufficient color contrast.
Similar sites
Similar tests
www.fish.com
www.fish.net
www.fish.org
www.fish.info
www.fish.biz
www.fish.us
www.fish.mobi
www.ish.audio
www.fish.audio
www.cish.audio
www.fcish.audio
www.cfish.audio
www.dish.audio
www.fdish.audio
www.dfish.audio
www.rish.audio
www.frish.audio
www.rfish.audio
www.tish.audio
www.ftish.audio
www.tfish.audio
www.gish.audio
www.fgish.audio
www.gfish.audio
www.vish.audio
www.fvish.audio
www.vfish.audio
www.fsh.audio
www.fush.audio
www.fiush.audio
www.fuish.audio
www.fjsh.audio
www.fijsh.audio
www.fjish.audio
www.fksh.audio
www.fiksh.audio
www.fkish.audio
www.fosh.audio
www.fiosh.audio
www.foish.audio
www.fih.audio
www.fiwh.audio
www.fiswh.audio
www.fiwsh.audio
www.fieh.audio
www.fiseh.audio
www.fiesh.audio
www.fidh.audio
www.fisdh.audio
www.fidsh.audio
www.fizh.audio
www.fiszh.audio
www.fizsh.audio
www.fixh.audio
www.fisxh.audio
www.fixsh.audio
www.fiah.audio
www.fisah.audio
www.fiash.audio
www.fis.audio
www.fisb.audio
www.fishb.audio
www.fisbh.audio
www.fisg.audio
www.fishg.audio
www.fisgh.audio
www.fisy.audio
www.fishy.audio
www.fisyh.audio
www.fisu.audio
www.fishu.audio
www.fisuh.audio
www.fisj.audio
www.fishj.audio
www.fisjh.audio
www.fisn.audio
www.fishn.audio
www.fisnh.audio
www.fish.net
www.fish.org
www.fish.info
www.fish.biz
www.fish.us
www.fish.mobi
www.ish.audio
www.fish.audio
www.cish.audio
www.fcish.audio
www.cfish.audio
www.dish.audio
www.fdish.audio
www.dfish.audio
www.rish.audio
www.frish.audio
www.rfish.audio
www.tish.audio
www.ftish.audio
www.tfish.audio
www.gish.audio
www.fgish.audio
www.gfish.audio
www.vish.audio
www.fvish.audio
www.vfish.audio
www.fsh.audio
www.fush.audio
www.fiush.audio
www.fuish.audio
www.fjsh.audio
www.fijsh.audio
www.fjish.audio
www.fksh.audio
www.fiksh.audio
www.fkish.audio
www.fosh.audio
www.fiosh.audio
www.foish.audio
www.fih.audio
www.fiwh.audio
www.fiswh.audio
www.fiwsh.audio
www.fieh.audio
www.fiseh.audio
www.fiesh.audio
www.fidh.audio
www.fisdh.audio
www.fidsh.audio
www.fizh.audio
www.fiszh.audio
www.fizsh.audio
www.fixh.audio
www.fisxh.audio
www.fixsh.audio
www.fiah.audio
www.fisah.audio
www.fiash.audio
www.fis.audio
www.fisb.audio
www.fishb.audio
www.fisbh.audio
www.fisg.audio
www.fishg.audio
www.fisgh.audio
www.fisy.audio
www.fishy.audio
www.fisyh.audio
www.fisu.audio
www.fishu.audio
www.fisuh.audio
www.fisj.audio
www.fishj.audio
www.fisjh.audio
www.fisn.audio
www.fishn.audio
www.fisnh.audio