1.3 sec in total
126 ms
952 ms
215 ms
Click here to check amazing Portal Office content for United States. Otherwise, check out these important facts you probably never knew about portal.office.com
Visit portal.office.comWe analyzed Portal.office.com page load time and found that the first response time was 126 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
portal.office.com performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value5.2 s
24/100
25%
Value5.3 s
59/100
10%
Value320 ms
77/100
30%
Value0.068
96/100
15%
Value5.1 s
76/100
10%
126 ms
90 ms
108 ms
177 ms
248 ms
Our browser made a total of 11 requests to load all elements on the main page. We found that 18% of them (2 requests) were addressed to the original Portal.office.com, 73% (8 requests) were made to Secure.aadcdn.microsoftonline-p.com and 9% (1 request) were made to Login.microsoftonline.com. The less responsive or slowest element that took the longest time to load (346 ms) relates to the external source Secure.aadcdn.microsoftonline-p.com.
Page size can be reduced by 243.7 kB (74%)
330.0 kB
86.2 kB
In fact, the total size of Portal.office.com main page is 330.0 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. 15% of websites need less resources to load. Javascripts take 271.7 kB which makes up the majority of the site volume.
Potential reduce by 27.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. This page needs HTML code to be minified as it can gain 4.4 kB, which is 12% 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 27.7 kB or 78% of the original size.
Potential reduce by 248 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, Portal Office needs image optimization as it can save up to 248 B or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 198.7 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 198.7 kB or 73% of the original size.
Potential reduce by 17.1 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. Portal.office.com needs all CSS files to be minified and compressed as it can save up to 17.1 kB or 79% of the original size.
Number of requests can be reduced by 3 (50%)
6
3
The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Portal Office. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
portal.office.com
126 ms
portal.office.com
90 ms
login.srf
108 ms
login_ltr.min.css
177 ms
jquery-1.11.2.min.js
248 ms
jquery-migrate-1.2.1.min.js
286 ms
jquery.easing.1.3.js
312 ms
aad.login.min.js
346 ms
microsoft_logo.png
69 ms
bannerlogo
39 ms
heroillustration
181 ms
portal.office.com accessibility score
portal.office.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
portal.office.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Portal.office.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 Portal.office.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.
portal.office.com
Open Graph description is not detected on the main page of Portal Office. 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: