Tools & Wizards About Us
bungie.net screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

bungie.net

Bungie.net | Creators of Destiny 2 & Marathon | Bungie.net

Page Load Speed

483 ms in total

First Response

22 ms

Resources Loaded

397 ms

Page Rendered

64 ms

bungie.net screenshot

About Website

Visit bungie.net now to see the best up-to-date Bungie content for United States and also check out these interesting facts you probably never knew about bungie.net

Visit bungie.net

Key Findings

We analyzed Bungie.net page load time and found that the first response time was 22 ms and then it took 461 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

bungie.net performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

bungie.net

22 ms

www.bungie.net

122 ms

7

128 ms

78.f3f7adf3.chunk.css

19 ms

JSNavigation.ashx

103 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 73% of them (8 requests) were addressed to the original Bungie.net, 9% (1 request) were made to Static.cloudflareinsights.com and 9% (1 request) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (128 ms) belongs to the original domain Bungie.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 22.6 kB (4%)

Content Size

528.6 kB

After Optimization

506.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Bungie.net main page is 528.6 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. Javascripts take 490.8 kB which makes up the majority of the site volume.

HTML Optimization

-45%

Potential reduce by 597 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 742 B

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 597 B or 45% of the original size.

JavaScript Optimization

-4%

Potential reduce by 19.2 kB

  • Original 490.8 kB
  • After minification 490.8 kB
  • After compression 471.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-8%

Potential reduce by 2.8 kB

  • Original 36.4 kB
  • After minification 36.4 kB
  • After compression 33.6 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. Bungie.net has all CSS files already compressed.

Requests Breakdown

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

Requests Now

8

After Optimization

4

  • JavaScript
  • CSS

The browser has sent 8 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bungie. 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

bungie.net

bungie.net

22 ms

www.bungie.net

www.bungie.net

122 ms

7

7

128 ms

78.f3f7adf3.chunk.css

78.f3f7adf3.chunk.css

19 ms

JSNavigation.ashx

JSNavigation.ashx

103 ms

runtime-main.28754574.js

runtime-main.28754574.js

40 ms

78.59446e5a.chunk.js

78.59446e5a.chunk.js

59 ms

main.98a3b2f4.chunk.js

main.98a3b2f4.chunk.js

54 ms

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

76 ms

qau3qwi.css

qau3qwi.css

61 ms

p.css

p.css

31 ms

Accessibility Review

bungie.net accessibility score

91

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.

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

Image elements do not have [alt] attributes

Best Practices

bungie.net best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

bungie.net SEO score

77

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

bungie.net

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