Read.cash Site Title
read.cash
Read.cash Test Results
Read.cash Mobile Performance: 27/100
Quick overview:
Max Potential First Input Delay
3,460 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more.
First Meaningful Paint
4.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Diagnostics
Collection of useful page vitals.
Final Screenshot
The last screenshot captured of the pageload.
1069024620638
Tasks
Lists the toplevel main thread tasks that executed during page load.
Metrics
Collects all available metrics.
Network Requests
Lists the network requests that were made during page load.
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.
Script Treemap Data
Used for treemap app
Read.cash Mobile SEO: 88/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.
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Tap targets are not sized appropriately
68% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
Read.cash 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.
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.
Includes front-end JavaScript libraries with known security vulnerabilities
5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
Read.cash Mobile PWA: 90/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.
Read.cash Mobile Accessibility: 67/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.
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 more.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. 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.read.com
www.read.net
www.read.org
www.read.info
www.read.biz
www.read.us
www.read.mobi
www.ead.cash
www.read.cash
www.eead.cash
www.reead.cash
www.eread.cash
www.dead.cash
www.rdead.cash
www.dread.cash
www.fead.cash
www.rfead.cash
www.fread.cash
www.tead.cash
www.rtead.cash
www.tread.cash
www.rad.cash
www.rwad.cash
www.rewad.cash
www.rwead.cash
www.rsad.cash
www.resad.cash
www.rsead.cash
www.rdad.cash
www.redad.cash
www.rrad.cash
www.rerad.cash
www.rread.cash
www.red.cash
www.reqd.cash
www.reaqd.cash
www.reqad.cash
www.rewd.cash
www.reawd.cash
www.resd.cash
www.reasd.cash
www.rezd.cash
www.reazd.cash
www.rezad.cash
www.rea.cash
www.reax.cash
www.readx.cash
www.reaxd.cash
www.reas.cash
www.reads.cash
www.reae.cash
www.reade.cash
www.reaed.cash
www.rear.cash
www.readr.cash
www.reard.cash
www.reaf.cash
www.readf.cash
www.reafd.cash
www.reac.cash
www.readc.cash
www.reacd.cash
www.read.net
www.read.org
www.read.info
www.read.biz
www.read.us
www.read.mobi
www.ead.cash
www.read.cash
www.eead.cash
www.reead.cash
www.eread.cash
www.dead.cash
www.rdead.cash
www.dread.cash
www.fead.cash
www.rfead.cash
www.fread.cash
www.tead.cash
www.rtead.cash
www.tread.cash
www.rad.cash
www.rwad.cash
www.rewad.cash
www.rwead.cash
www.rsad.cash
www.resad.cash
www.rsead.cash
www.rdad.cash
www.redad.cash
www.rrad.cash
www.rerad.cash
www.rread.cash
www.red.cash
www.reqd.cash
www.reaqd.cash
www.reqad.cash
www.rewd.cash
www.reawd.cash
www.resd.cash
www.reasd.cash
www.rezd.cash
www.reazd.cash
www.rezad.cash
www.rea.cash
www.reax.cash
www.readx.cash
www.reaxd.cash
www.reas.cash
www.reads.cash
www.reae.cash
www.reade.cash
www.reaed.cash
www.rear.cash
www.readr.cash
www.reard.cash
www.reaf.cash
www.readf.cash
www.reafd.cash
www.reac.cash
www.readc.cash
www.reacd.cash