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

Overview

Snoop Summary for ampproject.org

This is a free and comprehensive report about ampproject.org. The domain ampproject.org is currently hosted on a server located in United States with the IP address 172.217.12.174, where USD is the local currency and the local language is English. Ampproject.org is expected to earn an estimated $8,552 USD per day from advertising revenue. The sale of ampproject.org would possibly be worth $6,243,219 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Ampproject.org is insanely popular with an estimated 918,533 daily unique visitors. This report was last updated 30th May, 2023.

About ampproject.org

Site Preview:
Title:	AMP - a web component framework to easily create user-first web experiences - amp.dev
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.
Keywords and Tags:	internet services
Related Terms:	create memorable customer experiences, experiences
Fav Icon:
Age:	Over 9 years old
Domain Created:	31st August, 2015
Domain Updated:	30th July, 2020
Domain Expires:	31st August, 2021

Review

Snoop Score

4/5 (Excellent!)

Valuation

$6,243,219 USD

Note: All valuation figures are estimates.

Popularity

Very High

Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank:	2,429
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority:	87
Moz Page Authority:	57

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors:	918,533
Monthly Visitors:	27,957,251
Yearly Visitors:	335,264,545

Note: All visitors figures are estimates.

Visitors By Country

Revenue

Daily Revenue:	$8,552 USD
Monthly Revenue:	$260,306 USD
Yearly Revenue:	$3,121,605 USD

Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top Ranking Keywords (US)

Domain Analysis

	Value	Length
Domain:	ampproject.org	14
Domain Name:	ampproject	10
Extension (TLD):	org	3

Expiry Check:

Page Speed Analysis

Average Load Time:	0.84 seconds
Load Time Comparison:	Faster than 86% of sites

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

URL: https://amp.dev/

Updated: 31st March, 2021

1.37 seconds

First Contentful Paint (FCP)

62%

33%

5%

0.01 seconds

First Input Delay (FID)

97%

2%

1%

Simulate loading on desktop

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for ampproject.org. This includes details about optimizing page load times which can result in a better user experience.

Passing (50)
Average (6)

Metrics

Speed Index — 1.2 s
The time taken for the page contents to be visibly populated.

Time to Interactive — 1.2 s
The time taken for the page to become fully interactive.

Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 1.2 s
The time taken for the page's main thread to be quiet enough to handle input.

Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive ampproject.org as laggy when the latency is higher than 0.05 seconds.

Network Requests
Below is a list of network requests that were made during page load.

URL	Protocol	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://ampproject.org/	http/1.1	0	10.264999698848	293	0	302	text/html
https://ampproject.org/	http/1.1	10.981000028551	20.09700005874	574	0	302	text/html
https://www.ampproject.org/	http/1.1	20.773000083864	66.056000068784	401	0	301	text/plain
https://amp.dev/	h2	66.56499998644	113.10999980196	34433	181953	200	text/html	Document
https://cdn.ampproject.org/v0.mjs	h2	127.31699971482	138.85700004175	64435	221336	200	text/javascript	Script
https://amp.dev/static/fonts/poppins-v5-latin-700.woff2	h2	128.01199965179	139.69099987298	8989	7832	200	font/woff2	Font
https://amp.dev/static/fonts/noto-sans-v7-latin-700.woff2	h2	128.15100001171	1357.7509997413	10873	9716	200	font/woff2	Font
https://cdn.ampproject.org/v0/amp-bind-0.1.mjs	h2	133.74600000679	146.81300008669	15383	39989	200	text/javascript	Script
https://cdn.ampproject.org/v0/amp-lightbox-0.1.mjs	h2	133.95099993795	140.04099974409	7744	18077	200	text/javascript	Script
https://cdn.ampproject.org/v0/amp-form-0.1.mjs	h2	134.24099981785	141.03399962187	14547	41811	200	text/javascript	Script
https://cdn.ampproject.org/v0/amp-autocomplete-0.1.mjs	h2	134.77199990302	141.51299977675	9548	24647	200	text/javascript	Script
https://cdn.ampproject.org/v0/amp-list-0.1.mjs	h2	135.00100001693	143.19599978626	12753	35153	200	text/javascript	Script
https://cdn.ampproject.org/v0/amp-mustache-0.2.mjs	h2	135.34999964759	142.65499962494	14846	37319	200	text/javascript	Script
https://cdn.ampproject.org/v0/amp-carousel-0.2.mjs	h2	135.65099984407	140.56299999356	9924	27747	200	text/javascript	Script
https://cdn.ampproject.org/v0/amp-animation-0.1.mjs	h2	135.821999982	143.72799964622	17934	72009	200	text/javascript	Script
https://cdn.ampproject.org/v0/amp-analytics-0.1.mjs	h2	136.07000000775	145.32599970698	28962	89964	200	text/javascript	Script
https://cdn.ampproject.org/v0/amp-geo-0.1.mjs	h2	136.25299977139	141.81699976325	4881	7841	200	text/javascript	Script
https://cdn.ampproject.org/v0/amp-consent-0.1.mjs	h2	136.48899970576	144.83099989593	17202	50351	200	text/javascript	Script
https://cdn.ampproject.org/v0/amp-install-serviceworker-0.1.mjs	h2	136.65500003844	144.43999994546	4130	7334	200	text/javascript	Script
https://amp.dev/static/img/case-band-image-2.jpg?width=330&hash=33e5e2d61e897ee4dc33b6f74f25fdb7207681f9	h2	150.22299997509	2692.1099997126	16007	14988	200	image/webp	Image
https://amp.dev/static/img/case-band-image-1.png?width=470&hash=ae5b590ed0ec6bd943c89ade636ed3bb4f23a439	h2	150.41700005531	418.07799972594	26009	24990	200	image/webp	Image
https://amp.dev/static/img/case-band-image-5.jpg?width=560&hash=3530d3ec7ab20242dc2eb32ac2603896fcf8d359	h2	150.54599987343	314.50699968264	23853	22834	200	image/webp	Image
https://amp.dev/static/img/case-band-image-4.jpg?width=470&hash=1130d8f01b674fb0f2a505cf422cd8d208623024	h2	150.67699970677	2699.643000029	71329	70310	200	image/webp	Image
https://amp.dev/static/img/case-band-image-3.jpg?width=560&hash=104d3cb8772292735d6b30dd42e3af908d95df6f	h2	150.80699976534	2676.2959999032	24869	23850	200	image/webp	Image
https://amp.dev/static/fonts/noto-sans-v7-latin-regular.woff2	h2	206.22699987143	213.25099980459	11101	9944	200	font/woff2	Font
https://amp.dev/static/fonts/fira-mono-v7-latin-500.woff2	h2	208.4649996832	1359.90999965	17790	16632	200	font/woff2	Font
https://amp.dev/static/img/component-visual-site.jpg?width=470&hash=0ae2ab2813772ebfd1e3b935dfe23c8037201db5	h2	445.7679996267	900.11500008404	60095	59076	200	image/webp	Image
https://amp.dev/static/img/component-visual-nav.jpg?width=330&hash=a38aed562af191b3484a0644019da6360f3ce43e	h2	445.94099977985	685.14099996537	10353	9334	200	image/webp	Image
https://amp.dev/static/img/amp-stories-base.png?width=560&hash=1e021188d08d7208d0200d56aae89a4995b19161	h2	446.18600001559	2683.4959997796	3685	2666	200	image/webp	Image
https://amp.dev/static/img/amp-stories-monde.jpg?width=680&hash=8fc1c71d9a0e6255cb7ed4b30d3eff3f8f0034b2	h2	446.54499972239	2683.0380000174	47939	46920	200	image/webp	Image
https://amp.dev/static/img/amp-ads-bottom.jpg?width=470&hash=a27af8ab46938ad00508cd8e8143cc28babeb108	h2	446.76799979061	801.86000000685	20767	19748	200	image/webp	Image
https://amp.dev/static/img/amp-ads-top.jpg?width=560&hash=be67a20485737a09fd8dc0e8f07e3e1a6e0cf1af	h2	446.99699990451	2678.9130000398	23031	22012	200	image/webp	Image
https://amp.dev/static/img/amp-email-base.jpg?width=470&hash=3f6ec6237880d3b02190238fcc457bb17f61e92b	h2	447.2839999944	2688.0179997534	15139	14120	200	image/webp	Image
https://amp.dev/static/img/amp-email-top.jpg?width=560&hash=0c53167d16d7668d5bb4dfa126704fccb97e8c2b	h2	447.57799990475	2685.7880000025	8015	6996	200	image/webp	Image
https://cdn.ampproject.org/rtv/012103122145004/v0/amp-auto-lightbox-0.1.mjs	h2	466.94499999285	472.42800006643	3187	4398	200	text/javascript	Script
https://cdn.ampproject.org/rtv/012103122145004/ww.mjs	h2	530.20999999717	535.28899978846	14637	45343	200	text/javascript	Fetch
https://amp.dev/search/latest-query?__amp_source_origin=https%3A%2F%2Famp.dev	h2	544.89699983969	879.92099998519	1314	4	200	application/json	Fetch
https://amp.dev/search/highlights?locale=en&__amp_source_origin=https%3A%2F%2Famp.dev	h2	545.36199988797	552.23299982026	1811	1942	200	application/json	Fetch
	data	588.26899994165	588.33499997854	0	160	200	image/svg+xml	Image
	data	590.52799968049	590.59199970216	0	153	200	image/svg+xml	Image
https://cdn.ampproject.org/rtv/012103122145004/v0/amp-loader-0.1.mjs	h2	610.13399995863	614.8839998059	5065	14882	200	text/javascript	Script
https://amp.dev/static/remote/?url=https%3A%2F%2Fblog.amp.dev%2Fwp-content%2Fuploads%2F2021%2F03%2FAMPBlogBanner_Optimize_CWVfixed-300x150.jpg&width=560	h2	654.64099962264	888.49300006405	12655	11636	200	image/webp	Image
https://amp.dev/static/remote/?url=https%3A%2F%2Fblog.amp.dev%2Fwp-content%2Fuploads%2F2021%2F01%2Fimage1-1-300x150.png&width=560	h2	654.85799964517	2744.4189996459	9793	8774	200	image/webp	Image
https://amp.dev/static/remote/?url=https%3A%2F%2Fblog.amp.dev%2Fwp-content%2Fuploads%2F2021%2F01%2FCWV_Study_Graphic-1-300x150.jpg&width=560	h2	655.06799984723	851.73999983817	12631	11612	200	image/webp	Image
https://amp.dev/static/remote/?url=https%3A%2F%2Fblog.amp.dev%2Fwp-content%2Fuploads%2F2020%2F12%2FAsset-1-50-300x150.jpg&width=560	h2	655.34799965099	2689.5639998838	15801	14782	200	image/webp	Image
https://amp.dev/static/remote/?url=https%3A%2F%2Fblog.amp.dev%2Fwp-content%2Fuploads%2F2020%2F12%2Fimage2-300x169.png&width=560	h2	655.62399988994	813.58399987221	11233	10214	200	image/webp	Image
blob:https://amp.dev/aab054ea-67d9-4675-9c88-5750968706a6	blob	666.88499972224	668.38299995288	0	45411	200	text/javascript	Other
https://cdn.ampproject.org/rtv/012103122145004/v0/analytics-vendors/gtag.json	h2	2411.9499996305	2415.8689999022	2238	2484	200	application/json	Fetch
https://www.googletagmanager.com/gtag/amp?__amp_source_origin=https%3A%2F%2Famp.dev	h2	2428.7589997984	2444.6169999428	1323	1667	200	application/json	Fetch
https://www.google-analytics.com/r/collect?v=1&_v=a1&ds=AMP&aip&_s=1&dt=AMP%20-%20a%20web%20component%20framework%20to%20easily%20create%20user-first%20web%20experiences%20-%20amp.dev&sr=800x600&cid=amp-U0GCJfTYstRA1TiUZjGwTg&tid=UA-67833617-1&dl=https%3A%2F%2Famp.dev%2F&dr=&sd=24&ul=en-us&de=UTF-8&t=pageview&jid=0.2942213729477703&gjid=0.36372371230467815&_r=1&a=6807&z=0.4884611867694926&cd2=amp.dev&gtm=2pu000	http/1.1	2479.9919999205	2501.6379998997	777	0	302	text/html
https://stats.g.doubleclick.net/r/collect?v=1&aip=1&t=dc&_r=3&tid=UA-67833617-1&cid=amp-U0GCJfTYstRA1TiUZjGwTg&jid=0.2942213729477703&_v=a1&z=0.4884611867694926	http/1.1	2501.9640000537	2516.4079996757	847	0	302	text/html
https://www.google.com/ads/ga-audiences?v=1&aip=1&t=sr&_r=4&tid=UA-67833617-1&cid=amp-U0GCJfTYstRA1TiUZjGwTg&jid=0.2942213729477703&_v=a1&z=0.4884611867694926	h2	2516.6889997199	2524.2469999939	678	42	200	image/gif	Image

Show Details

Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.

Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.

Tasks
Below is a list of the top-level main thread tasks that executed during page load.

Start Time (Ms)	End Time (Ms)
146.87	8.996
159.992	7.348
174.1	12.321
202.782	40.948
260.516	20.106
284.588	5.622
290.248	7.142
300.571	61.415
376.942	77.08
454.64	37.942
497.518	89.069
586.609	25.061
611.685	26.899
647.269	14.515
677.191	15.344
700.583	14.451
726.762	5.627
746.06	6.676
769.927	5.462
838.016	5.079
860.581	5.526
883.721	5.382
927.67	5.304
949.325	5.061
1404.211	14.903
1419.15	14.183
2448.085	10.46
2482.265	28.294
2510.579	5.668
2520.973	5.412
2535.722	5.745
2724.849	7.152

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ampproject.org should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

Properly size images — Potential savings of 223 KiB
Images can slow down the page's load time. Ampproject.org should consider serving more appropriate-sized images.

URL	Resource Size (Bytes)	Potential Savings (Bytes)
https://amp.dev/static/img/component-visual-site.jpg?width=470&hash=0ae2ab2813772ebfd1e3b935dfe23c8037201db5	59076	35958
https://amp.dev/static/img/case-band-image-4.jpg?width=470&hash=1130d8f01b674fb0f2a505cf422cd8d208623024	70310	34957
https://amp.dev/static/img/amp-stories-monde.jpg?width=680&hash=8fc1c71d9a0e6255cb7ed4b30d3eff3f8f0034b2	46920	33842
https://amp.dev/static/img/case-band-image-1.png?width=470&hash=ae5b590ed0ec6bd943c89ade636ed3bb4f23a439	24990	14347
https://amp.dev/static/img/amp-ads-top.jpg?width=560&hash=be67a20485737a09fd8dc0e8f07e3e1a6e0cf1af	22012	13545
https://amp.dev/static/img/amp-ads-bottom.jpg?width=470&hash=a27af8ab46938ad00508cd8e8143cc28babeb108	19748	13093
https://amp.dev/static/img/case-band-image-3.jpg?width=560&hash=104d3cb8772292735d6b30dd42e3af908d95df6f	23850	12423
https://amp.dev/static/remote/?url=https%3A%2F%2Fblog.amp.dev%2Fwp-content%2Fuploads%2F2020%2F12%2FAsset-1-50-300x150.jpg&width=560	14782	10384
https://amp.dev/static/img/case-band-image-5.jpg?width=560&hash=3530d3ec7ab20242dc2eb32ac2603896fcf8d359	22834	9452
https://amp.dev/static/remote/?url=https%3A%2F%2Fblog.amp.dev%2Fwp-content%2Fuploads%2F2021%2F03%2FAMPBlogBanner_Optimize_CWVfixed-300x150.jpg&width=560	11636	8174
https://amp.dev/static/remote/?url=https%3A%2F%2Fblog.amp.dev%2Fwp-content%2Fuploads%2F2021%2F01%2FCWV_Study_Graphic-1-300x150.jpg&width=560	11612	8157
https://amp.dev/static/remote/?url=https%3A%2F%2Fblog.amp.dev%2Fwp-content%2Fuploads%2F2020%2F12%2Fimage2-300x169.png&width=560	10214	7513
https://amp.dev/static/img/amp-email-base.jpg?width=470&hash=3f6ec6237880d3b02190238fcc457bb17f61e92b	14120	7445
https://amp.dev/static/img/case-band-image-2.jpg?width=330&hash=33e5e2d61e897ee4dc33b6f74f25fdb7207681f9	14988	7140
https://amp.dev/static/remote/?url=https%3A%2F%2Fblog.amp.dev%2Fwp-content%2Fuploads%2F2021%2F01%2Fimage1-1-300x150.png&width=560	8774	6163
https://amp.dev/static/img/component-visual-nav.jpg?width=330&hash=a38aed562af191b3484a0644019da6360f3ce43e	9334	5778

Show Details

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ampproject.org should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ampproject.org should consider minifying CSS files.

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ampproject.org should consider minifying JS files.

Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ampproject.org should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.

Remove unused JavaScript — Potential savings of 29 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
https://cdn.ampproject.org/v0.mjs	64435	30093

Show Details

Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.

Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.

Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

Initial server response time was short — Root document took 50 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.

URL	Time Spent (Ms)
https://amp.dev/	47.541

Show Details

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ampproject.org should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.

Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

URL	Potential Savings (Ms)
https://amp.dev/static/img/case-band-image-4.jpg?width=470&hash=1130d8f01b674fb0f2a505cf422cd8d208623024	0

Show Details

Diagnostics

Avoids enormous network payloads — Total size was 734 KiB
Large network payloads can cost users money and are linked to long load times.

URL	Transfer Size (Bytes)
https://amp.dev/static/img/case-band-image-4.jpg?width=470&hash=1130d8f01b674fb0f2a505cf422cd8d208623024	71329
https://cdn.ampproject.org/v0.mjs	64435
https://amp.dev/static/img/component-visual-site.jpg?width=470&hash=0ae2ab2813772ebfd1e3b935dfe23c8037201db5	60095
https://amp.dev/static/img/amp-stories-monde.jpg?width=680&hash=8fc1c71d9a0e6255cb7ed4b30d3eff3f8f0034b2	47939
https://amp.dev/	34433
https://cdn.ampproject.org/v0/amp-analytics-0.1.mjs	28962
https://amp.dev/static/img/case-band-image-1.png?width=470&hash=ae5b590ed0ec6bd943c89ade636ed3bb4f23a439	26009
https://amp.dev/static/img/case-band-image-3.jpg?width=560&hash=104d3cb8772292735d6b30dd42e3af908d95df6f	24869
https://amp.dev/static/img/case-band-image-5.jpg?width=560&hash=3530d3ec7ab20242dc2eb32ac2603896fcf8d359	23853
https://amp.dev/static/img/amp-ads-top.jpg?width=560&hash=be67a20485737a09fd8dc0e8f07e3e1a6e0cf1af	23031

Show Details

Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ampproject.org should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

User Timing marks and measures — 8 user timings
Make use of the User Timing API to measure an app's real-world performance during key user experiences.

Name	Type	Start Time (Ms)
is	Mark	356.006
dr	Mark	356.67
visible	Mark	369.426
ofv	Mark	369.472
mbv	Mark	402.07
e_is	Mark	402.321
pc	Mark	2705.204
ol	Mark	2748.243

Show Details

JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

URL	Total CPU Time (Ms)	Script Evaluation (Ms)	Script Parse (Ms)
https://amp.dev/	644.64800000001	3.002	1.205
https://cdn.ampproject.org/v0.mjs	432.898	279.248	16.26
Unattributable	110.691	20.591	0.399

Show Details

Minimizes main-thread work — 1.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

Category	Time Spent (Ms)
Rendering	331.83700000001
Script Evaluation	315.767
Style & Layout	275.409
Other	244.142
Script Parsing & Compilation	45.15
Parse HTML & CSS	25.856
Garbage Collection	5.611

Show Details

All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.

Keep request counts low and transfer sizes small — 49 requests • 734 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.

Resource Type	Requests	Transfer Size (Bytes)
Total	49	751824
Image	19	413882
Script	15	230541
Font	4	48753
Document	1	34433
Other	10	24215
Stylesheet	0	0
Media	0	0
Third-party	24	252309

Show Details

Minimize third-party usage — Third-party code blocked the main thread for 30 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.

Third-Party	Transfer Size (Bytes)	Main-Thread Blocking Time (Ms)
SHOW DETAILS	248684	29.346
SHOW DETAILS	1323	0
SHOW DETAILS	847	0
SHOW DETAILS	777	0
SHOW DETAILS	678	0

Show Details

Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).

Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.

Element
A screenshot of a website using AMP.

Show Details

Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.

Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.

Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.

Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.

Avoid non-composited animations — 21 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Element	Name
websites.
stories.
ads.
emails.
A screenshot of a website using AMP.
A screenshot of a website using AMP.
A screenshot of a website using AMP.
A screenshot of a website using AMP.
A screenshot of a website using AMP.
A screenshot showing amp-sidebar.
<amp-sidebar id="sidebar" layout="nodisplay" side= "right" " " "left" </…
div
div
div
div
div
div
div
path
path
path

Show Details

Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.

Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 1.2 s
The time taken for the first image or text on the page to be rendered.

Largest Contentful Paint — 1.9 s
The timing of the largest text or image that is painted.

Other

First Meaningful Paint — 1.2 s
The time taken for the primary content of the page to be rendered.

Opportunities

Avoid multiple page redirects — Potential savings of 570 ms
Redirects can cause additional delays before the page can begin loading. Ampproject.org should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
http://ampproject.org/	190
https://ampproject.org/	150
https://www.ampproject.org/	230
https://amp.dev/	0

Show Details

Diagnostics

Serve static assets with an efficient cache policy — 18 resources found
Ampproject.org can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.

URL	Cache TTL (Ms)	Transfer Size (Bytes)
https://amp.dev/static/img/case-band-image-4.jpg?width=470&hash=1130d8f01b674fb0f2a505cf422cd8d208623024	604800000	71329
https://amp.dev/static/img/component-visual-site.jpg?width=470&hash=0ae2ab2813772ebfd1e3b935dfe23c8037201db5	604800000	60095
https://amp.dev/static/img/amp-stories-monde.jpg?width=680&hash=8fc1c71d9a0e6255cb7ed4b30d3eff3f8f0034b2	604800000	47939
https://amp.dev/static/img/case-band-image-1.png?width=470&hash=ae5b590ed0ec6bd943c89ade636ed3bb4f23a439	604800000	26009
https://amp.dev/static/img/case-band-image-3.jpg?width=560&hash=104d3cb8772292735d6b30dd42e3af908d95df6f	604800000	24869
https://amp.dev/static/img/case-band-image-5.jpg?width=560&hash=3530d3ec7ab20242dc2eb32ac2603896fcf8d359	604800000	23853
https://amp.dev/static/img/amp-ads-top.jpg?width=560&hash=be67a20485737a09fd8dc0e8f07e3e1a6e0cf1af	604800000	23031
https://amp.dev/static/img/amp-ads-bottom.jpg?width=470&hash=a27af8ab46938ad00508cd8e8143cc28babeb108	604800000	20767
https://amp.dev/static/img/case-band-image-2.jpg?width=330&hash=33e5e2d61e897ee4dc33b6f74f25fdb7207681f9	604800000	16007
https://amp.dev/static/remote/?url=https%3A%2F%2Fblog.amp.dev%2Fwp-content%2Fuploads%2F2020%2F12%2FAsset-1-50-300x150.jpg&width=560	604800000	15801
https://amp.dev/static/img/amp-email-base.jpg?width=470&hash=3f6ec6237880d3b02190238fcc457bb17f61e92b	604800000	15139
https://amp.dev/static/remote/?url=https%3A%2F%2Fblog.amp.dev%2Fwp-content%2Fuploads%2F2021%2F03%2FAMPBlogBanner_Optimize_CWVfixed-300x150.jpg&width=560	604800000	12655
https://amp.dev/static/remote/?url=https%3A%2F%2Fblog.amp.dev%2Fwp-content%2Fuploads%2F2021%2F01%2FCWV_Study_Graphic-1-300x150.jpg&width=560	604800000	12631
https://amp.dev/static/remote/?url=https%3A%2F%2Fblog.amp.dev%2Fwp-content%2Fuploads%2F2020%2F12%2Fimage2-300x169.png&width=560	604800000	11233
https://amp.dev/static/img/component-visual-nav.jpg?width=330&hash=a38aed562af191b3484a0644019da6360f3ce43e	604800000	10353
https://amp.dev/static/remote/?url=https%3A%2F%2Fblog.amp.dev%2Fwp-content%2Fuploads%2F2021%2F01%2Fimage1-1-300x150.png&width=560	604800000	9793
https://amp.dev/static/img/amp-email-top.jpg?width=560&hash=0c53167d16d7668d5bb4dfa126704fccb97e8c2b	604800000	8015
https://amp.dev/static/img/amp-stories-base.png?width=560&hash=1e021188d08d7208d0200d56aae89a4995b19161	604800000	3685

Show Details

Avoid an excessive DOM size — 1,160 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.

Statistic	Element	Value
Total DOM Elements		1160
Maximum DOM Depth	i-amphtml-sizer	12
Maximum Child Elements	defs	32

Show Details

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ampproject.org. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.

The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.

No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.

`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.

`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.

ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.

ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.

Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.

`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.

`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.

ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.

ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.

`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.

`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.

Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.

Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.

Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.

List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.

Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.

`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.

`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Ampproject.org may provide assistance to deaf or hearing-impaired users with captions on videos.

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.

Failing Elements
Optimizing your AMP page experience for Core Web Vitals
Too much choice
Follow us

Show Details

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.

Failing Elements
input

Show Details

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.

Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.

Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.

The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.

User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.

Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.

Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.

Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.

Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.

HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that ampproject.org should incorporate. This includes practices such as protecting pages with HTTPS.

Passing (15)
Failing (3)

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.

Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Avoids Application Cache
Application cache is deprecated and is no longer recommended.

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.

Name	Version
AMP	2103122145004

Show Details

Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.

Insecure URL	Request Resolution
http://ampproject.org/	Allowed

Show Details

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
https://amp.dev/static/img/case-band-image-4.jpg?width=470&hash=1130d8f01b674fb0f2a505cf422cd8d208623024	334 x 496 (0.67)	470 x 701 (0.67)
https://amp.dev/static/img/amp-ads-top.jpg?width=560&hash=be67a20485737a09fd8dc0e8f07e3e1a6e0cf1af	359 x 294 (1.22)	560 x 490 (1.14)

Show Details

Fonts with `font-display: optional` are not preloaded
It is recommended that optional fonts are preloaded.

URL
https://amp.dev/static/fonts/noto-sans-v7-latin-regular.woff2
https://amp.dev/static/fonts/noto-sans-v7-latin-regular.woff
https://amp.dev/static/fonts/noto-sans-v7-latin-700.woff
https://amp.dev/static/fonts/poppins-v5-latin-700.woff
https://amp.dev/static/fonts/fira-mono-v7-latin-500.woff2
https://amp.dev/static/fonts/fira-mono-v7-latin-500.woff

Show Details

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for ampproject.org. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ampproject.org on mobile screens.

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.

Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.

Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.

Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Document doesn't have a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.

Show Details

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of ampproject.org. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Registers a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.

Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data

Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ampproject.org on mobile screens.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.

Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.

Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.

Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

URL: https://amp.dev/

Updated: 31st March, 2021

2.73 seconds

First Contentful Paint (FCP)

28%

52%

20%

0.08 seconds

First Input Delay (FID)

79%

15%

6%

Simulate loading on mobile

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for ampproject.org. This includes details about optimizing page load times which can result in a better user experience.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ampproject.org should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

Properly size images — Potential savings of 61 KiB
Images can slow down the page's load time. Ampproject.org should consider serving more appropriate-sized images.

URL	Resource Size (Bytes)	Potential Savings (Bytes)
https://amp.dev/static/img/case-band-image-4.jpg?width=470&hash=1130d8f01b674fb0f2a505cf422cd8d208623024	70310	31098
https://amp.dev/static/img/case-band-image-1.png?width=470&hash=ae5b590ed0ec6bd943c89ade636ed3bb4f23a439	24990	13270
https://amp.dev/static/img/case-band-image-3.jpg?width=560&hash=104d3cb8772292735d6b30dd42e3af908d95df6f	23850	11250
https://amp.dev/static/img/case-band-image-2.jpg?width=330&hash=33e5e2d61e897ee4dc33b6f74f25fdb7207681f9	14988	6400