19.3 sec in total
1 sec
17.9 sec
395 ms
Click here to check amazing Busy Bee content. Otherwise, check out these important facts you probably never knew about busybee.com.au
Busy Bee Brushware is a family owned company based in Dandenong South, Victoria, specialising in manufacturing custom and industrial Brushware. Australian Owned
Visit busybee.com.auWe analyzed Busybee.com.au page load time and found that the first response time was 1 sec and then it took 18.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
busybee.com.au performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value17.8 s
0/100
25%
Value15.5 s
0/100
10%
Value1,670 ms
11/100
30%
Value1.17
1/100
15%
Value20.7 s
2/100
10%
1033 ms
1003 ms
4668 ms
1494 ms
1486 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 81% of them (58 requests) were addressed to the original Busybee.com.au, 3% (2 requests) were made to Maxcdn.bootstrapcdn.com and 3% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (7.1 sec) belongs to the original domain Busybee.com.au.
Page size can be reduced by 1.2 MB (53%)
2.2 MB
1.0 MB
In fact, the total size of Busybee.com.au 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.
Potential reduce by 44.4 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. This page needs HTML code to be minified as it can gain 9.1 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 44.4 kB or 81% of the original size.
Potential reduce by 766.8 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. Obviously, Busy Bee needs image optimization as it can save up to 766.8 kB or 46% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 227.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 227.6 kB or 66% of the original size.
Potential reduce by 148.3 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. Busybee.com.au needs all CSS files to be minified and compressed as it can save up to 148.3 kB or 85% of the original size.
Number of requests can be reduced by 31 (48%)
65
34
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Busy 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 13 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
busybee.com.au
1033 ms
busybee.com.au
1003 ms
www.busybee.com.au
4668 ms
stylesheet.css
1494 ms
jquery.mmenu.all.css
1486 ms
font-awesome.min.css
60 ms
owl.carousel.css
763 ms
owl.theme.css
765 ms
responsive.css
1307 ms
default.css
984 ms
slideshow.css
1505 ms
jquery-1.11.3.min.js
97 ms
jquery-migrate-1.2.1.min.js
81 ms
jquery.mmenu.min.all.js
2231 ms
owl.carousel.min.js
2233 ms
jquery-ui-1.8.16.custom.min.js
3577 ms
jquery-ui-1.8.16.custom.css
2938 ms
jquery.cookie.js
2236 ms
jquery.fancybox-1.3.4.pack.js
2724 ms
jquery.fancybox-1.3.4.css
3201 ms
tabs.js
2963 ms
common.js
3208 ms
jquery.nivo.slider.pack.js
3747 ms
analytics.js
216 ms
ga.js
217 ms
verified-seal.ashx
888 ms
2000px-F_icon.svg.png
202 ms
g+128.png
310 ms
bkg.png
756 ms
stylesheet.css
1481 ms
shopping-cart.png
762 ms
busy-bee-logo.png
1042 ms
mobile.png
757 ms
main-banner-2-940x299.jpg
1543 ms
Ember-Seal-Banner-940x299.jpg
2471 ms
FlueBanner-940x299.jpg
2505 ms
AustMadeBanner-940x299-940x299.jpg
2512 ms
showroom-banner-940x299.jpg
2753 ms
estorebanner-940x299.jpg
3204 ms
ContactUs-940x299.jpg
3299 ms
main-banner-4-940x299.jpg
4177 ms
PayPal-banner-940x299.png
5943 ms
tab-1.jpg
3969 ms
tab-2.jpg
4218 ms
tab-3.jpg
4660 ms
Strip%20Brush%20and%20Garage%20Door%20Seals%20SAMPLE%20PACK-115x115.jpg
4036 ms
stars-5.png
4718 ms
details.png
4776 ms
add-to-cart.png
4911 ms
Garage%20Door%20Seals%20Fire%20Retardant%20Options-115x115.jpg
4968 ms
Strip%20Brush%20Options%204mm%20Nylon%20fibre%20Zincseal%20back-115x115.jpg
5398 ms
red_black-strip-115x115.png
6455 ms
BSW_PP06-600x600-115x115.jpg
5539 ms
Flexi%20Flue%20Brush%20Kit_1-115x115.jpg
5655 ms
Cofee-115x115.jpg
5710 ms
WB%20K10-300%20Complete%2010%20Bi%20Level%20Kit-115x115.jpg
6140 ms
email3.png
6275 ms
paypal.png
6381 ms
sdk.js
219 ms
header-bee.png
6958 ms
arrow-down.png
6662 ms
menu-arrow.png
6865 ms
button-search.png
6989 ms
loading.gif
7101 ms
footer-bkg.png
7148 ms
fontawesome-webfont.woff
28 ms
collect
62 ms
__utm.gif
40 ms
37 ms
xd_arbiter.php
47 ms
arrows.png
6663 ms
bullets.png
6858 ms
busybee.com.au 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
Buttons do not have an accessible name
Links do not have a discernible name
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
busybee.com.au 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
General
Impact
Issue
Detected JavaScript libraries
busybee.com.au SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Busybee.com.au 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 Busybee.com.au main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
busybee.com.au
Open Graph description is not detected on the main page of Busy Bee. 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: