Au21.capital Test Results
Au21.capital Mobile Performance: 55/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Eliminate render-blocking resources
Est savings of 14,470 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.
Reduce unused JavaScript
Est savings of 2,135 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 multiple page redirects
Est savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Largest Contentful Paint element
15,570 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Reduce unused CSS
Est savings of 148 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 enormous network payloads
Total size was 2,686 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Avoid serving legacy JavaScript to modern browsers
Est savings of 46 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
Enable text compression
Est savings of 2 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Reduce the impact of third-party code
Third-party code blocked the main thread for 580 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 how to minimize third-party impact.
Render blocking requests
Est savings of 15,390 ms
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.
Document request latency
Est savings of 2 KiB
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Network dependency tree
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Legacy JavaScript
Est savings of 45 KiB
Polyfills and transforms enable older 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 older browsers. Learn why most sites can deploy ES6+ code without transpiling
Time to Interactive
15.6 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.
Optimize viewport for mobile
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
Au21.capital Mobile SEO: 80/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 about the meta description.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Page has unsuccessful HTTP status code
404
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Au21.capital Mobile Best Practices: 72/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
User Experience
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Document doesn't use legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes. Text is illegible because there's no viewport meta tag optimized for mobile screens.
Au21.capital Mobile Accessibility: 71/100
Quick overview:
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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Similar tests
www.au21.com
www.au21.net
www.au21.org
www.au21.info
www.au21.biz
www.au21.us
www.au21.mobi
www.u21.capital
www.au21.capital
www.qu21.capital
www.aqu21.capital
www.qau21.capital
www.wu21.capital
www.awu21.capital
www.wau21.capital
www.su21.capital
www.asu21.capital
www.sau21.capital
www.zu21.capital
www.azu21.capital
www.zau21.capital
www.a21.capital
www.ay21.capital
www.auy21.capital
www.ayu21.capital
www.ah21.capital
www.auh21.capital
www.ahu21.capital
www.aj21.capital
www.auj21.capital
www.aju21.capital
www.ai21.capital
www.aui21.capital
www.aiu21.capital
www.au1.capital
www.au2.capital
www.au21.net
www.au21.org
www.au21.info
www.au21.biz
www.au21.us
www.au21.mobi
www.u21.capital
www.au21.capital
www.qu21.capital
www.aqu21.capital
www.qau21.capital
www.wu21.capital
www.awu21.capital
www.wau21.capital
www.su21.capital
www.asu21.capital
www.sau21.capital
www.zu21.capital
www.azu21.capital
www.zau21.capital
www.a21.capital
www.ay21.capital
www.auy21.capital
www.ayu21.capital
www.ah21.capital
www.auh21.capital
www.ahu21.capital
www.aj21.capital
www.auj21.capital
www.aju21.capital
www.ai21.capital
www.aui21.capital
www.aiu21.capital
www.au1.capital
www.au2.capital