Tools & Wizards About Us
microsoft.live.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

microsoft.live.com

Microsoft Outlook (formerly Hotmail): Free email and calendar | Microsoft 365

Page Load Speed

840 ms in total

First Response

119 ms

Resources Loaded

632 ms

Page Rendered

89 ms

microsoft.live.com screenshot

About Website

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

Sign in to your Outlook.com, Hotmail.com, MSN.com or Live.com account. Download the free desktop and mobile app to connect all your email accounts, including Gmail, Yahoo, and iCloud, in one place.

Visit microsoft.live.com

Key Findings

We analyzed Microsoft.live.com page load time and found that the first response time was 119 ms and then it took 721 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

microsoft.live.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.154

75/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

119 ms

login.srf

78 ms

legacy-polyfill_gkSLb4SCwW2mK1CiSkJv1A2.js

150 ms

login_en_uUOwd3YLall49Tk7iIh1aA2.js

181 ms

oneds-analytics-js_077217740c853b5d4fe8.js

123 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Microsoft.live.com, 14% (1 request) were made to Outlook.live.com and 14% (1 request) were made to Login.live.com. The less responsive or slowest element that took the longest time to load (181 ms) relates to the external source Logincdn.msauth.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 18.4 kB (5%)

Content Size

344.4 kB

After Optimization

326.0 kB

  • HTML
  • JavaScript

In fact, the total size of Microsoft.live.com main page is 344.4 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. Javascripts take 313.9 kB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 18.3 kB

  • Original 30.5 kB
  • After minification 30.1 kB
  • After compression 12.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 18.3 kB or 60% of the original size.

JavaScript Optimization

-0%

Potential reduce by 73 B

  • Original 313.9 kB
  • After minification 313.9 kB
  • After compression 313.8 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.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

  • Images
  • JavaScript

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Microsoft Live. According to our analytics all requests are already optimized.

Network Requests Diagram

119 ms

login.srf

login.srf

78 ms

legacy-polyfill_gkSLb4SCwW2mK1CiSkJv1A2.js

legacy-polyfill_gkSLb4SCwW2mK1CiSkJv1A2.js

150 ms

login_en_uUOwd3YLall49Tk7iIh1aA2.js

login_en_uUOwd3YLall49Tk7iIh1aA2.js

181 ms

oneds-analytics-js_077217740c853b5d4fe8.js

oneds-analytics-js_077217740c853b5d4fe8.js

123 ms

microsoft_logo_ee5c8d9fb6248c938fd0.svg

microsoft_logo_ee5c8d9fb6248c938fd0.svg

44 ms

2_bc3d32a696895f78c19d.svg

2_bc3d32a696895f78c19d.svg

45 ms

Accessibility Review

microsoft.live.com accessibility score

73

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

[role] values are not valid

High

[aria-*] attributes do not have valid values

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements 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

Form elements do not have associated labels

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

microsoft.live.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

microsoft.live.com SEO score

86

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

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

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 Microsoft.live.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 Microsoft.live.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

microsoft.live.com

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