Amplify.aws Site Title

Full Stack Development - Web and Mobile Apps - AWS Amplify

Amplify.aws Meta Description

Accelerate your full-stack web and mobile app development with AWS Amplify. Easy to start, easy to scale. No cloud expertise needed.

Amplify.aws Test Results

Amplify.aws Mobile Performance: 26/100
Quick overview:
Max Potential First Input Delay
2,730 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
8.1 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
16.7 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.
Diagnostics
Collection of useful page vitals.
Script Treemap Data
Used for treemap app
Metrics
Collects all available metrics.
Final Screenshot
The last screenshot captured of the pageload.

21024342326

Tasks
Lists the toplevel main thread tasks that executed during page load.
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Network Requests
Lists the network requests that were made during page load.
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.

Amplify.aws Mobile SEO: 89/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
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 how to make pages mobile-friendly.
Tap targets are not sized appropriately
46% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.

Amplify.aws Mobile Best Practices: 75/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.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
General
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
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
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Amplify.aws Mobile PWA: 22/100
Quick overview:
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 about manifest installability requirements.
PWA Optimized
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 how to size content for the viewport. The viewport size of 422px does not match the window size of 412px.
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 about Service Workers.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more about theming the address bar. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
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 about splash screens. Failures: No manifest was fetched.
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 about maskable manifest icons. No manifest was fetched
Amplify.aws Mobile Accessibility: 91/100
Quick overview:
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.
`[aria-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
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 about proper list structure.
Similar tests
www.amplify.com
www.amplify.net
www.amplify.org
www.amplify.info
www.amplify.biz
www.amplify.us
www.amplify.mobi
www.mplify.aws
www.amplify.aws
www.qmplify.aws
www.aqmplify.aws
www.qamplify.aws
www.wmplify.aws
www.awmplify.aws
www.wamplify.aws
www.smplify.aws
www.asmplify.aws
www.samplify.aws
www.zmplify.aws
www.azmplify.aws
www.zamplify.aws
www.aplify.aws
www.anplify.aws
www.amnplify.aws
www.anmplify.aws
www.ajplify.aws
www.amjplify.aws
www.ajmplify.aws
www.akplify.aws
www.amkplify.aws
www.akmplify.aws
www.amlify.aws
www.amolify.aws
www.ampolify.aws
www.amoplify.aws
www.amllify.aws
www.ampllify.aws
www.amlplify.aws
www.ampify.aws
www.amppify.aws
www.amplpify.aws
www.ampplify.aws
www.ampoify.aws
www.amploify.aws
www.ampkify.aws
www.amplkify.aws
www.ampklify.aws
www.amplfy.aws
www.amplufy.aws
www.ampliufy.aws
www.ampluify.aws
www.ampljfy.aws
www.amplijfy.aws
www.ampljify.aws
www.amplkfy.aws
www.amplikfy.aws
www.amplofy.aws
www.ampliofy.aws
www.ampliy.aws
www.amplicy.aws
www.amplifcy.aws
www.amplicfy.aws
www.amplidy.aws
www.amplifdy.aws
www.amplidfy.aws
www.ampliry.aws
www.amplifry.aws
www.amplirfy.aws
www.amplity.aws
www.amplifty.aws
www.amplitfy.aws
www.ampligy.aws
www.amplifgy.aws
www.ampligfy.aws
www.amplivy.aws
www.amplifvy.aws
www.amplivfy.aws
www.amplif.aws
www.amplift.aws
www.amplifyt.aws
www.amplifg.aws
www.amplifyg.aws
www.amplifh.aws
www.amplifyh.aws
www.amplifhy.aws
www.amplifu.aws
www.amplifyu.aws
www.amplifuy.aws
Last Tested: