9.7 sec in total
224 ms
9.4 sec
155 ms
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.comWe 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
whymicrosoft.com performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value8.8 s
1/100
25%
Value7.1 s
32/100
10%
Value210 ms
89/100
30%
Value0
100/100
15%
Value11.9 s
16/100
10%
224 ms
1923 ms
2058 ms
1190 ms
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 size can be reduced by 1.3 MB (37%)
3.4 MB
2.2 MB
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.
Potential reduce by 77.7 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.
Potential reduce by 47.7 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. Why Microsoft images are well optimized though.
Potential reduce by 869.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 869.8 kB or 74% of the original size.
Potential reduce by 274.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. 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.
Number of requests can be reduced by 57 (79%)
72
15
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.
whymicrosoft.com
224 ms
www.whymicrosoft.com
1923 ms
bootstrap.css
2058 ms
all.css
1190 ms
buttons.css
797 ms
dashicons.css
1266 ms
mediaelementplayer.min.css
1009 ms
wp-mediaelement.css
1416 ms
media-views.css
1280 ms
imgareaselect.css
1519 ms
utils.js
1694 ms
jquery.js
3139 ms
jquery-migrate.js
2099 ms
plupload.full.min.js
2507 ms
filter.js
1861 ms
jquery.min.js
36 ms
jquery.main.js
2480 ms
bootstrap.js
2645 ms
underscore.min.js
2507 ms
shortcode.js
2678 ms
backbone.min.js
3085 ms
wp-util.js
2812 ms
wp-backbone.js
3094 ms
media-models.js
3468 ms
wp-plupload.js
3349 ms
core.min.js
3230 ms
widget.min.js
3401 ms
mouse.min.js
3432 ms
sortable.min.js
3519 ms
mediaelement-and-player.min.js
4002 ms
wp-mediaelement.js
3783 ms
media-views.js
5136 ms
media-editor.js
3938 ms
media-audiovideo.js
3925 ms
wp-embed.js
3783 ms
oct.js
4 ms
wtEaFix.js
4742 ms
html5VideoPlugin.js
4179 ms
conversion.js
17 ms
WhyMS_Icon_Homepage_Productivity-2.svg
250 ms
img19.png
333 ms
share-twitter.svg
2463 ms
share-facebook.svg
2670 ms
share-linkedin.svg
2673 ms
microsoft-footer.png
2672 ms
WhyMS_Icon_Homepage_CloudPlatform.svg
849 ms
WhyMS_Icon_Homepage_BusinessSolutions.svg
720 ms
twemoji.js
3050 ms
wp-emoji.js
2968 ms
segoeuil-webfont.woff
3009 ms
segoeui-webfont.woff
3020 ms
seguisb-webfont.woff
3030 ms
segoeuib-webfont.woff
3550 ms
icomoon.woff
3550 ms
WhyMS_Hero-Images-1.jpg
343 ms
WhyMS_Hero-Images-71.png
1060 ms
WhyMS_Hero-See-Why33.jpg
590 ms
segoeuil-webfont.ttf
1211 ms
segoeui-webfont.ttf
669 ms
seguisb-webfont.ttf
921 ms
analytics.js
28 ms
activityi;src=4754632;type=retar0;cat=whymi0;ord=5580525752156.973
73 ms
adsct
110 ms
adsct
50 ms
gtm.js
50 ms
wtid.js
70 ms
collect
16 ms
collect
64 ms
oct.js
30 ms
ms.js
230 ms
dcs.gif
13 ms
adsct
99 ms
adsct
32 ms
generic
17 ms
pixel
32 ms
11 ms
getid.js
196 ms
munchkin.js
128 ms
146 ms
sprite-bg.png
453 ms
trans_pixel.aspx
79 ms
munchkin.js
14 ms
generic
11 ms
visitWebPage
170 ms
visitWebPage
172 ms
47 ms
c.gif
19 ms
segoeuib-webfont.ttf
1562 ms
icomoon.ttf
754 ms
match
4 ms
whymicrosoft.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
whymicrosoft.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
whymicrosoft.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
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.
whymicrosoft.com
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: