12 sec in total
2.4 sec
9.2 sec
470 ms
Welcome to honeybeebaker.co.za homepage info - get ready to check Honey Bee Baker best content right away, or after learning these important things about honeybeebaker.co.za
Visit honeybeebaker.co.zaWe analyzed Honeybeebaker.co.za page load time and found that the first response time was 2.4 sec and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
honeybeebaker.co.za performance score
name
value
score
weighting
Value6.8 s
1/100
10%
Value10.1 s
0/100
25%
Value14.4 s
1/100
10%
Value670 ms
44/100
30%
Value0
100/100
15%
Value11.2 s
20/100
10%
2358 ms
494 ms
1229 ms
738 ms
743 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 82% of them (54 requests) were addressed to the original Honeybeebaker.co.za, 9% (6 requests) were made to Use.typekit.net and 3% (2 requests) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Honeybeebaker.co.za.
Page size can be reduced by 107.3 kB (8%)
1.4 MB
1.3 MB
In fact, the total size of Honeybeebaker.co.za main page is 1.4 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 41.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 41.1 kB or 78% of the original size.
Potential reduce by 65.4 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. Honey Bee Baker images are well optimized though.
Potential reduce by 281 B
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.
Potential reduce by 481 B
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. Honeybeebaker.co.za has all CSS files already compressed.
Number of requests can be reduced by 42 (72%)
58
16
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Honey Bee Baker. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
www.honeybeebaker.co.za
2358 ms
easy-modal-site.css
494 ms
js_composer.min.css
1229 ms
view.css
738 ms
mediaelementplayer-legacy.min.css
743 ms
wp-mediaelement.min.css
739 ms
classic-themes.min.css
745 ms
styles.css
741 ms
public.min.css
983 ms
wpex-woocommerce.css
988 ms
css2
47 ms
ticons.min.css
998 ms
style.css
1246 ms
wpex-mobile-menu-breakpoint-min.css
996 ms
wpex-wpbakery.css
1242 ms
vcex-shortcodes.css
1244 ms
frontend.css
1256 ms
jetpack.css
1256 ms
jquery.min.js
1474 ms
jquery-migrate.min.js
1485 ms
jquery.blockUI.min.js
1488 ms
add-to-cart.min.js
1488 ms
woocommerce-add-to-cart.js
1490 ms
s-202444.js
29 ms
efm8lqk.css
135 ms
js
61 ms
core.min.js
1289 ms
jquery.transit.min.js
1481 ms
easy-modal-site.js
1483 ms
index.js
1489 ms
index.js
1491 ms
js.cookie.min.js
1498 ms
woocommerce.min.js
1505 ms
public.min.js
1725 ms
wpex-wc-functions.min.js
1729 ms
hoverIntent.min.js
1734 ms
wpex-superfish.min.js
1739 ms
jquery.easing.min.js
1761 ms
total.min.js
1763 ms
e-202444.js
2 ms
wpex-wc-cart-dropdown.min.js
1969 ms
cart-fragments.min.js
1972 ms
js_composer_front.min.js
1735 ms
p.css
38 ms
Final-logo_2-2.svg
752 ms
homepage.jpg
1909 ms
802AA139-E95D-4DE5-B64A-748DE3C526F4-scaled-800x533.jpeg
694 ms
1.jpeg
1146 ms
10B9B576-E51C-40D8-BA2F-A22AAD3EBA19.jpeg
1641 ms
backgroundnewbrush-2.jpg
1655 ms
5BF4D559-84E6-4B73-B0F2-CB8119BE8FFE-1.jpeg
1655 ms
leave-1-100x25.png
939 ms
HONEY-BEEB-355x533.jpg
1187 ms
55A0CE0A-CC6E-4DB9-9AA7-0483DADE6EFD-355x533.jpeg
1392 ms
HONEY-BEEB-13-355x533.jpg
1436 ms
AC7E791C-4BE0-4A4B-9BDB-7EC17FED0C37-355x533.jpeg
1637 ms
font
40 ms
d
14 ms
d
20 ms
d
22 ms
d
21 ms
d
21 ms
AdeliciaScript.woff
1883 ms
ticons.woff
2081 ms
www.honeybeebaker.co.za
2390 ms
wpex-mobile-menu-breakpoint-max.css
250 ms
honeybeebaker.co.za 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.
honeybeebaker.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
honeybeebaker.co.za 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Honeybeebaker.co.za 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 Honeybeebaker.co.za 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.
honeybeebaker.co.za
Open Graph description is not detected on the main page of Honey Bee Baker. 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: