Amp.dev Site Title

AMP - a web component framework to easily create user-first web experiences - amp.dev

Amp.dev Meta Description

Whether you are a publisher, e-commerce company, storyteller, advertiser or email sender, AMP makes it easy to create great experiences on the web. Use AMP to build websites, stories, ads and emails.

Amp.dev Test Results

Amp.dev Mobile Performance: 90/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Remove duplicate modules in JavaScript bundles
Est savings of 15 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
2,910 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce unused JavaScript
Est savings of 58 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.
Serve images in next-gen formats
Est savings of 38 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.
Properly size images
Est savings of 24 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Document request latency
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Use efficient cache lifetimes
Est savings of 8 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Improve image delivery
Est savings of 36 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about forced reflow and its mitigations.

Amp.dev Mobile SEO: 91/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document doesn't have a valid `hreflang`
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about `hreflang`.

Amp.dev Mobile Best Practices: 83/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.
Amp.dev Mobile Accessibility: 80/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 toggle fields do not have accessible names
When a toggle 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 toggle fields.
`[aria-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn how `aria-hidden` affects focusable 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.
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.
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.
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Similar sites
Similar tests
www.amp.com
www.amp.net
www.amp.org
www.amp.info
www.amp.biz
www.amp.us
www.amp.mobi
www.mp.dev
www.amp.dev
www.qmp.dev
www.aqmp.dev
www.qamp.dev
www.wmp.dev
www.awmp.dev
www.wamp.dev
www.smp.dev
www.asmp.dev
www.samp.dev
www.zmp.dev
www.azmp.dev
www.zamp.dev
www.ap.dev
www.anp.dev
www.amnp.dev
www.anmp.dev
www.ajp.dev
www.amjp.dev
www.ajmp.dev
www.akp.dev
www.amkp.dev
www.akmp.dev
www.am.dev
www.amo.dev
www.ampo.dev
www.amop.dev
www.aml.dev
www.ampl.dev
www.amlp.dev
Last Tested: