Amz.run Site Title
Best URL Shortening Service
Amz.run Test Results
Amz.run Mobile Performance: 79/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 1,650 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.
Avoid multiple page redirects. Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve static assets with an efficient cache policy
16 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid chaining critical requests
18 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.
Keep request counts low and transfer sizes small
33 requests • 425 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Amz.run Mobile SEO: 79/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.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. 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
75% 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.
Amz.run Mobile Best Practices: 69/100
Quick overview:
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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
1 vulnerability 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.
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
Amz.run Mobile Progressive Web App: 44/100
Quick overview:
Installable
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.
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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.
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
PWA Optimized
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.
Content is not sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more. The viewport size of 532px does not match the window size of 412px.
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.
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Amz.run Mobile Accessibility: 50/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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. 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.
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.
Similar sites
Similar tests
www.amz.com
www.amz.net
www.amz.org
www.amz.info
www.amz.biz
www.amz.us
www.amz.mobi
www.mz.run
www.amz.run
www.qmz.run
www.aqmz.run
www.qamz.run
www.wmz.run
www.awmz.run
www.wamz.run
www.smz.run
www.asmz.run
www.samz.run
www.zmz.run
www.azmz.run
www.zamz.run
www.az.run
www.anz.run
www.amnz.run
www.anmz.run
www.ajz.run
www.amjz.run
www.ajmz.run
www.akz.run
www.amkz.run
www.akmz.run
www.am.run
www.amx.run
www.amzx.run
www.amxz.run
www.ams.run
www.amzs.run
www.amsz.run
www.ama.run
www.amza.run
www.amaz.run
www.amz.net
www.amz.org
www.amz.info
www.amz.biz
www.amz.us
www.amz.mobi
www.mz.run
www.amz.run
www.qmz.run
www.aqmz.run
www.qamz.run
www.wmz.run
www.awmz.run
www.wamz.run
www.smz.run
www.asmz.run
www.samz.run
www.zmz.run
www.azmz.run
www.zamz.run
www.az.run
www.anz.run
www.amnz.run
www.anmz.run
www.ajz.run
www.amjz.run
www.ajmz.run
www.akz.run
www.amkz.run
www.akmz.run
www.am.run
www.amx.run
www.amzx.run
www.amxz.run
www.ams.run
www.amzs.run
www.amsz.run
www.ama.run
www.amza.run
www.amaz.run