533 ms in total
37 ms
427 ms
69 ms
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 37 ms and then it took 496 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
o365.com performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value10.7 s
0/100
25%
Value7.2 s
29/100
10%
Value2,160 ms
6/100
30%
Value0
100/100
15%
Value19.0 s
3/100
10%
37 ms
181 ms
29 ms
101 ms
19 ms
Our browser made a total of 16 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original O365.com, 25% (4 requests) were made to Microsoft.com and 13% (2 requests) were made to Assets.onestore.ms. The less responsive or slowest element that took the longest time to load (181 ms) relates to the external source Assets.onestore.ms.
Page size can be reduced by 601.6 kB (84%)
716.4 kB
114.8 kB
In fact, the total size of O365.com main page is 716.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. 25% of websites need less resources to load. CSS take 563.9 kB which makes up the majority of the site volume.
Potential reduce by 96.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 40.2 kB, which is 38% 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 96.6 kB or 91% 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. Obviously, O 365 needs image optimization as it can save up to 493 B or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 8.6 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 8.6 kB or 21% of the original size.
Potential reduce by 495.9 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. O365.com needs all CSS files to be minified and compressed as it can save up to 495.9 kB or 88% of the original size.
We found no issues to fix!
7
7
The browser has sent 7 CSS, Javascripts, AJAX and image requests in order to completely render the main page of O 365. According to our analytics all requests are already optimized.
{{url}}
{{time}} ms
o365.com accessibility score
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
[aria-*] attributes do not have valid values
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
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
N/A
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 . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
{{og_description}}
o365.com
Open Graph description is not detected on the main page of O 365. 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: