Tools & Wizards About Us
royalbee.buzz screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

royalbee.buzz

Royal Bee • Skin Care, Soaps, Books, Candles & More

Page Load Speed

2.2 sec in total

First Response

174 ms

Resources Loaded

1.3 sec

Page Rendered

766 ms

royalbee.buzz screenshot

About Website

Welcome to royalbee.buzz homepage info - get ready to check Royal Bee best content right away, or after learning these important things about royalbee.buzz

Royal Bee is in pursuit to give back to the bees and to the world. Buy Top Bee Skin products derived from Bees: Skin Care, Books, Candles & More!

Visit royalbee.buzz

Key Findings

We analyzed Royalbee.buzz page load time and found that the first response time was 174 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

royalbee.buzz performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value8.0 s

43/100

10%

Network Requests Diagram

royalbee.buzz

174 ms

style.min.css

414 ms

vendors-style.css

303 ms

style.css

507 ms

menu-image.css

313 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 77% of them (49 requests) were addressed to the original Royalbee.buzz, 9% (6 requests) were made to Google-analytics.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (759 ms) belongs to the original domain Royalbee.buzz.

Page Optimization Overview & Recommendations

Page size can be reduced by 241.5 kB (11%)

Content Size

2.2 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royalbee.buzz main page is 2.2 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. 50% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 42.4 kB

  • Original 52.0 kB
  • After minification 50.6 kB
  • After compression 9.6 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 42.4 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 34.3 kB

  • Original 1.7 MB
  • After minification 1.7 MB

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. Royal Bee images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 3.9 kB

  • Original 107.5 kB
  • After minification 107.1 kB
  • After compression 103.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.

CSS Optimization

-55%

Potential reduce by 160.9 kB

  • Original 291.9 kB
  • After minification 288.2 kB
  • After compression 131.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. Royalbee.buzz needs all CSS files to be minified and compressed as it can save up to 160.9 kB or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (57%)

Requests Now

63

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royalbee.buzz

royalbee.buzz

174 ms

style.min.css

style.min.css

414 ms

vendors-style.css

vendors-style.css

303 ms

style.css

style.css

507 ms

menu-image.css

menu-image.css

313 ms

dashicons.min.css

dashicons.min.css

444 ms

fontello.css

fontello.css

380 ms

front.min.css

front.min.css

368 ms

genericons-neue.css

genericons-neue.css

442 ms

main.css

main.css

627 ms

custom-styles.css

custom-styles.css

446 ms

woocommerce.css

woocommerce.css

541 ms

custom-styles-woocommerce.css

custom-styles-woocommerce.css

515 ms

style.css

style.css

516 ms

7660-layout.css

7660-layout.css

518 ms

css-vars-ponyfill.min.js

css-vars-ponyfill.min.js

571 ms

jquery.min.js

jquery.min.js

637 ms

jquery-migrate.min.js

jquery-migrate.min.js

572 ms

front.min.js

front.min.js

575 ms

js

js

60 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

604 ms

add-to-cart.min.js

add-to-cart.min.js

636 ms

js.cookie.min.js

js.cookie.min.js

709 ms

woocommerce.min.js

woocommerce.min.js

710 ms

cart-fragments.min.js

cart-fragments.min.js

711 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

712 ms

scripts-navigation-accessibility.js

scripts-navigation-accessibility.js

713 ms

scripts-navigation-mobile.js

scripts-navigation-mobile.js

715 ms

scripts-global.js

scripts-global.js

714 ms

scripts-woocommerce.js

scripts-woocommerce.js

717 ms

7660-layout.js

7660-layout.js

756 ms

wp-embed.min.js

wp-embed.min.js

759 ms

css

css

30 ms

css

css

42 ms

analytics.js

analytics.js

62 ms

royal-bee-logo.png

royal-bee-logo.png

168 ms

royal-bee-logo.png

royal-bee-logo.png

168 ms

Royal-Bee-Mobile-Banner.jpg

Royal-Bee-Mobile-Banner.jpg

168 ms

Banner2.jpg

Banner2.jpg

186 ms

Royal-Bee-Homepage-New-Final_02.jpg

Royal-Bee-Homepage-New-Final_02.jpg

185 ms

rb-2.jpg

rb-2.jpg

185 ms

Planet-Logo-283x320.png

Planet-Logo-283x320.png

296 ms

Royal-Bee-Homepage-New-Final_09.jpg

Royal-Bee-Homepage-New-Final_09.jpg

302 ms

rb-4.jpg

rb-4.jpg

238 ms

rb-5.jpg

rb-5.jpg

233 ms

rb-3.jpg

rb-3.jpg

236 ms

rb-6.jpg

rb-6.jpg

240 ms

rb-7.jpg

rb-7.jpg

298 ms

rb-8.jpg

rb-8.jpg

302 ms

rb-9.jpg

rb-9.jpg

304 ms

rb-10.jpg

rb-10.jpg

307 ms

rb-11.jpg

rb-11.jpg

426 ms

pixabay-colorado-1436681.png

pixabay-colorado-1436681.png

365 ms

js

js

123 ms

analytics.js

analytics.js

99 ms

font

font

98 ms

linkid.js

linkid.js

100 ms

ec.js

ec.js

100 ms

collect

collect

15 ms

collect

collect

13 ms

collect

collect

26 ms

collect

collect

22 ms

ga-audiences

ga-audiences

29 ms

ga-audiences

ga-audiences

23 ms

Accessibility Review

royalbee.buzz accessibility score

98

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.

Best Practices

royalbee.buzz best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

SEO Factors

royalbee.buzz SEO score

86

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

Links do not have descriptive text

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

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 Royalbee.buzz 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 Royalbee.buzz 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

royalbee.buzz

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