Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

azure.com

Cloud Computing Services | Microsoft Azure

Page Load Speed

3.3 sec in total

First Response

69 ms

Resources Loaded

2.7 sec

Page Rendered

475 ms

azure.com screenshot

About Website

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

Invent with purpose, realize cost savings, and make your organization more efficient with Microsoft Azure’s open and flexible cloud computing platform.

Visit azure.com

Key Findings

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

Performance Metrics

azure.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value2,410 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

azure.com

69 ms

294 ms

home.css

246 ms

jquery-2.1.4.min.js

272 ms

home.js

344 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Azure.com, 29% (14 requests) were made to Acom.azurecomcdn.net and 19% (9 requests) were made to Azure.microsoft.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Azure.microsoft.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 356.0 kB (32%)

Content Size

1.1 MB

After Optimization

741.0 kB

In fact, the total size of Azure.com main page is 1.1 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. 35% of websites need less resources to load. Images take 586.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 293.1 kB

  • Original 373.3 kB
  • After minification 373.0 kB
  • After compression 80.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 293.1 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 586.5 kB
  • After minification 586.5 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. Azure images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 62.9 kB

  • Original 137.2 kB
  • After minification 137.2 kB
  • After compression 74.3 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 62.9 kB or 46% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (55%)

Requests Now

40

After Optimization

18

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

Accessibility Review

azure.com accessibility score

100

Accessibility Issues

Best Practices

azure.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

azure.com SEO score

99

Search Engine Optimization Advices

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 Azure.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 Azure.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 data is detected on the main page of Azure. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: