11.3 sec in total
471 ms
4.6 sec
6.3 sec
Click here to check amazing Beacon content. Otherwise, check out these important facts you probably never knew about beacon.co.za
Beacon has a wide variety of quality sweets and treats! Be inspired by our recipes and ideas and make every moment count with Beacon.
Visit beacon.co.zaWe analyzed Beacon.co.za page load time and found that the first response time was 471 ms and then it took 10.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
beacon.co.za performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value10.2 s
0/100
25%
Value8.0 s
21/100
10%
Value360 ms
72/100
30%
Value0.037
100/100
15%
Value9.1 s
33/100
10%
471 ms
1651 ms
186 ms
413 ms
277 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 96% of them (52 requests) were addressed to the original Beacon.co.za, 2% (1 request) were made to Googletagmanager.com and 2% (1 request) were made to Static.hotjar.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Beacon.co.za.
Page size can be reduced by 2.5 MB (9%)
28.6 MB
26.1 MB
In fact, the total size of Beacon.co.za main page is 28.6 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. 60% of websites need less resources to load. Images take 27.9 MB which makes up the majority of the site volume.
Potential reduce by 26.0 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 26.0 kB or 76% of the original size.
Potential reduce by 2.3 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. Beacon images are well optimized though.
Potential reduce by 136.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 136.4 kB or 24% of the original size.
Potential reduce by 79.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. Beacon.co.za needs all CSS files to be minified and compressed as it can save up to 79.0 kB or 61% of the original size.
Number of requests can be reduced by 15 (31%)
48
33
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Beacon. 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 4 to 1 for CSS and as a result speed up the page load time.
beacon.co.za
471 ms
www.beacon.co.za
1651 ms
optimized-min.css
186 ms
optimized-min.css
413 ms
optimized-min.css
277 ms
optimized-min.css
644 ms
VisitorIdentification.js
299 ms
optimized-min.js
614 ms
optimized-min.js
698 ms
optimized-min.js
374 ms
optimized-min.js
397 ms
optimized-min.js
470 ms
optimized-min.js
492 ms
optimized-min.js
519 ms
optimized-min.js
798 ms
optimized-min.js
609 ms
optimized-min.js
817 ms
gtm.js
230 ms
hotjar-2272453.js
232 ms
sweets-background.png
231 ms
beacon-logo-shadow.png
250 ms
smile-large.png
229 ms
Beacon_MelkTert-HomeSliders.png
514 ms
Beacon_MelkTert-HomeSliders-Mobi.png
750 ms
Beacon_GuessTheFlavour-HomeSliders.png
544 ms
Beacon_GuessTheFlavour-HomeSliders-Mobi.png
606 ms
Mallows-Homepage-Slider-Desktop.png
543 ms
Mallows-Homepage-Slider-Desktop---Mobile.jpg
785 ms
jelly-tots.jpg
634 ms
jelly-tots.jpg
709 ms
Allsorts-Q2-Homepage-Slider-Web.png
771 ms
Allsorts-Q2-Homepage-Slider-Web-Mobile.png
854 ms
Maynards-Brand-Clarity-HomeSlider-Q3.png
781 ms
Maynards-Brand-Clarity-HomePage-Slider-Mobi-Q3.jpg
863 ms
hero-curve.png
857 ms
Beacon_MelkTert-Footer-Banner.png
898 ms
Beacon_MelkTert-Footer-Mobi.png
913 ms
beacon-logo.svg
907 ms
fb-icon.png
1010 ms
twitter-icon.png
1011 ms
instagram-icon.png
1015 ms
footer-top.png
863 ms
overlay-bg.png
861 ms
928 ms
ionicons.woff
884 ms
pacifico-regular-webfont-woff.woff
898 ms
fontawesome-webfont-woff.woff
959 ms
fontawesome-webfont-woff.woff
935 ms
Beacon-Treats-to-Complement-Your-Fun-Activities-(1).jpg
297 ms
Discover-your-personality-type.jpg
417 ms
shutterstock_1408567424.jpg
602 ms
4-Creative-Ways-to-Decorate-an-Indoor-Picnic.jpg
356 ms
Beacon_MandelaDayArticle_650X500.jpg
189 ms
3-microwave-mug-cakes.jpg
333 ms
beacon.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
beacon.co.za 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
Missing source maps for large first-party JavaScript
beacon.co.za SEO score
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
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Beacon.co.za can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Beacon.co.za main page’s claimed encoding is . 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.
beacon.co.za
Open Graph data is detected on the main page of Beacon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: