Tools & Wizards About Us
buildroyale.io screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

buildroyale.io

Build Royale - Battle Royale in Your Browser

Page Load Speed

829 ms in total

First Response

117 ms

Resources Loaded

644 ms

Page Rendered

68 ms

buildroyale.io screenshot

About Website

Click here to check amazing Build Royale content for United States. Otherwise, check out these important facts you probably never knew about buildroyale.io

Build Royale - The #1 IO Battle Royale Game. Build, break and eliminate! - A free IO game by Mathew

Visit buildroyale.io

Key Findings

We analyzed Buildroyale.io page load time and found that the first response time was 117 ms and then it took 712 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

buildroyale.io performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

82/100

25%

SI (Speed Index)

Value16.2 s

0/100

10%

TBT (Total Blocking Time)

Value10,600 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value41.2 s

0/100

10%

Network Requests Diagram

buildroyale.io

117 ms

buildroyale.io

160 ms

bp.css

51 ms

main.css

226 ms

client

58 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 87% of them (46 requests) were addressed to the original Buildroyale.io, 6% (3 requests) were made to Sdki.truepush.com and 2% (1 request) were made to Accounts.google.com. The less responsive or slowest element that took the longest time to load (350 ms) belongs to the original domain Buildroyale.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 28.6 kB (15%)

Content Size

191.9 kB

After Optimization

163.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Buildroyale.io main page is 191.9 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. 25% of websites need less resources to load. Images take 122.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 19.9 kB

  • Original 25.3 kB
  • After minification 21.1 kB
  • After compression 5.4 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 4.1 kB, which is 16% 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 19.9 kB or 79% of the original size.

Image Optimization

-7%

Potential reduce by 8.1 kB

  • Original 122.4 kB
  • After minification 114.2 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. Build Royale images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 584 B

  • Original 44.2 kB
  • After minification 44.2 kB
  • After compression 43.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.

Requests Breakdown

Number of requests can be reduced by 17 (33%)

Requests Now

51

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

buildroyale.io

buildroyale.io

117 ms

buildroyale.io

buildroyale.io

160 ms

bp.css

bp.css

51 ms

main.css

main.css

226 ms

client

client

58 ms

msgpack.js

msgpack.js

166 ms

scheme.js

scheme.js

96 ms

peZWnv.js

peZWnv.js

190 ms

widget.min.js

widget.min.js

171 ms

js

js

59 ms

platform.js

platform.js

27 ms

app.js

app.js

55 ms

loader.png

loader.png

136 ms

play-button.png

play-button.png

202 ms

solo0.png

solo0.png

178 ms

duos0.png

duos0.png

192 ms

squad0.png

squad0.png

181 ms

mode-hotpotato.png

mode-hotpotato.png

261 ms

battle-pass.png

battle-pass.png

198 ms

icon-account.png

icon-account.png

216 ms

icon-settings.png

icon-settings.png

262 ms

icon-shop.png

icon-shop.png

215 ms

icon-locker.png

icon-locker.png

262 ms

emote34.png

emote34.png

261 ms

emote33.png

emote33.png

260 ms

emote32.png

emote32.png

261 ms

emote31.png

emote31.png

279 ms

icon-challenges.png

icon-challenges.png

261 ms

icon-leaderboard.png

icon-leaderboard.png

262 ms

logo2.png

logo2.png

278 ms

account-button.png

account-button.png

299 ms

challenges-button.png

challenges-button.png

279 ms

logo5.png

logo5.png

300 ms

locker-button.png

locker-button.png

279 ms

shop-button.png

shop-button.png

304 ms

login-button.png

login-button.png

291 ms

gammo-button.png

gammo-button.png

282 ms

signout-button.png

signout-button.png

291 ms

leaderboard-button.png

leaderboard-button.png

300 ms

setting-button.png

setting-button.png

316 ms

discord-out.png

discord-out.png

308 ms

instagram-out.png

instagram-out.png

350 ms

twitter-out.png

twitter-out.png

348 ms

twitch-out.png

twitch-out.png

273 ms

changelog.png

changelog.png

265 ms

battle-pass-logo.png

battle-pass-logo.png

199 ms

timer-icon.png

timer-icon.png

179 ms

master-builder.png

master-builder.png

158 ms

currency0.png

currency0.png

170 ms

watch-ad-icon.png

watch-ad-icon.png

165 ms

solo-active0.png

solo-active0.png

124 ms

version.json

version.json

18 ms

main.js

main.js

3 ms

Accessibility Review

buildroyale.io accessibility score

79

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Links do not have a discernible name

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

buildroyale.io best practices score

50

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

Displays images with incorrect aspect ratio

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

buildroyale.io SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Buildroyale.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Buildroyale.io main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

buildroyale.io

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