Tools & Wizards About Us

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

amazonecho.com

All-new Echo (4th Gen) | With premium sound, smart home hub, and Alexa | Charcoal

Page Load Speed

488 ms in total

First Response

163 ms

Resources Loaded

325 ms

Page Rendered

0 ms

About Website

Click here to check amazing Amazon Echo content. Otherwise, check out these important facts you probably never knew about amazonecho.com

New look, new sound - Echo delivers clear highs, dynamic mids, and deep bass for rich, detailed sound that automatically adapts to any room.

Visit amazonecho.com

Key Findings

We analyzed Amazonecho.com page load time and found that the first response time was 163 ms and then it took 325 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

amazonecho.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value10.5 s

8/100

10%

TBT (Total Blocking Time)

Value4,830 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value23.2 s

1/100

10%

Network Requests Diagram

amazonecho.com

163 ms

2iIrACh

28 ms

ref=as_li_ss_tl

37 ms

AmazonUI-3c913031596ca78a3768f4e934b1cc02ce238101.secure.min._V1_.css

41 ms

requestId=MNTYNYCHR488EZXGWTQ0&js=1

22 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 9% of them (1 request) were addressed to the original Amazonecho.com, 64% (7 requests) were made to Images-na.ssl-images-amazon.com and 9% (1 request) were made to Amzn.to. The less responsive or slowest element that took the longest time to load (163 ms) belongs to the original domain Amazonecho.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 6.6 kB (10%)

Content Size

67.1 kB

After Optimization

60.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Amazonecho.com main page is 67.1 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. Only 10% of websites need less resources to load. CSS take 23.2 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 5.4 kB

  • Original 7.4 kB
  • After minification 5.4 kB
  • After compression 2.0 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. This page needs HTML code to be minified as it can gain 2.0 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 5.4 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 110 B

  • Original 22.8 kB
  • After minification 22.6 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. Amazon Echo images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 1.1 kB

  • Original 13.8 kB
  • After minification 13.8 kB
  • After compression 12.7 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.

CSS Optimization

-0%

Potential reduce by 14 B

  • Original 23.2 kB
  • After minification 23.2 kB
  • After compression 23.1 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Amazonecho.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 3 (38%)

Requests Now

8

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

amazonecho.com accessibility score

79

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

amazonecho.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Missing source maps for large first-party JavaScript

SEO Factors

amazonecho.com SEO score

68

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 Amazonecho.com 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 Amazonecho.com 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

Open Graph description is not detected on the main page of Amazon Echo. 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: