Tools & Wizards About Us
royaleapi.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

royaleapi.com

RoyaleAPI - Clash Royale Analytics, Profiles and Insights

Page Load Speed

1.6 sec in total

First Response

26 ms

Resources Loaded

1.2 sec

Page Rendered

356 ms

royaleapi.com screenshot

About Website

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

The definitive source about decks, players and teams in Clash Royale. Explore advanced statistics about decks and cards based on millions of games per week.

Visit royaleapi.com

Key Findings

We analyzed Royaleapi.com page load time and found that the first response time was 26 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

royaleapi.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value15.6 s

0/100

10%

TBT (Total Blocking Time)

Value9,140 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.08

94/100

15%

TTI (Time to Interactive)

Value49.0 s

0/100

10%

Network Requests Diagram

royaleapi.com

26 ms

royaleapi.com

467 ms

gtm.js

50 ms

cls.css

51 ms

pubfig.min.js

66 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Royaleapi.com, 56% (55 requests) were made to Cdns3.royaleapi.com and 36% (35 requests) were made to Cdn.royaleapi.com. The less responsive or slowest element that took the longest time to load (502 ms) relates to the external source Cdns3.royaleapi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 114.6 kB (12%)

Content Size

977.6 kB

After Optimization

863.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royaleapi.com main page is 977.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. 60% of websites need less resources to load. Images take 608.3 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 90.9 kB

  • Original 104.1 kB
  • After minification 83.7 kB
  • After compression 13.2 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 20.4 kB, which is 20% 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 90.9 kB or 87% of the original size.

Image Optimization

-4%

Potential reduce by 23.4 kB

  • Original 608.3 kB
  • After minification 584.8 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. RoyaleAPI images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 96 B

  • Original 31.3 kB
  • After minification 31.3 kB
  • After compression 31.2 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

-0%

Potential reduce by 170 B

  • Original 233.9 kB
  • After minification 233.9 kB
  • After compression 233.7 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. Royaleapi.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 26 (27%)

Requests Now

95

After Optimization

69

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royaleapi.com

royaleapi.com

26 ms

royaleapi.com

royaleapi.com

467 ms

gtm.js

gtm.js

50 ms

cls.css

cls.css

51 ms

pubfig.min.js

pubfig.min.js

66 ms

semantic.min.css

semantic.min.css

98 ms

app.css

app.css

141 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

178 ms

mobile-detect.min.js

mobile-detect.min.js

51 ms

semantic.min.js

semantic.min.js

192 ms

flickity.min.css

flickity.min.css

191 ms

home.css

home.css

269 ms

vendor.js

vendor.js

172 ms

ads.js

ads.js

164 ms

app.main.js

app.main.js

188 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

214 ms

bg-lazyload.js

bg-lazyload.js

215 ms

home.min.js

home.min.js

215 ms

newrelic-royaleapiweb.js

newrelic-royaleapiweb.js

212 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

83 ms

pt-home.jpg

pt-home.jpg

55 ms

pt-profile.jpg

pt-profile.jpg

59 ms

pt-copy.jpg

pt-copy.jpg

502 ms

goblin-giant-ev1.png

goblin-giant-ev1.png

204 ms

zap-ev1.png

zap-ev1.png

203 ms

prince.png

prince.png

213 ms

phoenix.png

phoenix.png

206 ms

dark-prince.png

dark-prince.png

210 ms

bomber.png

bomber.png

212 ms

arrows.png

arrows.png

212 ms

rage.png

rage.png

214 ms

goblin-drill-ev1.png

goblin-drill-ev1.png

214 ms

skeletons-ev1.png

skeletons-ev1.png

216 ms

goblin-demolisher.png

goblin-demolisher.png

218 ms

magic-archer.png

magic-archer.png

217 ms

knight.png

knight.png

217 ms

tornado.png

tornado.png

216 ms

the-log.png

the-log.png

220 ms

bomb-tower.png

bomb-tower.png

220 ms

mortar-ev1.png

mortar-ev1.png

219 ms

bats-ev1.png

bats-ev1.png

224 ms

miner.png

miner.png

220 ms

skeleton-king.png

skeleton-king.png

221 ms

cannon-cart.png

cannon-cart.png

221 ms

goblin-gang.png

goblin-gang.png

224 ms

spear-goblins.png

spear-goblins.png

225 ms

mega-knight-ev1.png

mega-knight-ev1.png

294 ms

skeleton-barrel.png

skeleton-barrel.png

225 ms

inferno-dragon.png

inferno-dragon.png

292 ms

bats.png

bats.png

295 ms

pekka-ev1.png

pekka-ev1.png

295 ms

mother-witch.png

mother-witch.png

294 ms

fisherman.png

fisherman.png

296 ms

guards.png

guards.png

296 ms

zap.png

zap.png

297 ms

ram-rider.png

ram-rider.png

310 ms

royaleapi-logo-128.png

royaleapi-logo-128.png

25 ms

creator-code_128-fs8.png

creator-code_128-fs8.png

26 ms

hmg.jpg

hmg.jpg

25 ms

blog_post_image_fpo-fs8.png

blog_post_image_fpo-fs8.png

24 ms

sirtagcr.jpg

sirtagcr.jpg

31 ms

boss.jpg

boss.jpg

53 ms

sk_555.jpg

sk_555.jpg

49 ms

oj.jpg

oj.jpg

40 ms

ouahleouff.jpg

ouahleouff.jpg

197 ms

crvl.png

crvl.png

50 ms

twitter.svg

twitter.svg

199 ms

facebook.svg

facebook.svg

200 ms

instagram.svg

instagram.svg

204 ms

discord.svg

discord.svg

202 ms

github.svg

github.svg

202 ms

reddit.svg

reddit.svg

204 ms

youtube.svg

youtube.svg

209 ms

royal-ghost.png

royal-ghost.png

264 ms

electro-spirit.png

electro-spirit.png

255 ms

stripes.png

stripes.png

72 ms

elixir.png

elixir.png

71 ms

elixir-cycle.png

elixir-cycle.png

72 ms

archers-ev1.png

archers-ev1.png

112 ms

tesla-ev1.png

tesla-ev1.png

96 ms

x-bow.png

x-bow.png

109 ms

fireball.png

fireball.png

105 ms

skeletons.png

skeletons.png

103 ms

void.png

void.png

184 ms

valkyrie-ev1.png

valkyrie-ev1.png

182 ms

lava-hound.png

lava-hound.png

180 ms

balloon.png

balloon.png

178 ms

skeleton-dragons.png

skeleton-dragons.png

181 ms

gm-spawn-mk-or-pekka.png

gm-spawn-mk-or-pekka.png

178 ms

trophy-goblin-icon-tight.png

trophy-goblin-icon-tight.png

178 ms

global-tournament.png

global-tournament.png

179 ms

battle.png

battle.png

179 ms

league10.png

league10.png

178 ms

challenge-grand.png

challenge-grand.png

178 ms

challenge-classic.png

challenge-classic.png

178 ms

app_defer.css

app_defer.css

75 ms

icons.woff

icons.woff

87 ms

nr-spa-1209.min.js

nr-spa-1209.min.js

16 ms

Accessibility Review

royaleapi.com accessibility score

78

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-*] attributes do not match their roles

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

royaleapi.com 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

royaleapi.com SEO score

84

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

High

Tap targets are not sized appropriately

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 Royaleapi.com 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 Royaleapi.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

royaleapi.com

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