Morador.org Site Title

Documento sin título

Morador.org Test Results

Morador.org Mobile Performance: 61/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve images in next-gen formats
Potential savings of 245 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.
Reduce unused CSS
Potential savings of 31 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.
Minify CSS
Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Largest Contentful Paint element
6,810 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Minify JavaScript
Potential savings of 63 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Reduce unused JavaScript
Potential savings of 158 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.
Eliminate render-blocking resources
Potential savings of 2,070 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.
Avoid multiple page redirects
Potential savings of 2,190 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
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 how to set image dimensions
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 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
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 about adopting passive event listeners.
Properly size images
Potential savings of 50 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Serve static assets with an efficient cache policy
50 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
First Meaningful Paint
5.2 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
8.2 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.

Morador.org Mobile SEO: 92/100
Quick overview:
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 how to make links crawlable

Morador.org 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
Morador.org Mobile Accessibility: 80/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.
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 how to make links accessible.
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.
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.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
ARIA input fields do not have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
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 tests
www.morador.com
www.morador.net
www.morador.org
www.morador.info
www.morador.biz
www.morador.us
www.morador.mobi
www.orador.org
www.morador.org
www.norador.org
www.mnorador.org
www.nmorador.org
www.jorador.org
www.mjorador.org
www.jmorador.org
www.korador.org
www.mkorador.org
www.kmorador.org
www.mrador.org
www.mirador.org
www.moirador.org
www.miorador.org
www.mkrador.org
www.mokrador.org
www.mlrador.org
www.molrador.org
www.mlorador.org
www.mprador.org
www.moprador.org
www.mporador.org
www.moador.org
www.moeador.org
www.moreador.org
www.moerador.org
www.modador.org
www.mordador.org
www.modrador.org
www.mofador.org
www.morfador.org
www.mofrador.org
www.motador.org
www.mortador.org
www.motrador.org
www.mordor.org
www.morqdor.org
www.moraqdor.org
www.morqador.org
www.morwdor.org
www.morawdor.org
www.morwador.org
www.morsdor.org
www.morasdor.org
www.morsador.org
www.morzdor.org
www.morazdor.org
www.morzador.org
www.moraor.org
www.moraxor.org
www.moradxor.org
www.moraxdor.org
www.morasor.org
www.moradsor.org
www.moraeor.org
www.moradeor.org
www.moraedor.org
www.moraror.org
www.moradror.org
www.morardor.org
www.morafor.org
www.moradfor.org
www.morafdor.org
www.moracor.org
www.moradcor.org
www.moracdor.org
www.moradr.org
www.moradir.org
www.moradoir.org
www.moradior.org
www.moradkr.org
www.moradokr.org
www.moradkor.org
www.moradlr.org
www.moradolr.org
www.moradlor.org
www.moradpr.org
www.moradopr.org
www.moradpor.org
www.morado.org
www.moradoe.org
www.moradore.org
www.moradoer.org
www.moradod.org
www.moradord.org
www.moradodr.org
www.moradof.org
www.moradorf.org
www.moradofr.org
www.moradot.org
www.moradort.org
www.moradotr.org
Last Tested: