Tools & Wizards About Us
bladez.io screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

bladez.io

⚔️ bladez-io.com - Battle Royale Blade Wars io Game

Page Load Speed

3.7 sec in total

First Response

1 sec

Resources Loaded

2.6 sec

Page Rendered

115 ms

bladez.io screenshot

About Website

Visit bladez.io now to see the best up-to-date Blade Z content and also check out these interesting facts you probably never knew about bladez.io

New survive io game! Youre in a wide field, you have a small blade in your hand, and other people are attacking you, protect yourself, and try to hit the others head, if you do that, the bladez in you...

Visit bladez.io

Key Findings

We analyzed Bladez.io page load time and found that the first response time was 1 sec and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

bladez.io performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value7,710 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

Network Requests Diagram

bladez-io.com

1002 ms

css

35 ms

css

47 ms

jquery.min.js

31 ms

gpt.js

101 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Bladez.io, 13% (8 requests) were made to Bladez-io.com and 11% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Bladez-io.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (65%)

Content Size

2.6 MB

After Optimization

910.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Bladez.io main page is 2.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 1.4 MB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 240.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 1.4 MB or 85% of the original size.

Image Optimization

-83%

Potential reduce by 341.0 kB

  • Original 410.9 kB
  • After minification 69.9 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. Obviously, Blade Z needs image optimization as it can save up to 341.0 kB or 83% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 2.7 kB

  • Original 602.6 kB
  • After minification 602.5 kB
  • After compression 599.8 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 32 (58%)

Requests Now

55

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bladez-io.com

bladez-io.com

1002 ms

css

css

35 ms

css

css

47 ms

jquery.min.js

jquery.min.js

31 ms

gpt.js

gpt.js

101 ms

adsbygoogle.js

adsbygoogle.js

135 ms

pubads_impl.js

pubads_impl.js

51 ms

show_ads_impl.js

show_ads_impl.js

364 ms

zrt_lookup_nohtml.html

zrt_lookup_nohtml.html

77 ms

email-decode.min.js

email-decode.min.js

41 ms

js

js

131 ms

close.svg

close.svg

426 ms

ads

ads

408 ms

container.html

container.html

134 ms

logost.png

logost.png

445 ms

xlb.png.pagespeed.ic.Sz0YNLZ_-0.webp

xlb.png.pagespeed.ic.Sz0YNLZ_-0.webp

490 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf

130 ms

ads

ads

544 ms

spritesheet.json

spritesheet.json

516 ms

ndata

ndata

517 ms

js

js

53 ms

analytics.js

analytics.js

19 ms

collect

collect

11 ms

7cd4e431960dfbc46ebf5b45a3c9c013.js

7cd4e431960dfbc46ebf5b45a3c9c013.js

21 ms

load_preloaded_resource.js

load_preloaded_resource.js

47 ms

b402b2bd027c28d5c90c17bfa425037e.js

b402b2bd027c28d5c90c17bfa425037e.js

38 ms

abg_lite.js

abg_lite.js

49 ms

window_focus.js

window_focus.js

55 ms

qs_click_protection.js

qs_click_protection.js

58 ms

ufs_web_display.js

ufs_web_display.js

10 ms

d3bea833c2cc1c58e9669317c0a4e806.js

d3bea833c2cc1c58e9669317c0a4e806.js

47 ms

icon.png

icon.png

17 ms

s

s

111 ms

css

css

45 ms

reactive_library.js

reactive_library.js

194 ms

ca-pub-4173034791790735

ca-pub-4173034791790735

117 ms

activeview

activeview

90 ms

4DPoyt1VXFu9KUV3wfZ2z3y8g_kcb_PjstTR5ZPZl3Q.js

4DPoyt1VXFu9KUV3wfZ2z3y8g_kcb_PjstTR5ZPZl3Q.js

15 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

10 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

14 ms

spritesheet.png

spritesheet.png

833 ms

zrt_lookup_nohtml.html

zrt_lookup_nohtml.html

112 ms

3e4ba1a8aaf1eb5089ecf6e0b9cafde2.js

3e4ba1a8aaf1eb5089ecf6e0b9cafde2.js

102 ms

aace578ba99d20b5cd2403bbee6cc236.js

aace578ba99d20b5cd2403bbee6cc236.js

114 ms

14007763394025369976

14007763394025369976

267 ms

redir.html

redir.html

293 ms

one_click_handler_one_afma.js

one_click_handler_one_afma.js

266 ms

css2

css2

244 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

217 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

216 ms

icon.png

icon.png

208 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

210 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

209 ms

6492821534889200789

6492821534889200789

226 ms

10867355848191042843

10867355848191042843

205 ms

redir.html

redir.html

160 ms

redir.html

redir.html

145 ms

activeview

activeview

104 ms

iframe.html

iframe.html

84 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

32 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

31 ms

iframe.html

iframe.html

31 ms

14763004658117789537

14763004658117789537

29 ms

iframe.html

iframe.html

95 ms

Accessibility Review

bladez.io accessibility score

74

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.

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

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

bladez.io best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

bladez.io 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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

bladez.io

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