Tools & Wizards About Us
g.live.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

g.live.com

MSN

Page Load Speed

267 ms in total

First Response

19 ms

Resources Loaded

173 ms

Page Rendered

75 ms

g.live.com screenshot

About Website

Click here to check amazing G Live content for United States. Otherwise, check out these important facts you probably never knew about g.live.com

Visit g.live.com

Key Findings

We analyzed G.live.com page load time and found that the first response time was 19 ms and then it took 248 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

g.live.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value4,370 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

g.live.com

19 ms

www.msn.com

47 ms

SSR-extension.4c1fefa6d7c71077384c.js

29 ms

vendors.e0101c64629d61698b7b.js

53 ms

microsoft.24f4fe5ede5b8b248be7.js

70 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 14% of them (1 request) were addressed to the original G.live.com, 57% (4 requests) were made to Assets.msn.com and 29% (2 requests) were made to Msn.com. The less responsive or slowest element that took the longest time to load (81 ms) relates to the external source Assets.msn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (64%)

Content Size

3.2 MB

After Optimization

1.1 MB

  • HTML
  • JavaScript

In fact, the total size of G.live.com main page is 3.2 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. 20% of websites need less resources to load. Javascripts take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 30.5 kB

  • Original 46.6 kB
  • After minification 46.4 kB
  • After compression 16.1 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 30.5 kB or 65% of the original size.

JavaScript Optimization

-64%

Potential reduce by 2.0 MB

  • Original 3.1 MB
  • After minification 3.1 MB
  • After compression 1.1 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 2.0 MB or 64% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (80%)

Requests Now

5

After Optimization

1

  • JavaScript

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of G 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 5 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

g.live.com

g.live.com

19 ms

www.msn.com

www.msn.com

47 ms

SSR-extension.4c1fefa6d7c71077384c.js

SSR-extension.4c1fefa6d7c71077384c.js

29 ms

vendors.e0101c64629d61698b7b.js

vendors.e0101c64629d61698b7b.js

53 ms

microsoft.24f4fe5ede5b8b248be7.js

microsoft.24f4fe5ede5b8b248be7.js

70 ms

common.55bd9698981f91add559.js

common.55bd9698981f91add559.js

81 ms

experience.b4063dfdfbfc0b9fca49.js

experience.b4063dfdfbfc0b9fca49.js

79 ms

Accessibility Review

g.live.com accessibility score

68

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

[role]s are not contained by their required parent element

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

g.live.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

g.live.com SEO score

92

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

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise G.live.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that G.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

g.live.com

Open Graph description is not detected on the main page of G Live. 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: