2.7 sec in total
68 ms
2.2 sec
394 ms
Visit office.microsoft.com now to see the best up-to-date Office Microsoft content for United States and also check out these interesting facts you probably never knew about office.microsoft.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 office.microsoft.comWe analyzed Office.microsoft.com page load time and found that the first response time was 68 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
office.microsoft.com performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value11.8 s
0/100
25%
Value14.0 s
1/100
10%
Value19,200 ms
0/100
30%
Value0.302
39/100
15%
Value33.6 s
0/100
10%
68 ms
60 ms
252 ms
171 ms
67 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Office.microsoft.com, 27% (39 requests) were made to C.s-microsoft.com and 11% (16 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (700 ms) relates to the external source Microsoft.com.
Page size can be reduced by 961.2 kB (59%)
1.6 MB
675.4 kB
In fact, the total size of Office.microsoft.com main page is 1.6 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. 65% of websites need less resources to load. CSS take 688.2 kB which makes up the majority of the site volume.
Potential reduce by 77.4 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.4 kB or 76% of the original size.
Potential reduce by 57.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. Obviously, Office Microsoft needs image optimization as it can save up to 57.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 219.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 219.8 kB or 57% of the original size.
Potential reduce by 606.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. Office.microsoft.com needs all CSS files to be minified and compressed as it can save up to 606.3 kB or 88% of the original size.
Number of requests can be reduced by 97 (74%)
131
34
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Office 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 42 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
office.microsoft.com
68 ms
products.office.com
60 ms
252 ms
jquery-1.11.3.min.js
171 ms
Bootstrap.js
67 ms
wt.js
63 ms
style.csx
64 ms
style.csx
71 ms
style.csx
72 ms
style.csx
73 ms
style.csx
76 ms
style.csx
75 ms
style.csx
75 ms
style.csx
78 ms
style.csx
76 ms
script.jsx
82 ms
ms.js
543 ms
kjBREBZX.min.js
170 ms
microsoft.png
155 ms
Logo_Office_76x24.png
73 ms
Logo_Office_Orange_76x24.png
54 ms
fallback_icon_chevron.png
55 ms
Hero_ProductsHP_1920x760.jpg
58 ms
CTA_Arrow_White_19x19.png
54 ms
Image_BuiltForTeamwork_370x228.png
54 ms
Image_Windows10_440x300.png
62 ms
Image_WorksForYou_370x111.png
56 ms
PlayButton_135x135.png
56 ms
Image_VideoPromo_1600x450.jpg
108 ms
pmg-close-orange.PNG.png
56 ms
pmg-blue-arrow.png
59 ms
Icon_WindowsPhone_40x82.png
61 ms
Icon_AndroidPhone_40x78.png
57 ms
Icon_iPhone_33x69.png
93 ms
Icon_WindowsTablet_94x60.png
95 ms
Icon_AndroidTablet_85x62.png
96 ms
Icon_iPad_84x59.png
97 ms
Icon_PC_116x81.png
99 ms
Icon_Mac_99x82.png
98 ms
windows_symbol.png
99 ms
surface_symbol.png
100 ms
windowsphone_symbol.png
103 ms
xbox_symbol.png
101 ms
skype_symbol.png
102 ms
Logo_MSN_24x24.png
103 ms
bing_symbol.png
103 ms
store_symbol.png
104 ms
globe_icon.png
105 ms
serverComponent.php
105 ms
sizzle.min.js
47 ms
optimize.js
51 ms
sdk.js
291 ms
latest.woff
96 ms
latest.woff
170 ms
latest.woff
246 ms
latest.woff
224 ms
latest.woff
253 ms
ip.json
66 ms
pixel
146 ms
WT3B--g843TZV8t1CnDzONPdKpuHYI936OJnDbln9tKyWbQ4NkiumiRcLcDNmdObziDArKAYsxuR2449LSJ0J-sLq0A7QUbGO75w26_Maq8oaAuufvDEq84YQRMkuxWj3Vq08ozvEwdmGRe1MR-d7iKWUK1m8NAuppypjB0nd1f41qsUy1Y6_AJ1lhmA0baWOry3Brnc2nSNrrUfAfwZ_dajJ5c_pRb0hPvYFDcr0v9u8tjGljM-WkVD68lwrgwk0M5fT_a1WdbUncBq05Y8m-sSlJ2y6zBV7hV4MCo560Z5-bDW3ES-_QeFlqRxyZ5KoMznvzxrzpJ19gEsF5mEptPxhaGssqv262BEgI5Y0jzST_vAr-BfTsyPBbXfErM3JJiRUwtc8OWY5F6fWm-6TrwwGfQXzIpfAQTsiq2lBIarJB84xYJ5OFx801T26CIL4lfqvmy3Ul1uBZeLVg63MI_g0xoe3o16AY_u4gFRbpQ5aSLCGFhAoW5y2BedHGgyd2lq6Ry51ANEqu80U8m49C7gGVRIzSvU7pIzDEoO_Dq3ipBAZd0HPW0W0KKVCdVze9PFnTdLvK01BTPETZOL3ozs0S9jgSkxQSCeq-PqpktIR2U7tf1_w_BOvxQimKxD-WXjzL8_lpIAyToGmL8SZN0gVgAWILFmohFQ534VbUYGxs_pehexGFqghqRi6L8jDqHc10JkIFNPxdch64KYybxeMKybNjUUBByInvTGCKk9NNhSlMo5s0xOXdI3FcI8Hn0ecU0EZ739WoMQCLBTqknithJ4UJwVW5lPxVSCMrm5rwZFsoYEB5dloh70pNMXslkIsIfebDcHIx484o1f6agoh4-wFBHsVNKqP-1aVUkD9M6Vt2zUOhs3zG53JNSZSZJSomCRY6zpMc1AYqHr-Uknw329Dh5_jDNUdAVHP0irOcHU8J9RGCSlvmNK-3LTM-kajk8qgOrUq-z6M4sN_pDz77h_ZpLqH6r_vFkjeMJq67hmJjXdRCz6_Qeetqjcfcdwkxvhj4xBnke4UgQ-JxeZBcfk7fk0cSPjFWvLdNG-27mZmjMAKKGJvtIZEitSafv-_T3VI7giutt5SPVGFnugB1Y9kg1RJLWUL6vcafUIxRFxgEGJePKvdYcKtXjJuhdTFtiW58NfeHc-9mnzV24gq-xeltSAbf-V8bupO5jiO5c92glHPzbfm5eSJ9COU5A7RUOb-rUyjlx3t8fUDTiPzT0Jxxn3CuL7jZOoHxVJ4BajkclM24qrP3d6SR2ixxVBDmjwIhS_463clMhEAByQ-pFqR0GUaZcLzye-ARs5tws92OyOTMplcwHROUH4fjrAteWetaJCfkpTrnQpONEu5yRWzaGpic_vyhr1MZdu69UV_efRV41QZMKeIfpe7c-4fyCEJMLML9d8XYraNwayAVr7XiXVkTM4sreRtzrUjX_tZgfUQiH2XDWAB5wfsmDxmhu0MkDPmULU9DlC86QXjlMclZ7wZ32wSJpohUpwuopiAd7JfV15-FVVJf2fUvfxDTWUpPbwoIbdpJuw6gENO70cVOWr_w8vuwPX99VjDSoWSqHjnOONw2FAPIFJApcI2_FFiiThetuL9xLyt4UEyoAtIWvXY7IEei9m2MUp5UwDnX1y4tWvjgj-xAp9H3_fNZtDhUd4eXPtKEK3iNJP8sH2nsiroNhNCUZNpSDrQ2n3ozCg8Y3M1rqdaU8mqy6vBbhRd3n-SPhbq8G4MPyC6b3iBHkgFzzolv-ro6C6GmR6pbVKJZoGXZ2H_UZkKOY7tuyBarZeHIn_eKHJM_kUiTTf8gk8H3KL7T87BAjddFZAfMKE6W77TG8QG2_H8FamUTvfT-0DYte8BUGKy3DlNkSHSDY0UOAuzPmVLkWmI0TIIV0Ti2lmQnl76NvQpybBd4rgLOoPUD2SaqSczBK5fcbO8pzXiX6QtavcEx04T-30Qa76mhlR4zdBJwDSpLF0GFCgcRr0_Z5xlCsEH45SbLH5VsR79ue4dN5ab_QGoiIrWvsrvh0-00DEe1cbdB8-wYoxNO4x__T_LXOxOKG6EDIDdnPA-h2ejR-oMuV6sE3xfFrcYHRoFjsSfanomWPTMKYuYNFbfBd5IwsXQ853sDDVL7oAKJJ3MTrcGAMa96LJQD1kwEkeqbBPzywN3wKmYAXF-RmoFD5pf5fApN1N1icncVdqFbmUU4jF23QKeKoLRc59p8i8RYREcWGyWC0lASoqZxaEq_dAC28U2fgFw~~
288 ms
e807b654590e53bbd2868e08601b66ab.js
20 ms
efaede16292729e1049a780034cbc813.js
96 ms
1080edf88ec19c233a6d4729c9e2828d.js
170 ms
08b9029a626c60768dba6bf512e96d65.js
205 ms
fe45152b7f5bf7c05e3678d1a52db9f2.js
268 ms
1a5f489071f17eb5d52bbed1457a8169.js
203 ms
ff5d44f21cb7f4b9e3c9ef45ad20cef3.js
204 ms
cb1c8739d747e5c9c83d7628883b7e00.js
202 ms
15f45229b12fc5a55c38702ef101181c.js
204 ms
pixel
126 ms
getid.js
414 ms
PMGC2CGlobalConfig.js
700 ms
trans_pixel.aspx
123 ms
oct.js
122 ms
oct.js
127 ms
ld.js
278 ms
fbds.js
103 ms
a.js;m=11087201945788;cache=1456762351339
276 ms
bat.js
220 ms
270 ms
broker.js
166 ms
mediasource-A138761-4554-4ab0-bc28-f81d59c71e6b1-c-3327.js
196 ms
insight.min.js
242 ms
fbevents.js
97 ms
conversion_async.js
183 ms
286 ms
299 ms
xd_arbiter.php
297 ms
bk-coretag.js
238 ms
adsct
254 ms
adsct
257 ms
201 ms
205 ms
event
137 ms
broker-config.js
36 ms
120 ms
37 ms
c.gif
11 ms
16141
62 ms
adsct
30 ms
tr
29 ms
22 ms
4413
88 ms
3085
63 ms
13577
82 ms
66 ms
adsct
67 ms
adsct
67 ms
a.js;m=11087206147552;cache=0.10627410770393908
62 ms
3327
47 ms
dis.aspx
149 ms
34 ms
29 ms
29 ms
31 ms
31 ms
58 ms
57 ms
a.js;m=11087206212490;cache=0.9790379353798926
29 ms
like.php
113 ms
-1cfYrhulAt.js
286 ms
LVx-xkvaJ0b.png
305 ms
123
237 ms
123
233 ms
sync
205 ms
ad
241 ms
rtset
227 ms
Pug
226 ms
sync
231 ms
spp.pl
265 ms
u.php
149 ms
pixel
224 ms
105 ms
148 ms
cookiematch.aspx
108 ms
l
78 ms
match
37 ms
create.php
59 ms
rum
34 ms
362338.gif
28 ms
mapuser
21 ms
create.php
22 ms
397596.gif
8 ms
office.microsoft.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
office.microsoft.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
Page has valid source maps
office.microsoft.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 Office.microsoft.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 Office.microsoft.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.
office.microsoft.com
Open Graph description is not detected on the main page of Office Microsoft. 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: