59.7 sec in total
9.1 sec
47.5 sec
3.1 sec
Welcome to o365.com homepage info - get ready to check O 365 best content right away, or after learning these important things about o365.com
Microsoft 365 subscriptions include a set of familiar Office apps, intelligent cloud services, and world-class security in one place. Find the right plan for you.
Visit o365.comWe analyzed O365.com page load time and found that the first response time was 9.1 sec and then it took 50.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 20 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
o365.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value16.6 s
0/100
25%
Value14.2 s
1/100
10%
Value19,140 ms
0/100
30%
Value0.291
41/100
15%
Value34.8 s
0/100
10%
9147 ms
8195 ms
8027 ms
8271 ms
8372 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original O365.com, 15% (9 requests) were made to C.s-microsoft.com and 6% (4 requests) were made to Query.prod.cms.rt.microsoft.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Microsoft.com.
Page size can be reduced by 256.6 kB (68%)
374.7 kB
118.1 kB
In fact, the total size of O365.com main page is 374.7 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. 65% of websites need less resources to load. HTML takes 297.4 kB which makes up the majority of the site volume.
Potential reduce by 254.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. This page needs HTML code to be minified as it can gain 49.1 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 254.6 kB or 86% of the original size.
Potential reduce by 493 B
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. O 365 images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 210 B
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. O365.com has all CSS files already compressed.
Number of requests can be reduced by 23 (79%)
29
6
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of O 365. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
microsoft-365
9147 ms
microsoft-365
8195 ms
main-m365.min.ACSHASHc00d27236641b363e8e714e65efad902.css
8027 ms
main-m365.min.ACSHASHefdad90e6c206b62cbc7b06d8fa92156.css
8271 ms
clientlib-base.min.ACSHASH50628e34bba9f2b65078edc419e409b3.css
8372 ms
clientlib-events.min.ACSHASH7344ea3f173fdfa77c63bae1fed1c87d.js
10026 ms
clientlib-uhf.min.ACSHASHf9f2395c582fa601707b7a5dfae9f05f.css
9037 ms
clientlib-polyfills.min.ACSHASH87340f968f85ec162e195e5217994ae7.js
8269 ms
clientlib-jquery.min.ACSHASHb1168f0ce867875996c28ca9e8b4949b.js
17056 ms
clientlib-jquery-cookie.min.ACSHASHa67d659f582bf93e1d8156fc182326f5.js
16049 ms
jsll-4.js
36 ms
v1.min.ACSHASHd825183b3614c7a5dca53474beaec39e.js
16048 ms
v1.min.ACSHASH3007ee72081412fbd8b665a01afb7cad.js
16047 ms
RE1r2ij
188 ms
RE4OFm4
190 ms
RE4OxzH
207 ms
ef-a24652
19053 ms
override.css
121 ms
site.min.ACSHASH0df7fef27e9de44acae5b384a20f2542.js
18037 ms
site.min.ACSHASH7c34475ccd4fb5689f833f1255874583.css
20474 ms
site.min.ACSHASHb50eba9660b82459945c8a91d7b72956.js
20486 ms
site.min.ACSHASHcced67ac82867a5838572397f6cfd860.js
20525 ms
site.min.ACSHASH584107f1c2463f8acd905ecfa4ff5668.js
20525 ms
site.min.ACSHASH63751b2b6b6ef967be64041d603e906b.js
20524 ms
site.min.ACSHASH1d326b6a71c2dac6e3e8786d8499eb1e.js
20525 ms
wcp-consent.js
66 ms
37-8473b9
20528 ms
meversion
60 ms
main-light.min.ACSHASHf482e47f46fb33d80b20334060534d1c.js
20528 ms
main-m365.min.ACSHASH8f221b389bde729c5cac68dac6172b13.js
20532 ms
clientlib-base.min.ACSHASHa33966d73000d09955689b5a01aa29d5.js
20532 ms
clientlib-site.min.ACSHASH4c1f1c6a4ff877c820e56e5ab869262b.js
20532 ms
clientlib-httpclient.min.ACSHASH150d43657fba310deba9e52fffb151f3.js
20532 ms
clientlib-cookieconsent.min.ACSHASHc892f451b0c4db9c8ab2601a427c9b2c.js
20536 ms
clientlib-cookievalidator.min.ACSHASH57e17bc5d041e292fab3625ef861658a.js
20536 ms
featurecontrol.min.ACSHASHf120033122e43a4cb0b53bb306afc5dc.js
20537 ms
custom-oneds.min.ACSHASH5e3bdd09b4ded66c549038bde6fbc184.js
20537 ms
RE4OCI2
203 ms
clientlib-chat.min.ACSHASHfa6f56b2d3037982772378233706c9af.css
20541 ms
clientlib-chat.min.ACSHASHd28f58ccba8e55ad3c2eef33911b7929.js
20541 ms
clientlib-market-layer.min.ACSHASH52cb8441e33acc0de9f858216525fc58.js
20541 ms
clientlib-greenid.min.ACSHASH44a811225ab0a12502f646d624dede72.js
20541 ms
ie11-polyfills.js
18692 ms
RE1Mu3b
336 ms
LinkedIn-29
243 ms
Twitter-34
255 ms
Blog
257 ms
latest.woff
179 ms
latest.woff
200 ms
latest.woff
244 ms
latest.woff
244 ms
latest.woff
244 ms
latest.woff
242 ms
latest.woff
243 ms
latest.woff
222 ms
latest.woff
243 ms
mwfmdl2-v3.54.woff
10283 ms
MWFUISymbol.woff
8619 ms
launch-41185cd0b005.min.js
415 ms
RCbec314109be34962999dbad4041375a8-source.min.js
25 ms
RCb827b2d874d8436fa48a7c19baf01bf1-source.min.js
12 ms
RC3845794034964e32934c4dad4bdff728-source.min.js
10 ms
o365.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
o365.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
o365.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise O365.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 O365.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.
o365.com
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: