Tools & Wizards About Us
bumblebee.tv screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

bumblebee.tv

ViewNexa TV

Page Load Speed

1.8 sec in total

First Response

36 ms

Resources Loaded

1.6 sec

Page Rendered

79 ms

bumblebee.tv screenshot

About Website

Click here to check amazing Bumblebee content for United States. Otherwise, check out these important facts you probably never knew about bumblebee.tv

{{ $root.metadata.description }}

Visit bumblebee.tv

Key Findings

We analyzed Bumblebee.tv page load time and found that the first response time was 36 ms and then it took 1.7 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

bumblebee.tv performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value15.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value28.3 s

0/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value4,840 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.406

24/100

15%

TTI (Time to Interactive)

Value28.1 s

0/100

10%

Network Requests Diagram

bumblebee.tv

36 ms

bumblebee.tv

252 ms

font-awesome.min.css

253 ms

toastr.min.css

267 ms

rzslider.min.css

256 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 23% of them (18 requests) were addressed to the original Bumblebee.tv, 31% (25 requests) were made to Cdnjs.cloudflare.com and 10% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (727 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 527.7 kB (31%)

Content Size

1.7 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bumblebee.tv main page is 1.7 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. Only a small number of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 24.8 kB

  • Original 35.5 kB
  • After minification 35.3 kB
  • After compression 10.7 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 24.8 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 3.0 kB
  • After minification 3.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. Bumblebee images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 502.7 kB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 1.1 MB

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 502.7 kB or 31% of the original size.

CSS Optimization

-0%

Potential reduce by 231 B

  • Original 55.3 kB
  • After minification 55.3 kB
  • After compression 55.1 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. Bumblebee.tv has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 64 (91%)

Requests Now

70

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bumblebee.tv

bumblebee.tv

36 ms

bumblebee.tv

bumblebee.tv

252 ms

font-awesome.min.css

font-awesome.min.css

253 ms

toastr.min.css

toastr.min.css

267 ms

rzslider.min.css

rzslider.min.css

256 ms

css

css

255 ms

style.css

style.css

254 ms

angular-dropdowns.min.css

angular-dropdowns.min.css

25 ms

video-js.min.css

video-js.min.css

258 ms

videojs.ads.css

videojs.ads.css

283 ms

videojs.ima.min.css

videojs.ima.min.css

260 ms

unreel-player-39e5848b33.min.css

unreel-player-39e5848b33.min.css

163 ms

reset.css

reset.css

246 ms

bootstrap.min.css

bootstrap.min.css

284 ms

smartbanner.min.css

smartbanner.min.css

254 ms

dark-5c6df853ae.css

dark-5c6df853ae.css

267 ms

js

js

421 ms

gpt.js

gpt.js

329 ms

api.js

api.js

299 ms

jquery.min.js

jquery.min.js

302 ms

jquery.embedly.min.js

jquery.embedly.min.js

298 ms

moment.min.js

moment.min.js

301 ms

countdown.min.js

countdown.min.js

398 ms

fastclick.min.js

fastclick.min.js

297 ms

clipboard.min.js

clipboard.min.js

322 ms

angular.min.js

angular.min.js

326 ms

angular-ui-router.min.js

angular-ui-router.min.js

331 ms

angular-cookies.min.js

angular-cookies.min.js

328 ms

elasticsearch.angular.min.js

elasticsearch.angular.min.js

390 ms

toastr.min.js

toastr.min.js

330 ms

rzslider.min.js

rzslider.min.js

390 ms

lodash.min.js

lodash.min.js

299 ms

iframe_api

iframe_api

321 ms

video.min.js

video.min.js

331 ms

pubnub.4.27.4.min.js

pubnub.4.27.4.min.js

326 ms

ima3.js

ima3.js

320 ms

ima3_dai.js

ima3_dai.js

392 ms

dash.all.min.js

dash.all.min.js

391 ms

videojs.ads.min.js

videojs.ads.min.js

330 ms

videojs-dash.min.js

videojs-dash.min.js

385 ms

videojs-contrib-eme.min.js

videojs-contrib-eme.min.js

309 ms

videojs.ima.min.js

videojs.ima.min.js

382 ms

hls.js@0.12.4

hls.js@0.12.4

381 ms

videojs-ttml.js

videojs-ttml.js

238 ms

can-autoplay.min.js

can-autoplay.min.js

242 ms

videojs-event-tracking.min.js

videojs-event-tracking.min.js

242 ms

ellipsis.min.js

ellipsis.min.js

245 ms

ui-bootstrap-tpls.min.js

ui-bootstrap-tpls.min.js

399 ms

api.js

api.js

241 ms

index.min.js

index.min.js

402 ms

ng-FitText.min.js

ng-FitText.min.js

399 ms

angular-animate.min.js

angular-animate.min.js

400 ms

angular-sanitize.min.js

angular-sanitize.min.js

401 ms

angular-dropdowns.js

angular-dropdowns.js

261 ms

angular-credit-cards.js

angular-credit-cards.js

261 ms

smartbanner.min.js

smartbanner.min.js

278 ms

v3

v3

310 ms

unreel-player-4d8f63e49d.min.js

unreel-player-4d8f63e49d.min.js

309 ms

unreel-fullscreen-03336f2e50.min.js

unreel-fullscreen-03336f2e50.min.js

373 ms

recaptcha__en.js

recaptcha__en.js

576 ms

NaPDcZTIAOhVxoMyOr9n_E7ffHjDGItzZg.ttf

NaPDcZTIAOhVxoMyOr9n_E7ffHjDGItzZg.ttf

553 ms

NaPDcZTIAOhVxoMyOr9n_E7ffBzCGItzZg.ttf

NaPDcZTIAOhVxoMyOr9n_E7ffBzCGItzZg.ttf

628 ms

NaPecZTIAOhVxoMyOr9n_E7fdMPmCA.ttf

NaPecZTIAOhVxoMyOr9n_E7fdMPmCA.ttf

717 ms

NaPDcZTIAOhVxoMyOr9n_E7ffGjEGItzZg.ttf

NaPDcZTIAOhVxoMyOr9n_E7ffGjEGItzZg.ttf

717 ms

NaPDcZTIAOhVxoMyOr9n_E7ffAzHGItzZg.ttf

NaPDcZTIAOhVxoMyOr9n_E7ffAzHGItzZg.ttf

727 ms

pubads_impl.js

pubads_impl.js

576 ms

ppub_config

ppub_config

664 ms

www-widgetapi.js

www-widgetapi.js

390 ms

loader.js

loader.js

527 ms

anchor

anchor

119 ms

white.png

white.png

18 ms

styles__ltr.css

styles__ltr.css

11 ms

recaptcha__en.js

recaptcha__en.js

32 ms

RI3Pk2QfVraTqUQvmENYAwISRapPH8Lx3ZoW8uCkQH4.js

RI3Pk2QfVraTqUQvmENYAwISRapPH8Lx3ZoW8uCkQH4.js

46 ms

webworker.js

webworker.js

41 ms

logo_48.png

logo_48.png

28 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

43 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

43 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

43 ms

recaptcha__en.js

recaptcha__en.js

41 ms

Accessibility Review

bumblebee.tv accessibility score

79

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

bumblebee.tv best practices score

75

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

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

bumblebee.tv SEO score

91

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

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 Bumblebee.tv 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 Bumblebee.tv 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

bumblebee.tv

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