Tools & Wizards About Us
cr-api.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

cr-api.com

RoyaleAPI - Clash Royale Analytics, Profiles and Insights

Page Load Speed

2.3 sec in total

First Response

35 ms

Resources Loaded

1.8 sec

Page Rendered

394 ms

cr-api.com screenshot

About Website

Visit cr-api.com now to see the best up-to-date Cr Api content for Israel and also check out these interesting facts you probably never knew about cr-api.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 cr-api.com

Key Findings

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

Performance Metrics

cr-api.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value23.9 s

0/100

10%

TBT (Total Blocking Time)

Value9,420 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.08

94/100

15%

TTI (Time to Interactive)

Value59.6 s

0/100

10%

Network Requests Diagram

cr-api.com

35 ms

royaleapi.com

467 ms

gtm.js

63 ms

cls.css

55 ms

pubfig.min.js

80 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Cr-api.com, 59% (62 requests) were made to Cdns3.royaleapi.com and 33% (35 requests) were made to Cdn.royaleapi.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Cdns3.royaleapi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 120.3 kB (11%)

Content Size

1.0 MB

After Optimization

927.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 93.1 kB

  • Original 106.5 kB
  • After minification 85.0 kB
  • After compression 13.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 21.5 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 93.1 kB or 87% of the original size.

Image Optimization

-4%

Potential reduce by 26.9 kB

  • Original 676.3 kB
  • After minification 649.4 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. Cr Api 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. Cr-api.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (24%)

Requests Now

102

After Optimization

78

  • Images
  • JavaScript
  • CSS

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

cr-api.com

cr-api.com

35 ms

royaleapi.com

royaleapi.com

467 ms

gtm.js

gtm.js

63 ms

cls.css

cls.css

55 ms

pubfig.min.js

pubfig.min.js

80 ms

semantic.min.css

semantic.min.css

91 ms

app.css

app.css

142 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

173 ms

mobile-detect.min.js

mobile-detect.min.js

52 ms

semantic.min.js

semantic.min.js

185 ms

flickity.min.css

flickity.min.css

171 ms

home.css

home.css

171 ms

vendor.js

vendor.js

182 ms

ads.js

ads.js

304 ms

app.main.js

app.main.js

305 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

306 ms

bg-lazyload.js

bg-lazyload.js

305 ms

home.min.js

home.min.js

402 ms

newrelic-royaleapiweb.js

newrelic-royaleapiweb.js

400 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

81 ms

pt-home.jpg

pt-home.jpg

422 ms

pt-profile.jpg

pt-profile.jpg

370 ms

pt-copy.jpg

pt-copy.jpg

402 ms

gm-pekka-evo-launch.png

gm-pekka-evo-launch.png

394 ms

goblin-trophy.png

goblin-trophy.png

397 ms

global-tournament.png

global-tournament.png

413 ms

battle.png

battle.png

395 ms

league10.png

league10.png

389 ms

challenge-grand.png

challenge-grand.png

413 ms

challenge-classic.png

challenge-classic.png

416 ms

mortar-ev1.png

mortar-ev1.png

420 ms

bats-ev1.png

bats-ev1.png

425 ms

miner.png

miner.png

435 ms

skeleton-king.png

skeleton-king.png

429 ms

cannon-cart.png

cannon-cart.png

432 ms

mother-witch.png

mother-witch.png

523 ms

goblin-gang.png

goblin-gang.png

1002 ms

arrows.png

arrows.png

522 ms

goblin-drill-ev1.png

goblin-drill-ev1.png

523 ms

tesla-ev1.png

tesla-ev1.png

524 ms

goblin-demolisher.png

goblin-demolisher.png

540 ms

knight.png

knight.png

672 ms

poison.png

poison.png

544 ms

skeletons.png

skeletons.png

543 ms

ice-spirit.png

ice-spirit.png

541 ms

the-log.png

the-log.png

543 ms

goblin-giant-ev1.png

goblin-giant-ev1.png

544 ms

zap-ev1.png

zap-ev1.png

545 ms

prince.png

prince.png

661 ms

phoenix.png

phoenix.png

546 ms

dark-prince.png

dark-prince.png

547 ms

bomber.png

bomber.png

661 ms

rage.png

rage.png

663 ms

archers-ev1.png

archers-ev1.png

661 ms

x-bow.png

x-bow.png

662 ms

fireball.png

fireball.png

663 ms

royaleapi-logo-128.png

royaleapi-logo-128.png

363 ms

creator-code_128-fs8.png

creator-code_128-fs8.png

363 ms

stripes.png

stripes.png

362 ms

elixir.png

elixir.png

363 ms

elixir-cycle.png

elixir-cycle.png

366 ms

sk_555.jpg

sk_555.jpg

362 ms

blog_post_image_fpo-fs8.png

blog_post_image_fpo-fs8.png

387 ms

sirtagcr.jpg

sirtagcr.jpg

384 ms

boss.jpg

boss.jpg

376 ms

ouahleouff.jpg

ouahleouff.jpg

386 ms

hmg.jpg

hmg.jpg

378 ms

juicyj.jpg

juicyj.jpg

382 ms

crvl.png

crvl.png

393 ms

twitter.svg

twitter.svg

398 ms

facebook.svg

facebook.svg

410 ms

instagram.svg

instagram.svg

401 ms

discord.svg

discord.svg

403 ms

github.svg

github.svg

404 ms

reddit.svg

reddit.svg

413 ms

youtube.svg

youtube.svg

418 ms

icons.woff

icons.woff

208 ms

wizard-ev1.png

wizard-ev1.png

396 ms

ram-rider.png

ram-rider.png

298 ms

pekka.png

pekka.png

277 ms

void.png

void.png

274 ms

royal-ghost.png

royal-ghost.png

274 ms

bandit.png

bandit.png

273 ms

electro-spirit.png

electro-spirit.png

266 ms

wall-breakers-ev1.png

wall-breakers-ev1.png

257 ms

royal-recruits-ev1.png

royal-recruits-ev1.png

257 ms

skeleton-barrel.png

skeleton-barrel.png

254 ms

mighty-miner.png

mighty-miner.png

250 ms

firecracker.png

firecracker.png

247 ms

goblins.png

goblins.png

242 ms

valkyrie-ev1.png

valkyrie-ev1.png

256 ms

app_defer.css

app_defer.css

91 ms

lava-hound.png

lava-hound.png

168 ms

balloon.png

balloon.png

168 ms

inferno-dragon.png

inferno-dragon.png

169 ms

skeleton-dragons.png

skeleton-dragons.png

167 ms

guards.png

guards.png

154 ms

knight-ev1.png

knight-ev1.png

168 ms

graveyard.png

graveyard.png

161 ms

little-prince.png

little-prince.png

161 ms

baby-dragon.png

baby-dragon.png

173 ms

tornado.png

tornado.png

180 ms

barbarian-barrel.png

barbarian-barrel.png

185 ms

tombstone.png

tombstone.png

186 ms

nr-spa-1209.min.js

nr-spa-1209.min.js

18 ms

Accessibility Review

cr-api.com accessibility score

76

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

cr-api.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

cr-api.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 Cr-api.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 Cr-api.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

cr-api.com

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