12.6 sec in total
268 ms
6 sec
6.3 sec
Click here to check amazing Dbzdokkanbattle content for United States. Otherwise, check out these important facts you probably never knew about dbzdokkanbattle.com
Visit dbzdokkanbattle.comWe analyzed Dbzdokkanbattle.com page load time and found that the first response time was 268 ms and then it took 12.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
dbzdokkanbattle.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value5.2 s
23/100
25%
Value4.0 s
81/100
10%
Value730 ms
40/100
30%
Value0.095
91/100
15%
Value7.0 s
53/100
10%
268 ms
108 ms
125 ms
125 ms
127 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 76% of them (95 requests) were addressed to the original Dbzdokkanbattle.com, 5% (6 requests) were made to Pagead2.googlesyndication.com and 5% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Dbzdokkanbattle.com.
Page size can be reduced by 1.4 MB (16%)
8.8 MB
7.4 MB
In fact, the total size of Dbzdokkanbattle.com main page is 8.8 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 7.9 MB which makes up the majority of the site volume.
Potential reduce by 188.1 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 188.1 kB or 90% of the original size.
Potential reduce by 771.0 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. Dbzdokkanbattle images are well optimized though.
Potential reduce by 313.1 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 313.1 kB or 60% of the original size.
Potential reduce by 133.4 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. Dbzdokkanbattle.com needs all CSS files to be minified and compressed as it can save up to 133.4 kB or 87% of the original size.
Number of requests can be reduced by 26 (22%)
116
90
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dbzdokkanbattle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
dbzdokkanbattle.com
268 ms
wp-emoji-release.min.js
108 ms
style.css
125 ms
skeleton.css
125 ms
layout.css
127 ms
style.css
128 ms
css
26 ms
shortcodes.css
130 ms
genericons.css
166 ms
tablepress-combined.min.css
184 ms
jquery.js
306 ms
jquery-migrate.min.js
197 ms
adsbygoogle.js
8 ms
wp_clock.php
17 ms
navigation.js
155 ms
skip-link-focus-fix.js
156 ms
sticky-nav.js
5596 ms
retina.js
204 ms
shortcodes.js
205 ms
wp-embed.min.js
206 ms
jquery.datatables.min.js
409 ms
style.css
189 ms
us.png
117 ms
bg.gif
118 ms
banner1.png
538 ms
android16-300x193.png
473 ms
android16int.png
273 ms
anddddd-300x117.png
391 ms
coolervent1-300x197.png
511 ms
coolerevent2-300x265.png
625 ms
coolereventcooler.png
511 ms
cyborgbot.png
539 ms
futuretrunksevent-300x196.png
683 ms
futuretrunksstr.png
632 ms
brolyevent-300x195.png
662 ms
phybroly.png
664 ms
ssjphybroly.png
755 ms
strbroly.png
804 ms
news_banner_event_501_D_3_en-300x297.png
807 ms
rampagepassivenullify-300x255.png
883 ms
treeofmight-300x195.png
887 ms
strtirles.png
820 ms
diaz.png
886 ms
takasei.png
882 ms
treeofmightlocations-243x300.png
950 ms
rasonteq.png
927 ms
amond.png
927 ms
cacao.png
1008 ms
urintturles.png
949 ms
bardock.png
988 ms
raditzcockycounter.png
988 ms
nappacrueltactics.png
1015 ms
gokudetermineddefender.png
1013 ms
worldTournamentdokkan-300x300.png
1112 ms
rof2-300x198.png
1114 ms
sorbet.png
1072 ms
analytics.js
105 ms
tagoma.png
972 ms
9t2Q2pT.png
973 ms
zarbonevilelegant.png
924 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
47 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
49 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
47 ms
PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf
48 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
48 ms
PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf
48 ms
collect
30 ms
ca-pub-5810075006502134.js
136 ms
zrt_lookup.html
204 ms
show_ads_impl.js
130 ms
dodoriarecklessrage.png
873 ms
recoombedazzlingdisplay.png
758 ms
ads
271 ms
osd.js
26 ms
ads
228 ms
burterunfathomablespeed.png
693 ms
jiecelessonsinfear.png
675 ms
guldotimestopper.png
696 ms
uE0kp83.png
676 ms
friezafirstformonslaught.png
677 ms
maiSOPc.png
622 ms
friezasecondformmightmaretransformed.png
618 ms
frieza3rdform.png
610 ms
S3wsmOF.png
609 ms
friezafinalform.png
599 ms
adServer.bs
131 ms
abg.js
41 ms
m_js_controller.js
31 ms
mechafrieza.png
556 ms
s
23 ms
googlelogo_color_112x36dp.png
32 ms
nessie_icon_tiamat_white.png
11 ms
x_button_blue2.png
10 ms
kingcold.png
508 ms
shishami.png
527 ms
goldenfreizaevolved.png
516 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
4 ms
ebStdBanner.js
47 ms
0nsJUW4.png
464 ms
ssjbluevegeta.png
492 ms
ssbluegoku.png
492 ms
rof2-1-copy-220x300.png
573 ms
9b78a619-e913-43b0-ab94-10556616981f.jpg
9 ms
rof2-2-300x174.png
533 ms
rof2-3-300x175.png
545 ms
rofeventimg-300x198.png
498 ms
emperorpilafrobot.png
500 ms
teqrofgoku.png
527 ms
rofvegeta.png
527 ms
beerusteq.png
516 ms
whisint.png
512 ms
amdrid13-300x174.png
589 ms
wcb3C7R-Imgur.png
507 ms
wftN36w-Imgur.png
501 ms
w5UzJcx-Imgur.png
508 ms
AuiOoLU-Imgur.png
475 ms
4tTUShZ-Imgur.png
526 ms
ch2-300x261.png
571 ms
fb.png
508 ms
twt.png
508 ms
gplus.png
492 ms
dbzdokkanbattle.com
527 ms
shadow.png
512 ms
activeview
12 ms
9VDFEM2AAXEDMyMDEyMTIzsjCyMrIxsjNy8CRnpJYV5efF56SmlfDCOEWZ6RklXMmJRakl8Sn55XkcEGZpAVQMpJgbwgQrZSnOLyoBACnGHqgAAAA=
12 ms
dbzdokkanbattle.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
dbzdokkanbattle.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
dbzdokkanbattle.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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dbzdokkanbattle.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Dbzdokkanbattle.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.
dbzdokkanbattle.com
Open Graph description is not detected on the main page of Dbzdokkanbattle. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: