Tools & Wizards About Us
signin.aws screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

signin.aws

Cloud Computing Services - Amazon Web Services (AWS)

Page Load Speed

3.5 sec in total

First Response

15 ms

Resources Loaded

1.5 sec

Page Rendered

1.9 sec

signin.aws screenshot

About Website

Visit signin.aws now to see the best up-to-date Signin content for United States and also check out these interesting facts you probably never knew about signin.aws

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

Visit signin.aws

Key Findings

We analyzed Signin.aws page load time and found that the first response time was 15 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

signin.aws performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value30.2 s

0/100

25%

SI (Speed Index)

Value14.5 s

1/100

10%

TBT (Total Blocking Time)

Value10,400 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.186

66/100

15%

TTI (Time to Interactive)

Value31.6 s

0/100

10%

Network Requests Diagram

signin.aws

15 ms

aws.amazon.com

176 ms

csp-report.js

35 ms

style-awsm-base.css

43 ms

style-awsm-components.css

53 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Signin.aws, 49% (18 requests) were made to A0.awsstatic.com and 38% (14 requests) were made to D1.awsstatic.com. The less responsive or slowest element that took the longest time to load (795 ms) relates to the external source D1.awsstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (17%)

Content Size

7.4 MB

After Optimization

6.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Signin.aws main page is 7.4 MB. 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 a small number of websites need less resources to load. Images take 5.5 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 1.2 MB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 145.1 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 1.2 MB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 24.9 kB

  • Original 5.5 MB
  • After minification 5.5 MB

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. Signin images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 935 B

  • Original 487.8 kB
  • After minification 487.8 kB
  • After compression 486.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 108 B

  • Original 88.7 kB
  • After minification 88.7 kB
  • After compression 88.6 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. Signin.aws has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (41%)

Requests Now

29

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

signin.aws

signin.aws

15 ms

aws.amazon.com

aws.amazon.com

176 ms

csp-report.js

csp-report.js

35 ms

style-awsm-base.css

style-awsm-base.css

43 ms

style-awsm-components.css

style-awsm-components.css

53 ms

es-module-shims.js

es-module-shims.js

48 ms

libra-head.js

libra-head.js

74 ms

awshome_s_code.js

awshome_s_code.js

96 ms

d2c-load.js

d2c-load.js

45 ms

aws-da.js

aws-da.js

74 ms

orchestrate.css

orchestrate.css

47 ms

orchestrate.js

orchestrate.js

267 ms

aws-target-mediator.js

aws-target-mediator.js

268 ms

panorama-nav-init.js

panorama-nav-init.js

44 ms

loader.js

loader.js

240 ms

w42y24_Cutsomer_Slot-3_Gartner-CAIDS.d8a636def2d554d9a21da6e8ba5a70abb085fe48.png

w42y24_Cutsomer_Slot-3_Gartner-CAIDS.d8a636def2d554d9a21da6e8ba5a70abb085fe48.png

795 ms

w40y24_Customer_Slot-2_Amazon-Bedrock.4bd2cef060f47c88c2490ad41036048f9ca3dd2e.png

w40y24_Customer_Slot-2_Amazon-Bedrock.4bd2cef060f47c88c2490ad41036048f9ca3dd2e.png

691 ms

w41y24_Customer_Slot-2_Generative-AI.7f1eceb37c7deb5071f0cd008672b64408ddada5.png

w41y24_Customer_Slot-2_Generative-AI.7f1eceb37c7deb5071f0cd008672b64408ddada5.png

686 ms

w40y24_Customer_Slot-3_Amazon-Q_Business.14c31157322e2e91e532c68f500e27e7d31df39e.png

w40y24_Customer_Slot-3_Amazon-Q_Business.14c31157322e2e91e532c68f500e27e7d31df39e.png

684 ms

w40y24_Customer_Slot-1_Reinvent.63438fb6e11ce97c146e0944201e80bb7ae52d18.png

w40y24_Customer_Slot-1_Reinvent.63438fb6e11ce97c146e0944201e80bb7ae52d18.png

684 ms

2024_reInvent_Site-Merch_Logo.222e0c5759575d5502a3293e551aaa5ad375ca9d.png

2024_reInvent_Site-Merch_Logo.222e0c5759575d5502a3293e551aaa5ad375ca9d.png

624 ms

aws_smile-header-desktop-en-white_59x35.png

aws_smile-header-desktop-en-white_59x35.png

622 ms

AmazonEmberDisplay_Lt.ttf

AmazonEmberDisplay_Lt.ttf

609 ms

AmazonEmberDisplay_He.ttf

AmazonEmberDisplay_He.ttf

608 ms

AmazonEmber_Rg.woff

AmazonEmber_Rg.woff

197 ms

AmazonEmber_Bd.woff

AmazonEmber_Bd.woff

197 ms

tnc-skillbuilder-background3.79bd330408975145348174037541236c7f2a9bb6.png

tnc-skillbuilder-background3.79bd330408975145348174037541236c7f2a9bb6.png

205 ms

Industry-Finance_Studio-401_1200.7528e7bcf6728f8654a8528073fc3f15a21e3891.jpg

Industry-Finance_Studio-401_1200.7528e7bcf6728f8654a8528073fc3f15a21e3891.jpg

201 ms

Genai_main_P2genaitoolseverybiz_square_large.ebe310a2802c5c65a0dd7ab86561b3afa862e4d2.jpg

Genai_main_P2genaitoolseverybiz_square_large.ebe310a2802c5c65a0dd7ab86561b3afa862e4d2.jpg

200 ms

customer-stories-homepage-image.10f5f80e8be439a8bb8e7341db44b3fa8d9756ef.jpg

customer-stories-homepage-image.10f5f80e8be439a8bb8e7341db44b3fa8d9756ef.jpg

140 ms

AmazonEmber_Lt.woff

AmazonEmber_Lt.woff

62 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

62 ms

HOME_Next_Analyst-Reports2.914c4fb9b0d9aeb471bed80eff05a647d2442a9f.png

HOME_Next_Analyst-Reports2.914c4fb9b0d9aeb471bed80eff05a647d2442a9f.png

16 ms

HOME_Next_Marketplace.a50fc6d00cab4ac0127dc73e10ff1e53737a8423.jpg

HOME_Next_Marketplace.a50fc6d00cab4ac0127dc73e10ff1e53737a8423.jpg

108 ms

HOME_Next_Partners.b0ff0807a1c9cfc517e19ae179f61ceeb244b4a1.jpg

HOME_Next_Partners.b0ff0807a1c9cfc517e19ae179f61ceeb244b4a1.jpg

109 ms

HOME_Next_Builders-Library2.47ae9050f88e8f59a887709b3c338f5804e1e248.jpg

HOME_Next_Builders-Library2.47ae9050f88e8f59a887709b3c338f5804e1e248.jpg

108 ms

fontawesome.css

fontawesome.css

73 ms

Accessibility Review

signin.aws accessibility score

59

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

High

button, link, and menuitem elements 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.

High

[role]s are not contained by their required parent element

High

[role] values are not valid

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

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

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

signin.aws 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

signin.aws SEO score

89

Search Engine Optimization Advices

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 Signin.aws 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 Signin.aws 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

signin.aws

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