Copays.org Site Title

COPAYS.ORG | Patient Advocate Foundation Co-Pay Relief

Copays.org Test Results

Copays.org Mobile Performance: 12/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Eliminate render-blocking resources. Potential savings of 7,410 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.
Enable text compression. Potential savings of 786 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Remove unused JavaScript. Potential savings of 737 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Serve images in next-gen formats. Potential savings of 397 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.
Reduce initial server response time. Root document took 1,810 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Defer offscreen images. Potential savings of 504 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Remove unused CSS. Potential savings of 171 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.
Preload Largest Contentful Paint image. Potential savings of 690 ms
Preload the image used by the LCP element in order to improve your LCP time. Learn more.
Minify CSS. Potential savings of 30 KiB
Minifying CSS files can reduce network payload sizes. Learn more.
Avoid serving legacy JavaScript to modern browsers. Potential savings of 27 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn More
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Some third-party resources can be lazy loaded with a facade
1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn more
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.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Reduce the impact of third-party code
Third-party code blocked the main thread for 990 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.
Serve static assets with an efficient cache policy
53 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
3.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
2.2 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 2,881 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Keep request counts low and transfer sizes small
80 requests • 2,881 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
User Timing marks and measures
3 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid chaining critical requests
28 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.
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

Copays.org Mobile SEO: 93/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.

Copays.org Mobile Best Practices: 73/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 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
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
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.
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
Copays.org Mobile Progressive Web App: 42/100
Quick overview:
PWA Optimized
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.
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.
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
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.
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
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. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
Copays.org Mobile Accessibility: 65/100
Quick overview:
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. 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.
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.
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 tests
www.copays.com
www.copays.net
www.copays.org
www.copays.info
www.copays.biz
www.copays.us
www.copays.mobi
www.opays.org
www.copays.org
www.xopays.org
www.cxopays.org
www.xcopays.org
www.dopays.org
www.cdopays.org
www.dcopays.org
www.fopays.org
www.cfopays.org
www.fcopays.org
www.vopays.org
www.cvopays.org
www.vcopays.org
www.cpays.org
www.cipays.org
www.coipays.org
www.ciopays.org
www.ckpays.org
www.cokpays.org
www.ckopays.org
www.clpays.org
www.colpays.org
www.clopays.org
www.cppays.org
www.coppays.org
www.cpopays.org
www.coays.org
www.cooays.org
www.copoays.org
www.coopays.org
www.colays.org
www.coplays.org
www.copys.org
www.copqys.org
www.copaqys.org
www.copqays.org
www.copwys.org
www.copawys.org
www.copways.org
www.copsys.org
www.copasys.org
www.copsays.org
www.copzys.org
www.copazys.org
www.copzays.org
www.copas.org
www.copats.org
www.copayts.org
www.copatys.org
www.copags.org
www.copaygs.org
www.copagys.org
www.copahs.org
www.copayhs.org
www.copahys.org
www.copaus.org
www.copayus.org
www.copauys.org
www.copay.org
www.copayw.org
www.copaysw.org
www.copayws.org
www.copaye.org
www.copayse.org
www.copayes.org
www.copayd.org
www.copaysd.org
www.copayds.org
www.copayz.org
www.copaysz.org
www.copayzs.org
www.copayx.org
www.copaysx.org
www.copayxs.org
www.copaya.org
www.copaysa.org
www.copayas.org
Last Tested:

This website uses cookies to ensure you get the best experience on our website. Learn more. Got it.