Access dev.windowsphone.com. Microsoft Developer

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

dev.windowsphone.com

76 ms

en-us

36 ms

dev.windows.com

73 ms

en-us

141 ms

jquery-2.1.1.min.js

189 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Dev.windowsphone.com, 19% (21 requests) were made to Assets.windowsphone.com and 15% (17 requests) were made to Dev.windows.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Assets.windowsphone.com.

Content Size

1.8 MB

After Optimization

875.4 kB

In fact, the total size of Dev.windowsphone.com main page is 1.8 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. 60% of websites need less resources to load. Images take 749.0 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 131.0 kB

Original 149.6 kB
After minification 102.6 kB
After compression 18.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 47.1 kB, which is 31% 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 131.0 kB or 88% of the original size.

Image Optimization

-22%

Potential reduce by 165.6 kB

Original 749.0 kB
After minification 583.3 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, Dev Windowsphone needs image optimization as it can save up to 165.6 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-58%

Potential reduce by 307.4 kB

Original 532.5 kB
After minification 487.4 kB
After compression 225.1 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 307.4 kB or 58% of the original size.

CSS Optimization

-86%

Potential reduce by 288.1 kB

Original 336.4 kB
After minification 333.0 kB
After compression 48.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. Dev.windowsphone.com needs all CSS files to be minified and compressed as it can save up to 288.1 kB or 86% of the original size.

Requests Now

After Optimization

The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dev Windowsphone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.