Tools & Wizards About Us

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

whymicrosoft.com

Technologies for Hybrid & Flexible Work | Microsoft Flexibility

Page Load Speed

9.7 sec in total

First Response

224 ms

Resources Loaded

9.4 sec

Page Rendered

155 ms

About Website

Welcome to whymicrosoft.com homepage info - get ready to check Why Microsoft best content for United States right away, or after learning these important things about whymicrosoft.com

Discover technologies that enable flexibility in the workplace. Use Microsoft technologies to empower digital, remote, hybrid, and flexible working solutions.

Visit whymicrosoft.com

Key Findings

We analyzed Whymicrosoft.com page load time and found that the first response time was 224 ms and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster. This domain responded with an error, which can significantly jeopardize Whymicrosoft.com rating and web reputation

Performance Metrics

whymicrosoft.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value7.1 s

32/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.9 s

16/100

10%

Network Requests Diagram

whymicrosoft.com

224 ms

www.whymicrosoft.com

1923 ms

bootstrap.css

2058 ms

all.css

1190 ms

buttons.css

797 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 59% of them (53 requests) were addressed to the original Whymicrosoft.com, 4% (4 requests) were made to Whyms.blob.core.windows.net and 3% (3 requests) were made to Whyms.trafficmanager.net. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Whymicrosoft.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (36%)

Content Size

3.4 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whymicrosoft.com main page is 3.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. 45% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 77.7 kB

  • Original 97.3 kB
  • After minification 92.9 kB
  • After compression 19.6 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 77.7 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 47.7 kB

  • Original 1.8 MB
  • After minification 1.8 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. Why Microsoft images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 837.8 kB

  • Original 1.1 MB
  • After minification 853.3 kB
  • After compression 298.1 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 837.8 kB or 74% of the original size.

CSS Optimization

-80%

Potential reduce by 274.0 kB

  • Original 342.8 kB
  • After minification 277.6 kB
  • After compression 68.8 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. Whymicrosoft.com needs all CSS files to be minified and compressed as it can save up to 274.0 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (79%)

Requests Now

72

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

whymicrosoft.com accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

whymicrosoft.com SEO score

84

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whymicrosoft.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Whymicrosoft.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 Why Microsoft. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: