Prex.app Test Results
Prex.app Mobile Performance: 54/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce unused JavaScript
Potential savings of 196 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.
Reduce JavaScript execution time
1.3 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.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Minimize main-thread work
2.2 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 serving legacy JavaScript to modern browsers
Potential savings of 7 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 how to use modern JavaScript
Largest Contentful Paint element
7,730 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Serve static assets with an efficient cache policy
5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Reduce unused CSS
Potential savings of 18 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.
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 about `font-display`.
Max Potential First Input Delay
770 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.
First Meaningful Paint
5.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
6.5 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.
Prex.app Mobile SEO: 82/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
137 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
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 about the meta description.
Prex.app Mobile Best Practices: 79/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 about HTTPS.
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 about this errors in console diagnostic audit
Prex.app Mobile Accessibility: 89/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 how to make buttons more accessible.
Similar sites
Similar tests
www.prex.com
www.prex.net
www.prex.org
www.prex.info
www.prex.biz
www.prex.us
www.prex.mobi
www.rex.app
www.prex.app
www.orex.app
www.porex.app
www.oprex.app
www.lrex.app
www.plrex.app
www.lprex.app
www.pex.app
www.peex.app
www.preex.app
www.perex.app
www.pdex.app
www.prdex.app
www.pdrex.app
www.pfex.app
www.prfex.app
www.pfrex.app
www.ptex.app
www.prtex.app
www.ptrex.app
www.prx.app
www.prwx.app
www.prewx.app
www.prwex.app
www.prsx.app
www.presx.app
www.prdx.app
www.predx.app
www.prrx.app
www.prerx.app
www.prrex.app
www.pre.app
www.prez.app
www.prexz.app
www.prezx.app
www.pres.app
www.prexs.app
www.pred.app
www.prexd.app
www.prec.app
www.prexc.app
www.precx.app
www.prex.net
www.prex.org
www.prex.info
www.prex.biz
www.prex.us
www.prex.mobi
www.rex.app
www.prex.app
www.orex.app
www.porex.app
www.oprex.app
www.lrex.app
www.plrex.app
www.lprex.app
www.pex.app
www.peex.app
www.preex.app
www.perex.app
www.pdex.app
www.prdex.app
www.pdrex.app
www.pfex.app
www.prfex.app
www.pfrex.app
www.ptex.app
www.prtex.app
www.ptrex.app
www.prx.app
www.prwx.app
www.prewx.app
www.prwex.app
www.prsx.app
www.presx.app
www.prdx.app
www.predx.app
www.prrx.app
www.prerx.app
www.prrex.app
www.pre.app
www.prez.app
www.prexz.app
www.prezx.app
www.pres.app
www.prexs.app
www.pred.app
www.prexd.app
www.prec.app
www.prexc.app
www.precx.app