Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

amazonnaws.com

Cloud Computing Services - Amazon Web Services (AWS)

Page Load Speed

4.9 sec in total

First Response

153 ms

Resources Loaded

2.9 sec

Page Rendered

1.8 sec

amazonnaws.com screenshot

About Website

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

Amazon Web Services offers reliable, scalable, and inexpensive cloud computing services. Free to join, pay only for what you use.

Visit amazonnaws.com

Key Findings

We analyzed Amazonnaws.com page load time and found that the first response time was 153 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

amazonnaws.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value22.9 s

0/100

25%

SI (Speed Index)

Value16.1 s

0/100

10%

TBT (Total Blocking Time)

Value18,310 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.1

89/100

15%

TTI (Time to Interactive)

Value36.4 s

0/100

10%

Network Requests Diagram

amazonnaws.com

153 ms

HP04O8

17 ms

aws.amazon.com

8 ms

aws.amazon.com

119 ms

csp-report.js

138 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Amazonnaws.com, 78% (62 requests) were made to D1.awsstatic.com and 18% (14 requests) were made to A0.awsstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source D1.awsstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 309.4 kB (46%)

Content Size

675.3 kB

After Optimization

365.9 kB

In fact, the total size of Amazonnaws.com main page is 675.3 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. 55% of websites need less resources to load. HTML takes 337.6 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 307.3 kB

  • Original 337.6 kB
  • After minification 300.0 kB
  • After compression 30.4 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 37.7 kB, which is 11% 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 307.3 kB or 91% of the original size.

Image Optimization

-1%

Potential reduce by 1.6 kB

  • Original 245.2 kB
  • After minification 243.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 N AWS images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 502 B

  • Original 8.4 kB
  • After minification 8.4 kB
  • After compression 7.9 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 26 B

  • Original 84.0 kB
  • After minification 84.0 kB
  • After compression 84.0 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. Amazonnaws.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 34 (47%)

Requests Now

72

After Optimization

38

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

Accessibility Review

amazonnaws.com accessibility score

87

Accessibility Issues

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.

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>).

Best Practices

amazonnaws.com best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

amazonnaws.com SEO score

75

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 Amazonnaws.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 Amazonnaws.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 N AWS. 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: