Tools & Wizards About Us
grandmaster.report screenshot

Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

grandmaster.report

Grandmaster Report | Stats & insights about players' performance in Destiny 2

Page Load Speed

833 ms in total

First Response

119 ms

Resources Loaded

649 ms

Page Rendered

65 ms

grandmaster.report screenshot

About Website

Click here to check amazing Grandmaster content for United States. Otherwise, check out these important facts you probably never knew about grandmaster.report

Get insights about your and anyone's performance in Destiny 2's Nightfall: The Ordeal strikes on Grandmaster difficulty & more

Visit grandmaster.report

Key Findings

We analyzed Grandmaster.report page load time and found that the first response time was 119 ms and then it took 714 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

grandmaster.report performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

98/100

25%

SI (Speed Index)

Value1.8 s

100/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value3.3 s

94/100

10%

Network Requests Diagram

grandmaster.report

119 ms

73c065a9ed1ab3c8eec7.css

135 ms

513cdd68281f00f5cefe.css

18 ms

js

60 ms

polyfills-c8d7e579a944b23d8324.js

104 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 77% of them (17 requests) were addressed to the original Grandmaster.report, 14% (3 requests) were made to O640806.ingest.sentry.io and 5% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (263 ms) relates to the external source Bungie.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.3 kB (41%)

Content Size

8.2 kB

After Optimization

4.8 kB

  • HTML
  • Images

In fact, the total size of Grandmaster.report main page is 8.2 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. Only 10% of websites need less resources to load. HTML takes 5.5 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 3.3 kB

  • Original 5.5 kB
  • After minification 5.5 kB
  • After compression 2.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 3.3 kB or 61% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.7 kB
  • After minification 2.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. Grandmaster images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 13 (65%)

Requests Now

20

After Optimization

7

  • AJAX
  • JavaScript
  • CSS

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

Network Requests Diagram

grandmaster.report

grandmaster.report

119 ms

73c065a9ed1ab3c8eec7.css

73c065a9ed1ab3c8eec7.css

135 ms

513cdd68281f00f5cefe.css

513cdd68281f00f5cefe.css

18 ms

js

js

60 ms

polyfills-c8d7e579a944b23d8324.js

polyfills-c8d7e579a944b23d8324.js

104 ms

webpack-50bee04d1dc61f8adf5b.js

webpack-50bee04d1dc61f8adf5b.js

221 ms

framework.6fff953eb0f638171baa.js

framework.6fff953eb0f638171baa.js

31 ms

4c305d0592c55235a3e81fa7af0861b38d53d627.da40e8613949437d09f1.js

4c305d0592c55235a3e81fa7af0861b38d53d627.da40e8613949437d09f1.js

18 ms

main-1ecb1ce93a2daef99398.js

main-1ecb1ce93a2daef99398.js

25 ms

6ce5dd3fcb6b2325e397de7dc05b8f39e851c640.1fb347fb76f56890e794.js

6ce5dd3fcb6b2325e397de7dc05b8f39e851c640.1fb347fb76f56890e794.js

26 ms

1e8fc4a2a8163210277b1754257b4229455cd5ec.ff2a6f0abaf64f007878.js

1e8fc4a2a8163210277b1754257b4229455cd5ec.ff2a6f0abaf64f007878.js

34 ms

b5deef23c7d8ef607d56d0077c937a2f99b5818b.0c2fa92c1d50fdd9a596.js

b5deef23c7d8ef607d56d0077c937a2f99b5818b.0c2fa92c1d50fdd9a596.js

35 ms

_app-919fe68c4735bc724b96.js

_app-919fe68c4735bc724b96.js

39 ms

index-2d8bbc80283f1504e919.js

index-2d8bbc80283f1504e919.js

44 ms

_buildManifest.js

_buildManifest.js

42 ms

_ssgManifest.js

_ssgManifest.js

46 ms

48dda413d9f412ca2b10fd56a35a2665.png

48dda413d9f412ca2b10fd56a35a2665.png

263 ms

126 ms

123 ms

125 ms

after-the-nightfall-7c5c21c49b7b60b030c2.js

after-the-nightfall-7c5c21c49b7b60b030c2.js

112 ms

764b01f45795dc8a94cc.css

764b01f45795dc8a94cc.css

21 ms

Accessibility Review

grandmaster.report accessibility score

98

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

grandmaster.report best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

grandmaster.report SEO score

100

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

grandmaster.report

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