3.8 sec in total
173 ms
3.2 sec
507 ms
Click here to check amazing Windows Phone content for United States. Otherwise, check out these important facts you probably never knew about windowsphone.com
Read this Q&A to learn about Windows 10 Mobile End of Support.
Visit windowsphone.comWe analyzed Windowsphone.com page load time and found that the first response time was 173 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
windowsphone.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value5.4 s
20/100
25%
Value7.8 s
24/100
10%
Value5,380 ms
0/100
30%
Value0.003
100/100
15%
Value15.1 s
7/100
10%
173 ms
941 ms
123 ms
123 ms
147 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Windowsphone.com, 36% (30 requests) were made to C.s-microsoft.com and 8% (7 requests) were made to Assets.onestore.ms. The less responsive or slowest element that took the longest time to load (941 ms) relates to the external source Microsoft.com.
Page size can be reduced by 4.4 MB (61%)
7.3 MB
2.8 MB
In fact, the total size of Windowsphone.com main page is 7.3 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. 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. CSS take 4.8 MB which makes up the majority of the site volume.
Potential reduce by 148.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 19.1 kB, which is 11% 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 148.6 kB or 83% of the original size.
Potential reduce by 16.0 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. Windows Phone images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 69% of the original size.
Potential reduce by 3.2 MB
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. Windowsphone.com needs all CSS files to be minified and compressed as it can save up to 3.2 MB or 67% of the original size.
Number of requests can be reduced by 39 (53%)
73
34
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Windows Phone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and as a result speed up the page load time.
windowsphone.com
173 ms
phones
941 ms
jquery-1.11.2.min.js
123 ms
widgets.js
123 ms
shell.min.css
147 ms
respond-proxy.html
151 ms
style.csx
374 ms
shell_ie8.js
162 ms
meversion
143 ms
shellservice.v3.min.js
173 ms
blender.js
118 ms
script.jsx
447 ms
wt.js
39 ms
respond.min.js
196 ms
script.jsx
489 ms
l8MdwrYyEeSEOwp+lcGdIw.js
35 ms
pre_broker.js
55 ms
broker.js
31 ms
bootstraper.js
40 ms
Bootstrap.js
19 ms
serverComponent.php
40 ms
b6bb3bc511e7c77d93f49ed351ee4465.js
4 ms
7c9627645fa56b4ec396d4d6f646602b.js
63 ms
HTU-Windows10DownloadExe.xml
272 ms
sdk.js
262 ms
sizzle_1.min.js
16 ms
optimize.js
16 ms
microsoft.png
40 ms
phone_hero.jpg
37 ms
icon-windows-logo.png
30 ms
Lumia-950-XL-performance_feature.jpg
169 ms
Lumia-950-performance_feature.jpg
244 ms
Phone81_NAV.jpg
167 ms
Tablet_NAV.jpg
166 ms
2-In-1_NAV.jpg
244 ms
Laptops_NAV.jpg
167 ms
AllInOnes_NAV.jpg
244 ms
GamingPC_NAV.jpg
244 ms
Windows10_Footer_Icon_Social.png
243 ms
accordion-expand.png
242 ms
accordion-collapse.png
246 ms
Windows10_Footer_Icon_Office.png
248 ms
rsz_windows10_footer_icon_surface_new.png
249 ms
nokia_symbol_clr_52x52.png
248 ms
Windows10_Footer_Icon_Xbox.png
248 ms
Windows10_Footer_Icon_Skype.png
247 ms
Windows10_Footer_Icon_OneDrive.png
249 ms
Windows10_Footer_Icon_Outlook.png
309 ms
Windows10_Footer_Icon_Bing.png
309 ms
Windows10_Footer_Icon_MSStore.png
310 ms
Windows10_Footer_newLocaleSVG.png
310 ms
latest.woff
137 ms
latest.woff
215 ms
latest.woff
213 ms
latest.woff
219 ms
latest.woff
213 ms
shell-icons-0.4.0.woff
131 ms
me.min.css
3 ms
WT3N8JuQex-vEtPMcHtNm1Nto8ZZeCL28nj-huovnpNv0_s1hNrPlxJNAihJjOZyYpGGIJg0VkPB7wmYT7LZ1Kiu-wJo_vO5J4_diI8WOLao4ckJq6EMA-GDUsX_VLhIuSujYXyNfDEcwXPckiSPEAWfbdimNrefP-beFc5hFCsXcVQdPjIMAKk4iuHBSwlPdOKKaDMBDHiQaECFPJpbmsJXPs0xDywcl74Urfcq8pX1vGbQY3svuMGvvTesiXbNXGCkttvIrqmoqkWxoEctwIjHX1tpJ8CxUsiQ_Ai0gqHaVi7M3lpvfHhdOIAqwX-bhO_TT_eT6u6Zlh5Usl2THG49Lz_Nkky7bsYxq7q2NRciXWE-mXGQnzU5skEuJu4QANYfgrdvjrM4v2y2zh8-Dxhh1CjUUuIq1RvhY9R-llu2F3R8oeekKVYMsQOpS6poaGY07M4kWLJl7l9n6nHXuUtsdBMh5enR8-goUyxBMWRr-yFBKfROtAjZJprdXbySp8PIvqQMPOac_JGwUZxebTYIonXK_9fJSeg9_kNxD3AH_-Vj6lbpmwAWkPSSC-_x5XwnXzFd9Q3hMQB0Jsf3xGYU62TZGDyWbKyQjTSlq8kX4iUcKHd74t3iwHQO0bCTwPFP7QD3fD09J1N9JmbEMQhawAU-RteheD75JhXBBsJn7gQipmvKLFbFGa2NIp3B_2JloXImrVMcWFbPg-Uc2TEq029j4KLIqll4ZEJjzWlRbLAcJNb9VkIxPwQbIyFP2zNJSgLKgKjBodXG-rAUrb2LnfPbIi4bxfs23wV2JYFkorXYp4XFgS5fAwAmMrVVg_9oDm0gG2NxwIt_SOtB8bQAg7cGtMKDqvbJlyPkUlbrIgKRzdcOoda2Kv1zdg-MAKFbuBUmfbw2vADLsLV2Obu8Ju_iOJo92symd72RS_aHW3mWSYlg6PWrqkMCNViIzxbtMXzlh4Iyjekqf5a5dE4GozfITbseXSA8I5Aug0HOxuJI_cYqvoqZvj5U5J9VOowBS_JLpAALm9RIH-H20j_qUN26DGC0yYnkOaD9Dg8iVkxjEsuD19W3lR-gnt7w6dF8O4AdbELvnCvGDpvc0qWLqwjXFk5eJjRMJGAXE9yhbGtje78rux52kdfKAJjxCSNWxS-JV5X41v_WDy46yPrXaxPXuwhtK46MMfF-2fyXxJTkD0fMg7AD_bTW1v8o0U9Ditm3s9qbJb330AgwPQ2H16NSiKRxIhrb6EUDgRWakrFwqLk_epui1TlPG-IE5EUXVODaxhncCJAf5x_xbNzuJQPh_r7jYUo9eyO1tOyGqTQaF0EZ6aWe6OIU-frIdy8COVc6givLzpGuodtFMAFFff5ueMP6ZOWolO-1No6BHUPIuSJUJC1ZdXeS_XYG0Wc9kFu3MNOhxLJa-4z5BT-5L7q0FWkAcNm_0av_Y1-kC_GsTZ_szo_ceQQBOTIj_PL94cUSunOSeSxf63ZjQbw0U7eJeOMandhT6SgYvjptVsAHF1Ggs-xMh3NE3Qq67_hnZkoob0EpVL_l6W5nRZ72CQQUNnYZV1eVSk9t0RzCqn2vVQVsoD0Lu1dgnPOuNA8aHSyR9iepboLM3w82VStHk-lm3vZal755l6F6_yZZVG99LHI2ukqlI1ZQyvhqA6MdYLl8l6h2PGB-w0WUjFGvI_6Fa9c9-RjH8FoA4-UPX_EzUNPJn7enhCKDJkncMcCo02aEkT98daNIVLtHMRgejP5hsxT17foLvqorEY4avhAWvetDG9z8a80d5f5gBSVd545aagDRfivHM9Y5BCoB82pPbD5pz_QMJX8xml3-mRXYlKChUNgqgfpmP3scqa97Rw9vUgbkz2KMVQ0nlkIKBO9X9_DaXO8B9EDFWD3E7srNzp5MqFc0Pbsbh4HhlumMVA2a4SwNTPLkf7_iT3R5MiYlSj7R4buSVx80dWHo7_dLOlzpnyaFgEaLu_vIZ_TmucLeyrjqU4yPLHh3muEYY1y9Vw5g-To9cUqxB-mfVPEdasJ7qs2dzX-Wi5xfTNmllrUiG2034fwTlx2t2tf6aFpQiZkXvjLRejfN6IeUh5lM2szHkbhFObmsFq9R_Wcl3b7uud3oOXGg4UISnxQQIyOPXSb2XW3GjtzWgX5duc4amQIhXRmgcCxRYc9Rl-wTsbtavvnkpAqYLfTOgpbIyThUaqj6gyUzU1H01TGSkcSfOrkOTQrndzl0orQfN58bW0Wh3LPnUcjjXb0kcvtBg2Y6Eo4LgMmYKP0qzR6Ok7lKyIrSYCQfanDBavZjNT7B7S-0anBG_AFr006DwA9na_uV5d8eeWQ53bzWD_1joINzQE6r407M5EbveblwLfjv8XmBRFRjGkD3uaU
131 ms
pbPage.CartSummary
129 ms
meBoot.min.js
128 ms
phone_productive.jpg
214 ms
phone_personal.jpg
206 ms
phone_photos.jpg
212 ms
phone_fun.jpg
473 ms
latest.woff
58 ms
latest.woff
61 ms
323 ms
meCore.min.js
97 ms
ms.js
312 ms
fbevents.js
99 ms
broker-config.js
170 ms
xd_arbiter.php
130 ms
xd_arbiter.php
262 ms
34 ms
c.gif
32 ms
like.php
89 ms
vpc6VNjRPXV.js
294 ms
LVx-xkvaJ0b.png
324 ms
getid.js
212 ms
trans_pixel.aspx
92 ms
trans_pixel.aspx
86 ms
trans_pixel.aspx
163 ms
trans_pixel.aspx
165 ms
windowsphone.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
windowsphone.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
Missing source maps for large first-party JavaScript
windowsphone.com SEO score
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Windowsphone.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 Windowsphone.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.
windowsphone.com
Open Graph data is detected on the main page of Windows Phone. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: