5.2 sec in total
156 ms
4.8 sec
231 ms
Visit brazenanimation.com now to see the best up-to-date Brazen Animation content for United States and also check out these interesting facts you probably never knew about brazenanimation.com
Brazen Animation is an audacious gathering of artists, innovators, and creators. We are here to tell transcendent stories that endure for ages. Through our cutting edge technology, bold visuals, and c...
Visit brazenanimation.comWe analyzed Brazenanimation.com page load time and found that the first response time was 156 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
brazenanimation.com performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value9.0 s
1/100
25%
Value29.0 s
0/100
10%
Value37,140 ms
0/100
30%
Value0
100/100
15%
Value50.1 s
0/100
10%
156 ms
339 ms
75 ms
132 ms
226 ms
Our browser made a total of 169 requests to load all elements on the main page. We found that 53% of them (89 requests) were addressed to the original Brazenanimation.com, 32% (54 requests) were made to I0.wp.com and 3% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source I0.wp.com.
Page size can be reduced by 177.3 kB (3%)
5.6 MB
5.5 MB
In fact, the total size of Brazenanimation.com main page is 5.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. 85% 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 5.0 MB which makes up the majority of the site volume.
Potential reduce by 151.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 151.5 kB or 85% of the original size.
Potential reduce by 20.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. Brazen Animation images are well optimized though.
Potential reduce by 3.6 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 1.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. Brazenanimation.com has all CSS files already compressed.
Number of requests can be reduced by 88 (57%)
154
66
The browser has sent 154 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brazen Animation. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
brazenanimation.com
156 ms
www.brazenanimation.com
339 ms
wp-emoji-release.min.js
75 ms
v4-shims.min.css
132 ms
all.min.css
226 ms
mediaelementplayer-legacy.min.css
175 ms
wp-mediaelement.min.css
173 ms
autoptimize_single_e6fae855021a88a0067fcc58121c594f.css
177 ms
autoptimize_single_806660feb28c8fbcbc71c988774a56f1.css
177 ms
autoptimize_single_614e7805d92c4702107d8a472080102d.css
188 ms
wcpm.min.css
229 ms
instagram.min.css
232 ms
swipebox.min.css
231 ms
twitter.min.css
229 ms
flexslider.min.css
244 ms
flickity.min.css
283 ms
lity.min.css
283 ms
autoptimize_single_de88d60dd10b2ffd8503330924313e9f.css
287 ms
autoptimize_single_a5f3f27858a6920ab11a2e33bc14f80a.css
459 ms
css
35 ms
socicon.min.css
282 ms
linea-icons.min.css
300 ms
linearicons.min.css
337 ms
dashicons.min.css
448 ms
normalize.min.css
337 ms
jquery.fancybox.min.css
340 ms
autoptimize_single_8cc07bc7ce8f239bc17bead23d83f7fe.css
540 ms
single-post.css
384 ms
style.css
383 ms
js_composer.min.css
634 ms
elegant-icons.min.css
441 ms
vc_linecons_icons.min.css
441 ms
autoptimize_single_37d6e8a20854c0b56bd54d4b39ed2ea0.css
498 ms
jquery.min.js
706 ms
jquery-migrate.min.js
497 ms
rbtools.min.js
790 ms
rs6.min.js
1089 ms
autoptimize_single_1a75a1adeffcd055a8be8798c05f4bb2.js
589 ms
api.js
39 ms
e-202240.js
19 ms
animate.min.css
601 ms
wolficons.min.css
725 ms
autoptimize_single_847da8fca8060ca1a70f976aab1210b9.css
678 ms
autoptimize_single_1a19aedf37f4d259dbd1018a60214cc6.js
706 ms
lazysizes.min.js
705 ms
photon.min.js
706 ms
regenerator-runtime.min.js
790 ms
wp-polyfill.min.js
789 ms
autoptimize_single_3f97a68905d330bde2987f0e70052cb2.js
762 ms
js.cookie.min.js
760 ms
wcpm.min.js
756 ms
instagram.min.js
813 ms
share.min.js
812 ms
jquery.lazyloadxt.min.js
861 ms
autoptimize_single_065476569b3d66768148fc19c652e7c2.js
822 ms
mediaelement-and-player.min.js
864 ms
mediaelement-migrate.min.js
860 ms
wp-mediaelement.min.js
859 ms
jquery.flexslider.min.js
832 ms
jquery.fancybox.min.js
806 ms
sticky-kit.min.js
807 ms
autoptimize_single_cb64969930bfee98ac48c71ed8db1c77.js
1035 ms
tooltipsy.min.js
990 ms
jarallax.min.js
984 ms
jquery.bigtext.min.js
927 ms
autoptimize_single_dc4157a44ed0b7c09edb514fbd60e188.js
946 ms
autoptimize_single_ed3b4417df0895e4cf8465d32b69adc6.js
947 ms
autoptimize_single_168b9e73ae0afd819b60016837864cec.js
934 ms
autoptimize_single_6a0e8318d42803736d2fafcc12238026.js
890 ms
effect.min.js
889 ms
js_composer_front.min.js
807 ms
jquery.inview.min.js
805 ms
autoptimize_single_2a8742c0ac1cdbec23be44a7d4e9a3c9.js
790 ms
analytics.js
345 ms
player.min.js
1012 ms
BrazenLogoWhite.png
449 ms
BlackBackground.webp
678 ms
669635153
659 ms
BrazenLogoBlack.png
384 ms
cropped-Screen-Shot-2021-07-22-at-5.24.34-PM.png
380 ms
autoptimize_single_9239b31620286cd0ef2b9f386071c258.js
938 ms
blank.gif
371 ms
BrazenLogos_WBsmall.webp
380 ms
Fox.webp
577 ms
Riot.webp
577 ms
BrazenLogos_EpicSmall.webp
582 ms
EA.webp
589 ms
BrazenLogos_Microsoft.webp
580 ms
Nintendo.webp
929 ms
Wizards.webp
617 ms
UAR.webp
608 ms
Academy.webp
613 ms
ESPN.webp
614 ms
BrazenLogos_TNTsmall.webp
606 ms
BrazenLogos_FX.webp
617 ms
BrazenLogos_Tencent.webp
619 ms
BrazenLogos_Blizzard.webp
922 ms
BrazenLogos_Hasbro.webp
614 ms
AmazonGames.webp
940 ms
SqEnix.webp
941 ms
BrazenLogos_Zynga.webp
1640 ms
samsung.webp
922 ms
B_Engram-e1403759394158.jpg
923 ms
R_Iltis-e1403759554362.jpg
937 ms
M_Matthews2-600x600.jpg
926 ms
G_Lyons-e1403759628101.jpg
1628 ms
H_Drummons_v02.jpg
1638 ms
Brazen_Website_Timeline_BeBrazen.jpg
1659 ms
Brazen_Website_Timeline_Iggy_Final_v002.jpg
1659 ms
Brazen_Website_Timeline_Moses_Final_v002.jpg
1660 ms
Brazen_Website_Timeline_Homer_Final_v002.jpg
1869 ms
Brazen_Website_Timeline_Alexander_Final_v002.jpg
1866 ms
Brazen_Website_Timeline_Constantine_Final_v002.jpg
1867 ms
Brazen_Website_Timeline_Joan_Final_v002.jpg
1865 ms
Brazen_Website_Timeline_Gutenberg_Final_v002.jpg
1865 ms
Brazen_Website_Timeline_DaVinci_Final_v002.jpg
1864 ms
wow.min.js
931 ms
jquery.waypoints.min.js
857 ms
jquery.fittext.min.js
855 ms
autoptimize_single_7c497e387bcce6f8fe0f87de92e12040.js
854 ms
flickity.pkgd.min.js
1545 ms
autoptimize_single_c2501abe14447e51c3af33c9b76918b8.js
1467 ms
autoptimize_single_a5bb895291886ffb17feb9b99d103a29.js
1454 ms
autoptimize_single_70b4897108480dbe11c443c2ab7679c9.js
1445 ms
WhiteFlame_Small.gif
1474 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
188 ms
6ae_4KGrU7VR7bNmaYcV_3E.ttf
264 ms
fontawesome-webfont.woff
1448 ms
fa-brands-400.woff
1668 ms
Socicon.ttf
1622 ms
fa-regular-400.woff
1413 ms
collect
72 ms
fa-solid-900.woff
1560 ms
elegant-icons.woff
1560 ms
Linearicons-Free.woff
1557 ms
Brazen_Website_Timeline_Magellan_Final_v002.jpg
1522 ms
collect
230 ms
Brazen_Website_Timeline_Elizabeth_Final_v002.jpg
1499 ms
player.js
1110 ms
player.css
1086 ms
vuid.min.js
1103 ms
Brazen_Website_Timeline_Shakespeare_Final_v002.jpg
1297 ms
Brazen_Website_Timeline_Newton_Final_v002.jpg
1315 ms
Brazen_Website_Timeline_Franklin_Final_v002.jpg
1315 ms
Brazen_Website_Timeline_Mozart_Final_v002.jpg
1309 ms
Brazen_Website_Timeline_Washington_Final_v002.jpg
1291 ms
Brazen_Website_Timeline_Lincoln_Final_v002.jpg
1491 ms
ga-audiences
1038 ms
Brazen_Website_Timeline_Edison_Final_v002.jpg
1495 ms
Brazen_Website_Timeline_MadameCurie_Final_v002.jpg
1486 ms
Brazen_Website_Timeline_WrightBros_Final_v002.jpg
1492 ms
Brazen_Website_Timeline_Carver_Final_v002.jpg
1480 ms
Brazen_Website_Timeline_Einstein_Final_v002.jpg
1489 ms
Brazen_Website_Timeline_Chaplin_Final_v002.jpg
1486 ms
Brazen_Website_Timeline_Robinson_Final_v002.jpg
1490 ms
recaptcha__en.js
959 ms
Brazen_Website_Timeline_MLK_Final_v002.jpg
1187 ms
Brazen_Website_Timeline_Armstrong_Final_v002.jpg
1187 ms
Brazen_Website_Timeline_Brazen_Final_v002.jpg
1183 ms
anchor
73 ms
linea-arrows-10.woff
310 ms
styles__ltr.css
10 ms
recaptcha__en.js
30 ms
webworker.js
412 ms
logo_48.png
349 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
156 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
161 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
205 ms
recaptcha__en.js
57 ms
brazenanimation.com accessibility score
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
brazenanimation.com 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
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
brazenanimation.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brazenanimation.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 Brazenanimation.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.
brazenanimation.com
Open Graph data is detected on the main page of Brazen Animation. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: