8.9 sec in total
221 ms
7.1 sec
1.6 sec
Visit firecast.com.br now to see the best up-to-date Firecast content and also check out these interesting facts you probably never knew about firecast.com.br
Online tabletop RPG platform for D&D 5e and more. Tools like character sheets, complete 3D dice set, combat grid, macros, initiative tracker.
Visit firecast.com.brWe analyzed Firecast.com.br page load time and found that the first response time was 221 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
firecast.com.br performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value17.0 s
0/100
25%
Value16.7 s
0/100
10%
Value1,540 ms
13/100
30%
Value0.552
13/100
15%
Value16.7 s
5/100
10%
221 ms
3435 ms
295 ms
258 ms
349 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Firecast.com.br, 69% (74 requests) were made to Firecast.app and 17% (18 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Firecast.app.
Page size can be reduced by 272.7 kB (14%)
1.9 MB
1.7 MB
In fact, the total size of Firecast.com.br main page is 1.9 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. 80% 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. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 269.5 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 269.5 kB or 90% of the original size.
Potential reduce by 85 B
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. Firecast images are well optimized though.
Potential reduce by 2.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.
Potential reduce by 293 B
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. Firecast.com.br has all CSS files already compressed.
Number of requests can be reduced by 60 (70%)
86
26
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Firecast. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
firecast.com.br
221 ms
3435 ms
js
295 ms
wp-emoji-release.min.js
258 ms
pa-frontend-15909006b.min.css
349 ms
style.min.css
352 ms
trp-language-switcher.css
375 ms
style.min.css
357 ms
theme.min.css
229 ms
elementor-icons.min.css
376 ms
frontend.min.css
401 ms
frontend.min.css
682 ms
she-header-style.css
467 ms
ekiticons.css
622 ms
widget-styles.css
489 ms
responsive.css
617 ms
css
334 ms
fontawesome.min.css
707 ms
solid.min.css
706 ms
jquery.min.js
731 ms
jquery-migrate.min.js
751 ms
frontend-gtag.min.js
755 ms
she-header.js
762 ms
js
286 ms
all.min.css
1012 ms
slick.min.css
1011 ms
animations.min.css
1340 ms
trp-translate-dom-changes.js
1343 ms
pa-frontend-15909006b.min.js
1342 ms
frontend-script.js
1343 ms
widget-scripts.js
1329 ms
jquery.smartmenus.min.js
1328 ms
waypoints.min.js
1324 ms
slick.min.js
1337 ms
imagesloaded.min.js
1331 ms
webpack-pro.runtime.min.js
1335 ms
webpack.runtime.min.js
1337 ms
frontend-modules.min.js
1338 ms
frontend.min.js
1354 ms
core.min.js
1351 ms
swiper.min.js
1322 ms
share-link.min.js
1198 ms
js
56 ms
dialog.min.js
1096 ms
frontend.min.js
1088 ms
preloaded-elements-handlers.min.js
1070 ms
animate-circle.js
1071 ms
elementor.js
1074 ms
preloaded-modules.min.js
1075 ms
analytics.js
214 ms
jquery.sticky.min.js
933 ms
underscore.min.js
802 ms
wp-util.min.js
797 ms
frontend.min.js
743 ms
js
588 ms
logo1024x1024no_padding-300x300.png
389 ms
en_US.png
389 ms
pt_BR.png
405 ms
slide1_img.jpg
502 ms
slide2_img.jpg
405 ms
slide3_img.jpg
499 ms
slide4_img.jpg
766 ms
Delphi-minified.png
498 ms
elementor-1.png
499 ms
linkid.js
356 ms
wordpress-1.png
165 ms
c7-1024x578.jpg
436 ms
c12-1024x578.jpg
561 ms
c3-1024x578.jpg
435 ms
c9-1024x578.jpg
559 ms
c1-1024x578.jpg
430 ms
c8-1024x578.jpg
554 ms
c11-1024x578.jpg
786 ms
c5-1024x578.jpg
775 ms
c4-1024x578.jpg
782 ms
c6-1024x597.jpg
775 ms
c2-1024x578.jpg
779 ms
c10-1024x578.jpg
776 ms
7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8SX21nejpA.woff
458 ms
7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8Rf21nejpA.woff
459 ms
7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8fvx1nejpA.woff
692 ms
7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8cLx1nejpA.woff
463 ms
7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8aXx1nejpA.woff
690 ms
7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8Yzx1nejpA.woff
461 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYw.woff
462 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYw.woff
462 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYw.woff
551 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUZiYw.woff
533 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYw.woff
549 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYw.woff
532 ms
fa-solid-900.woff
894 ms
KFOmCnqEu92Fr1Mu4mxM.woff
673 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
665 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
664 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
654 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
724 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
723 ms
eicons.woff
871 ms
conversion_async.js
706 ms
collect
367 ms
uwt.js
648 ms
collect
354 ms
88 ms
adsct
195 ms
adsct
213 ms
trp-ajax.php
151 ms
trp-ajax.php
158 ms
156 ms
firecast.com.br accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
firecast.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
firecast.com.br SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Firecast.com.br 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 Firecast.com.br 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.
firecast.com.br
Open Graph data is detected on the main page of Firecast. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: