Tools & Wizards About Us
amp.dev screenshot

Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

amp.dev

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

Page Load Speed

302 ms in total

First Response

110 ms

Resources Loaded

192 ms

Page Rendered

0 ms

amp.dev screenshot

About Website

Visit amp.dev now to see the best up-to-date AMP content for India and also check out these interesting facts you probably never knew about amp.dev

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.

Visit amp.dev

Key Findings

We analyzed Amp.dev page load time and found that the first response time was 110 ms and then it took 192 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

amp.dev performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value1.6 s

100/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.6 s

91/100

10%

Network Requests Diagram

amp.dev

110 ms

amp.dev

36 ms

v0.js

29 ms

amp-analytics-0.1.js

42 ms

amp-animation-0.1.js

49 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 21% of them (3 requests) were addressed to the original Amp.dev, 79% (11 requests) were made to Cdn.ampproject.org. The less responsive or slowest element that took the longest time to load (110 ms) belongs to the original domain Amp.dev.

Page Optimization Overview & Recommendations

Page size can be reduced by 129.4 kB (31%)

Content Size

414.5 kB

After Optimization

285.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Amp.dev main page is 414.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 223.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 109.5 kB

  • Original 138.4 kB
  • After minification 138.4 kB
  • After compression 28.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 109.5 kB or 79% of the original size.

Image Optimization

-26%

Potential reduce by 13.7 kB

  • Original 53.1 kB
  • After minification 39.4 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, AMP needs image optimization as it can save up to 13.7 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 6.2 kB

  • Original 223.0 kB
  • After minification 223.0 kB
  • After compression 216.8 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 10 (83%)

Requests Now

12

After Optimization

2

  • Images
  • JavaScript

The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AMP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

amp.dev

amp.dev

110 ms

amp.dev

amp.dev

36 ms

v0.js

v0.js

29 ms

amp-analytics-0.1.js

amp-analytics-0.1.js

42 ms

amp-animation-0.1.js

amp-animation-0.1.js

49 ms

amp-base-carousel-0.1.js

amp-base-carousel-0.1.js

54 ms

amp-bind-0.1.js

amp-bind-0.1.js

55 ms

amp-consent-0.1.js

amp-consent-0.1.js

59 ms

amp-fx-collection-0.1.js

amp-fx-collection-0.1.js

54 ms

amp-geo-0.1.js

amp-geo-0.1.js

51 ms

amp-install-serviceworker-0.1.js

amp-install-serviceworker-0.1.js

54 ms

amp-position-observer-0.1.js

amp-position-observer-0.1.js

61 ms

amp-selector-0.1.js

amp-selector-0.1.js

61 ms

https%253A%252F%252Fblog.amp.dev%252Fwp-content%252Fuploads%252F2021%252F12%252Funboxing-the-bento-component-library-768x384.png

https%253A%252F%252Fblog.amp.dev%252Fwp-content%252Fuploads%252F2021%252F12%252Funboxing-the-bento-component-library-768x384.png

5 ms

Accessibility Review

amp.dev accessibility score

83

Accessibility Issues

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.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

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.

Impact

Issue

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

amp.dev best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

amp.dev SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a valid hreflang

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](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Amp.dev can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Amp.dev main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

amp.dev

Open Graph description is not detected on the main page of AMP. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: