5.3 sec in total
348 ms
4.5 sec
515 ms
Welcome to resources.office.com homepage info - get ready to check Resources Office best content for United States right away, or after learning these important things about resources.office.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 resources.office.comWe analyzed Resources.office.com page load time and found that the first response time was 348 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
resources.office.com performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value20.0 s
0/100
25%
Value20.4 s
0/100
10%
Value38,260 ms
0/100
30%
Value0.291
41/100
15%
Value55.0 s
0/100
10%
348 ms
766 ms
71 ms
148 ms
165 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Resources.office.com, 61% (36 requests) were made to Microsoft.com and 15% (9 requests) were made to C.s-microsoft.com. The less responsive or slowest element that took the longest time to load (822 ms) relates to the external source Img-prod-cms-rt-microsoft-com.akamaized.net.
Page size can be reduced by 219.2 kB (73%)
301.8 kB
82.6 kB
In fact, the total size of Resources.office.com main page is 301.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 233.6 kB which makes up the majority of the site volume.
Potential reduce by 208.0 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 21% 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 208.0 kB or 89% 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. Resources Office images are well optimized though.
Potential reduce by 433 B
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 10.3 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. Resources.office.com needs all CSS files to be minified and compressed as it can save up to 10.3 kB or 78% of the original size.
Number of requests can be reduced by 40 (87%)
46
6
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Resources 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 33 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
resources.office.com
348 ms
microsoft-365
766 ms
main-m365.min.ACSHASHc00d27236641b363e8e714e65efad902.css
71 ms
main-m365.min.ACSHASHefdad90e6c206b62cbc7b06d8fa92156.css
148 ms
clientlib-base.min.ACSHASH50628e34bba9f2b65078edc419e409b3.css
165 ms
clientlib-events.min.ACSHASH7344ea3f173fdfa77c63bae1fed1c87d.js
147 ms
clientlib-uhf.min.ACSHASHf9f2395c582fa601707b7a5dfae9f05f.css
147 ms
clientlib-polyfills.min.ACSHASH87340f968f85ec162e195e5217994ae7.js
221 ms
clientlib-jquery.min.ACSHASHb1168f0ce867875996c28ca9e8b4949b.js
163 ms
clientlib-jquery-cookie.min.ACSHASHa67d659f582bf93e1d8156fc182326f5.js
286 ms
jsll-4.js
283 ms
v1.min.ACSHASHd825183b3614c7a5dca53474beaec39e.js
258 ms
v1.min.ACSHASH3007ee72081412fbd8b665a01afb7cad.js
257 ms
RE1r2ij
531 ms
RE4OFm4
538 ms
RE4OxzH
536 ms
ef-a24652
278 ms
override.css
479 ms
site.min.ACSHASH0df7fef27e9de44acae5b384a20f2542.js
246 ms
site.min.ACSHASH7c34475ccd4fb5689f833f1255874583.css
268 ms
site.min.ACSHASHb50eba9660b82459945c8a91d7b72956.js
269 ms
site.min.ACSHASHcced67ac82867a5838572397f6cfd860.js
265 ms
site.min.ACSHASH584107f1c2463f8acd905ecfa4ff5668.js
266 ms
site.min.ACSHASH63751b2b6b6ef967be64041d603e906b.js
439 ms
site.min.ACSHASH1d326b6a71c2dac6e3e8786d8499eb1e.js
437 ms
wcp-consent.js
386 ms
37-8473b9
425 ms
meversion
386 ms
main-light.min.ACSHASHf482e47f46fb33d80b20334060534d1c.js
424 ms
main-m365.min.ACSHASH8f221b389bde729c5cac68dac6172b13.js
423 ms
clientlib-base.min.ACSHASHa33966d73000d09955689b5a01aa29d5.js
423 ms
clientlib-site.min.ACSHASH4c1f1c6a4ff877c820e56e5ab869262b.js
493 ms
clientlib-httpclient.min.ACSHASH150d43657fba310deba9e52fffb151f3.js
492 ms
clientlib-cookieconsent.min.ACSHASHc892f451b0c4db9c8ab2601a427c9b2c.js
491 ms
clientlib-cookievalidator.min.ACSHASH57e17bc5d041e292fab3625ef861658a.js
491 ms
featurecontrol.min.ACSHASHf120033122e43a4cb0b53bb306afc5dc.js
492 ms
custom-oneds.min.ACSHASH5e3bdd09b4ded66c549038bde6fbc184.js
497 ms
RE4OCI2
729 ms
clientlib-chat.min.ACSHASHfa6f56b2d3037982772378233706c9af.css
725 ms
clientlib-chat.min.ACSHASHd28f58ccba8e55ad3c2eef33911b7929.js
726 ms
clientlib-market-layer.min.ACSHASH52cb8441e33acc0de9f858216525fc58.js
724 ms
clientlib-greenid.min.ACSHASH44a811225ab0a12502f646d624dede72.js
727 ms
ie11-polyfills.js
548 ms
RE1Mu3b
822 ms
LinkedIn-29
299 ms
Twitter-34
746 ms
Blog
820 ms
latest.woff
293 ms
latest.woff
293 ms
latest.woff
754 ms
latest.woff
756 ms
latest.woff
755 ms
latest.woff
774 ms
latest.woff
758 ms
latest.woff
756 ms
latest.woff
755 ms
mwfmdl2-v3.54.woff
72 ms
MWFUISymbol.woff
67 ms
launch-41185cd0b005.min.js
87 ms
resources.office.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
resources.office.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
resources.office.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 Resources.office.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 Resources.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.
resources.office.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: