Tools & Wizards About Us
amp.watch screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 72

    SEO

    Google-friendlier than
    31% of websites

amp.watch

Internet Live Stats - Internet Usage & Social Media Statistics

Page Load Speed

2.3 sec in total

First Response

69 ms

Resources Loaded

1.8 sec

Page Rendered

393 ms

amp.watch screenshot

About Website

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

Watch the Internet as it grows in real time and monitor social media usage: Internet users, websites, blog posts, Facebook, Google+, Twitter, and Pinterest users. Visualize the total number of emails,...

Visit amp.watch

Key Findings

We analyzed Amp.watch page load time and found that the first response time was 69 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

amp.watch performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

57/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value5,450 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

amp.watch

69 ms

hEyGpfiM47d

193 ms

rs=AGLTcCO4gwoK4kDD7rdBZUcs4Jl0rrq9Dw

61 ms

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

306 ms

rs=AGLTcCMwttuGQh16blrbkpeMBBylQh07KQ

422 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Amp.watch, 48% (16 requests) were made to Plus.google.com and 18% (6 requests) were made to Lh3.googleusercontent.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 323.1 kB (62%)

Content Size

524.7 kB

After Optimization

201.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Amp.watch main page is 524.7 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. 35% of websites need less resources to load. Javascripts take 431.1 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 41.8 kB

  • Original 58.0 kB
  • After minification 58.0 kB
  • After compression 16.2 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 41.8 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 219 B

  • Original 35.5 kB
  • After minification 35.3 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. Amp images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 281.0 kB

  • Original 431.1 kB
  • After minification 429.9 kB
  • After compression 150.1 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 281.0 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (46%)

Requests Now

28

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 28 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 14 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

amp.watch

amp.watch

69 ms

hEyGpfiM47d

hEyGpfiM47d

193 ms

rs=AGLTcCO4gwoK4kDD7rdBZUcs4Jl0rrq9Dw

rs=AGLTcCO4gwoK4kDD7rdBZUcs4Jl0rrq9Dw

61 ms

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

306 ms

rs=AGLTcCMwttuGQh16blrbkpeMBBylQh07KQ

rs=AGLTcCMwttuGQh16blrbkpeMBBylQh07KQ

422 ms

photo.jpg

photo.jpg

945 ms

photo.jpg

photo.jpg

1095 ms

iLQxzVJgNyzGriUcCAiC_VJ5mXypm-iZIRl1DOgZYmTTAy0-ZyZ6WnP0rTlHkKqPs7Txo5LK-qWhkRyhn3VTX8HJOpJd01NS=w506-h337

iLQxzVJgNyzGriUcCAiC_VJ5mXypm-iZIRl1DOgZYmTTAy0-ZyZ6WnP0rTlHkKqPs7Txo5LK-qWhkRyhn3VTX8HJOpJd01NS=w506-h337

1165 ms

photo.jpg

photo.jpg

1147 ms

photo.jpg

photo.jpg

1223 ms

photo.jpg

photo.jpg

1162 ms

pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf

pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf

992 ms

JcQUq3K39RZrUxrrs7pjpwLUuEpTyoUstqEm5AMlJo4.ttf

JcQUq3K39RZrUxrrs7pjpwLUuEpTyoUstqEm5AMlJo4.ttf

1182 ms

IhuqmeHx65TaW6CiR2l0VALUuEpTyoUstqEm5AMlJo4.ttf

IhuqmeHx65TaW6CiR2l0VALUuEpTyoUstqEm5AMlJo4.ttf

1233 ms

gplus_icon_flatsq_44dp.png

gplus_icon_flatsq_44dp.png

1076 ms

ribbon-nav-1x-7f2ff444a9831b4e82675ae39f1e0a1a.png

ribbon-nav-1x-7f2ff444a9831b4e82675ae39f1e0a1a.png

1122 ms

collections_ribbon_1x-053433a84a2230587831db62f0a4bfc2.png

collections_ribbon_1x-053433a84a2230587831db62f0a4bfc2.png

1231 ms

stream-9d991e56752b6d57f78fa1d4650083b8.png

stream-9d991e56752b6d57f78fa1d4650083b8.png

1198 ms

stream_showroom-d8de88384f6e5817983d0fcec12c128a.png

stream_showroom-d8de88384f6e5817983d0fcec12c128a.png

1197 ms

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

803 ms

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

319 ms

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

320 ms

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

379 ms

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

386 ms

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

340 ms

254 ms

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

205 ms

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

217 ms

cpw-7de38e2bb0.png

cpw-7de38e2bb0.png

129 ms

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

170 ms

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

98 ms

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

129 ms

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

rs=AGLTcCPtWg2c3rPLKud_jFEfOB9nGMfmSQ

73 ms

Accessibility Review

amp.watch accessibility score

72

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-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

amp.watch best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

amp.watch SEO score

72

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not 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 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.watch 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.watch 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.watch

Open Graph data is detected on the main page of Amp. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: