Tools & Wizards About Us
dragonballz.com screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

dragonballz.com

Dragon Ball Z | The Official Site

Page Load Speed

1.8 sec in total

First Response

28 ms

Resources Loaded

1.5 sec

Page Rendered

267 ms

dragonballz.com screenshot

About Website

Visit dragonballz.com now to see the best up-to-date Dragon Ball Z content for India and also check out these interesting facts you probably never knew about dragonballz.com

The Official Dragon Ball Z anime website from FUNimation

Visit dragonballz.com

Key Findings

We analyzed Dragonballz.com page load time and found that the first response time was 28 ms and then it took 1.8 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

dragonballz.com performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value2.7 s

97/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value1.046

2/100

15%

TTI (Time to Interactive)

Value7.8 s

45/100

10%

Network Requests Diagram

dragonballz.com

28 ms

styles.css

6 ms

jquery-2.1.4.min.js

7 ms

header.css

20 ms

style.css

4 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 32% of them (27 requests) were addressed to the original Dragonballz.com, 6% (5 requests) were made to C1.adform.net and 5% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Dragonballz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 82.1 kB (7%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-67%

Potential reduce by 32.3 kB

  • Original 48.1 kB
  • After minification 46.5 kB
  • After compression 15.8 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 32.3 kB or 67% of the original size.

Image Optimization

-4%

Potential reduce by 34.6 kB

  • Original 964.6 kB
  • After minification 930.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. Dragon Ball Z images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 12.4 kB

  • Original 100.8 kB
  • After minification 100.8 kB
  • After compression 88.4 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 12.4 kB or 12% of the original size.

CSS Optimization

-24%

Potential reduce by 2.8 kB

  • Original 11.8 kB
  • After minification 11.8 kB
  • After compression 9.0 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. Dragonballz.com needs all CSS files to be minified and compressed as it can save up to 2.8 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (66%)

Requests Now

68

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dragon Ball Z. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

dragonballz.com

dragonballz.com

28 ms

styles.css

styles.css

6 ms

jquery-2.1.4.min.js

jquery-2.1.4.min.js

7 ms

header.css

header.css

20 ms

style.css

style.css

4 ms

landing.css

landing.css

6 ms

jquery.fancybox.css

jquery.fancybox.css

20 ms

jquery.fancybox-thumbs.css

jquery.fancybox-thumbs.css

18 ms

jquery.fancybox.js

jquery.fancybox.js

22 ms

flexslider.js

flexslider.js

27 ms

flexslider.css

flexslider.css

21 ms

shared.js

shared.js

28 ms

gtm.js

gtm.js

61 ms

background-50.jpg

background-50.jpg

56 ms

headerlogo.png

headerlogo.png

56 ms

toei-logo.png

toei-logo.png

55 ms

orange_button.png

orange_button.png

493 ms

01.jpg

01.jpg

1011 ms

boxart-combo.jpg

boxart-combo.jpg

1437 ms

boxart-dvd.jpg

boxart-dvd.jpg

56 ms

boxart-collectors.jpg

boxart-collectors.jpg

57 ms

digitalhd-home.jpg

digitalhd-home.jpg

57 ms

slider-repeater.jpg

slider-repeater.jpg

50 ms

db.png

db.png

50 ms

content.json

content.json

14 ms

Antenna-Regular.woff

Antenna-Regular.woff

8 ms

Molot.woff

Molot.woff

9 ms

Antenna-Bold.woff

Antenna-Bold.woff

1416 ms

dbz.ttf

dbz.ttf

9 ms

gtm.js

gtm.js

61 ms

analytics.js

analytics.js

7 ms

tag.js

tag.js

29 ms

56 ms

bat.js

bat.js

29 ms

ec.js

ec.js

18 ms

collect

collect

51 ms

collect

collect

50 ms

collect

collect

42 ms

collect

collect

40 ms

trackpoint-async.js

trackpoint-async.js

56 ms

11 ms

11 ms

12 ms

pixels

pixels

67 ms

308 ms

activityi;src=8299517;type=invmedia;cat=zi6yk7hm;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=399733101949.0957

activityi;src=8299517;type=invmedia;cat=zi6yk7hm;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=399733101949.0957

94 ms

ytc.js

ytc.js

34 ms

10050030.json

10050030.json

21 ms

user-registering

user-registering

229 ms

29729

29729

300 ms

click

click

410 ms

usermatch.gif

usermatch.gif

34 ms

pixel

pixel

236 ms

Pug

Pug

218 ms

cs

cs

325 ms

generic

generic

224 ms

um

um

261 ms

280 ms

put

put

213 ms

33302

33302

291 ms

src=8299517;type=invmedia;cat=zi6yk7hm;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=399733101949.0957

src=8299517;type=invmedia;cat=zi6yk7hm;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=399733101949.0957

244 ms

match

match

25 ms

gdpr_consent=

gdpr_consent=

35 ms

generic

generic

16 ms

83 ms

xuid

xuid

17 ms

pixel

pixel

94 ms

match

match

30 ms

match

match

29 ms

rum

rum

43 ms

pixel

pixel

99 ms

sd

sd

48 ms

75 ms

pixel.gif

pixel.gif

151 ms

info2

info2

48 ms

setuid

setuid

54 ms

10 ms

10 ms

pixel.gif

pixel.gif

290 ms

match

match

10 ms

pixel

pixel

18 ms

11 ms

p

p

70 ms

3.gif

3.gif

98 ms

Accessibility Review

dragonballz.com accessibility score

50

Accessibility Issues

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

dragonballz.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

dragonballz.com SEO score

92

Search Engine Optimization Advices

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

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 Dragonballz.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 Dragonballz.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

dragonballz.com

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