Tools & Wizards About Us
writer.live.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

writer.live.com

Windows Essentials - Microsoft Support

Page Load Speed

1.8 sec in total

First Response

191 ms

Resources Loaded

1.4 sec

Page Rendered

215 ms

writer.live.com screenshot

About Website

Visit writer.live.com now to see the best up-to-date Writer Live content for United States and also check out these interesting facts you probably never knew about writer.live.com

Windows Essentials reached end of support on January 10, 2017 and is no longer available for download.

Visit writer.live.com

Key Findings

We analyzed Writer.live.com page load time and found that the first response time was 191 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

writer.live.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

writer.live.com

191 ms

essentials-other

21 ms

essentials

12 ms

essentials

117 ms

modernizr.wol.js

23 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Writer.live.com, 36% (17 requests) were made to Res2.windows.microsoft.com and 19% (9 requests) were made to Res1.windows.microsoft.com. The less responsive or slowest element that took the longest time to load (547 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 465.8 kB (51%)

Content Size

916.0 kB

After Optimization

450.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Writer.live.com main page is 916.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. 55% of websites need less resources to load. Images take 295.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 71.7 kB

  • Original 89.4 kB
  • After minification 84.4 kB
  • After compression 17.8 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 71.7 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 25.0 kB

  • Original 295.0 kB
  • After minification 270.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. Writer Live images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 162.6 kB

  • Original 289.1 kB
  • After minification 287.7 kB
  • After compression 126.4 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 162.6 kB or 56% of the original size.

CSS Optimization

-85%

Potential reduce by 206.5 kB

  • Original 242.5 kB
  • After minification 231.9 kB
  • After compression 36.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. Writer.live.com needs all CSS files to be minified and compressed as it can save up to 206.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (49%)

Requests Now

41

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

writer.live.com

writer.live.com

191 ms

essentials-other

essentials-other

21 ms

essentials

essentials

12 ms

essentials

essentials

117 ms

modernizr.wol.js

modernizr.wol.js

23 ms

windows8_site_ltr.css

windows8_site_ltr.css

47 ms

15d2470f-0fcf-45e9-bf5b-c943236a61cf_534.css

15d2470f-0fcf-45e9-bf5b-c943236a61cf_534.css

70 ms

siteresource.ashx

siteresource.ashx

36 ms

MicrosoftAjax.js

MicrosoftAjax.js

92 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

91 ms

wol.common.js

wol.common.js

83 ms

pre_broker.js

pre_broker.js

85 ms

broker.js

broker.js

87 ms

67706439-4969-4bc3-9e3b-50770f40b20e_42.js

67706439-4969-4bc3-9e3b-50770f40b20e_42.js

37 ms

566128a7-5192-449d-99b0-11b4459eaf1d_14.js

566128a7-5192-449d-99b0-11b4459eaf1d_14.js

60 ms

ed238a8c-7088-4066-9cc0-b59861a5a8a2_15.js

ed238a8c-7088-4066-9cc0-b59861a5a8a2_15.js

38 ms

siteresource.ashx

siteresource.ashx

36 ms

bsilite-min.js

bsilite-min.js

81 ms

4300ae64-546c-4bbe-9026-6779b3684fb9_18.png

4300ae64-546c-4bbe-9026-6779b3684fb9_18.png

60 ms

mslogo.png

mslogo.png

260 ms

login.srf

login.srf

299 ms

f6539fab-e1c1-4a86-adf3-e452119a6d53_8.png

f6539fab-e1c1-4a86-adf3-e452119a6d53_8.png

256 ms

cbc6f38d-b79c-4bff-8b67-b81eb9676ab3_5.png

cbc6f38d-b79c-4bff-8b67-b81eb9676ab3_5.png

188 ms

9f89e813-dc8b-4fdb-ab24-63bbb254a6b1_5.png

9f89e813-dc8b-4fdb-ab24-63bbb254a6b1_5.png

189 ms

49eb9f77-0c92-450c-a267-999f2caaa56b_18.png

49eb9f77-0c92-450c-a267-999f2caaa56b_18.png

246 ms

ab21605f-82f5-4052-8125-d13b96cc9075_5.png

ab21605f-82f5-4052-8125-d13b96cc9075_5.png

244 ms

4300ae64-546c-4bbe-9026-6779b3684fb8_32.png

4300ae64-546c-4bbe-9026-6779b3684fb8_32.png

249 ms

gl_site.svg

gl_site.svg

189 ms

5a7873a1-fd4e-4462-8ab2-32bd729117c6_7.png

5a7873a1-fd4e-4462-8ab2-32bd729117c6_7.png

244 ms

gl_social.svg

gl_social.svg

244 ms

6ef177b8-1a15-4e39-bdda-6b672064860b_45.png

6ef177b8-1a15-4e39-bdda-6b672064860b_45.png

248 ms

c641cc8d-f054-4fdf-9456-ee8259186e1b_5.png

c641cc8d-f054-4fdf-9456-ee8259186e1b_5.png

248 ms

3ef01e72-0832-46f0-a6e1-23f9d5a07d86_14.png

3ef01e72-0832-46f0-a6e1-23f9d5a07d86_14.png

249 ms

03df314e-c18c-4d6c-9b89-f5490b1b5c0b_17.png

03df314e-c18c-4d6c-9b89-f5490b1b5c0b_17.png

249 ms

1f5c1661-b1b6-4675-820e-67f729bc7eb6_13.png

1f5c1661-b1b6-4675-820e-67f729bc7eb6_13.png

249 ms

eb4f0171-7cb7-428a-afcc-d93a6b84525c_33.png

eb4f0171-7cb7-428a-afcc-d93a6b84525c_33.png

249 ms

82470c75-e529-4009-9d4e-38ff28975a0a_11.woff

82470c75-e529-4009-9d4e-38ff28975a0a_11.woff

247 ms

ClientBiSettings.Wol.js

ClientBiSettings.Wol.js

205 ms

MergeHandler.aspx

MergeHandler.aspx

289 ms

gl_site.svg

gl_site.svg

98 ms

broker-config.js

broker-config.js

107 ms

5fdaa5e4-14c0-41a1-8810-dbaf91fb113c_11.woff

5fdaa5e4-14c0-41a1-8810-dbaf91fb113c_11.woff

58 ms

trans_pixel.aspx

trans_pixel.aspx

158 ms

like.php

like.php

148 ms

fy8tT2klpgR.js

fy8tT2klpgR.js

482 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

547 ms

trans_pixel.aspx

trans_pixel.aspx

81 ms

Accessibility Review

writer.live.com accessibility score

97

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best Practices

writer.live.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

writer.live.com SEO score

84

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Writer.live.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 Writer.live.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.

Social Sharing Optimization

writer.live.com

Open Graph data is detected on the main page of Writer Live. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: