8.7 sec in total
805 ms
7.4 sec
470 ms
Welcome to burgessflorist.co.za homepage info - get ready to check Burgess Florist best content for South Africa right away, or after learning these important things about burgessflorist.co.za
Our online flower and gift delivery service for Durban and surrounding areas.
Visit burgessflorist.co.zaWe analyzed Burgessflorist.co.za page load time and found that the first response time was 805 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
burgessflorist.co.za performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value8.2 s
2/100
25%
Value12.8 s
2/100
10%
Value0 ms
100/100
30%
Value0.062
97/100
15%
Value7.9 s
43/100
10%
805 ms
255 ms
507 ms
1016 ms
507 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that all of those requests were addressed to Burgessflorist.co.za and no external sources were called. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Burgessflorist.co.za.
Page size can be reduced by 247.5 kB (16%)
1.5 MB
1.3 MB
In fact, the total size of Burgessflorist.co.za main page is 1.5 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. 30% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 38.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 38.7 kB or 83% of the original size.
Potential reduce by 95.1 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. Burgess Florist images are well optimized though.
Potential reduce by 108.7 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 108.7 kB or 70% of the original size.
Potential reduce by 5.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. Burgessflorist.co.za needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 82% of the original size.
Number of requests can be reduced by 72 (65%)
110
38
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Burgess Florist. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
burgessflorist.co.za
805 ms
wpstyles.css
255 ms
nav_3style.css
507 ms
jquery.js
1016 ms
jsNavBarFuncs.js
507 ms
wp_navbar_textmenu.js
506 ms
nav_3tree.js
507 ms
jquery.event.move.js
507 ms
jquery.event.swipe.js
756 ms
jquery.wpslider.js
756 ms
wpb9c936ad_1a.jpg
1266 ms
img_282.png
257 ms
img_281.png
257 ms
burgess_florist_logo_image.PNG
511 ms
grp_3.png
512 ms
pcrv_29.png
257 ms
pcrv_30.png
512 ms
pcrv_31.png
509 ms
pcrv_32.png
509 ms
pcrv_33.png
760 ms
pcrv_34.png
761 ms
pcrv_35.png
762 ms
pcrv_36.png
762 ms
pcrv_37.png
764 ms
pcrv_38.png
1013 ms
pcrv_39.png
1011 ms
pcrv_40.png
1015 ms
pcrv_41.png
1014 ms
pcrv_42.png
1015 ms
pcrv_43.png
1261 ms
pcrv_44.png
1263 ms
pcrv_45.png
1262 ms
pcrv_46.png
1264 ms
pcrv_47.png
1264 ms
pcrv_48.png
1512 ms
pcrv_49.png
1510 ms
pcrv_50.png
1513 ms
pcrv_51.png
1513 ms
pcrv_52.png
1515 ms
pcrv_53.png
1516 ms
Converted%201.png
1760 ms
Converted%201-1.png
1763 ms
img_15.png
1762 ms
img_16.png
1764 ms
img_17.png
1764 ms
img_18.png
1734 ms
img_19.png
1767 ms
img_20.png
1767 ms
img_21.png
1767 ms
img_22.png
1515 ms
img_23.png
1517 ms
img_24.png
1516 ms
img_25.png
1765 ms
img_26.png
1766 ms
img_27.png
1518 ms
img_28.png
1517 ms
img_29.png
1764 ms
img_30.png
1763 ms
wp94ccbaec_1a.png
1764 ms
wp9d2eead8_1a.png
1515 ms
img_34.png
1516 ms
img_35.png
1516 ms
img_36.png
1753 ms
img_37.png
1753 ms
img_38.png
1520 ms
img_39.png
1518 ms
img_160.png
1519 ms
wp8b511527_1a.png
1518 ms
wpaa5ebec8_1a.png
1765 ms
wpf8d18264_1a.png
1764 ms
wpfe6aa5af_1a.png
1519 ms
wp07de7a48_1a.png
1518 ms
wpe982bf05_1a.png
1518 ms
wp72bdcf89_1a.png
1519 ms
wp109a098f_1a.png
1763 ms
Converted%201-2.png
1765 ms
block.png
1519 ms
block2.png
1518 ms
Print.png
1519 ms
wp54f3491f_1a.png
1519 ms
wp5533b116.gif
1766 ms
wp3fd64ae5_1a.png
1767 ms
wp11395609_1a.png
1520 ms
wp38f96e96_1a.png
1520 ms
wp205911d0_1a.png
1522 ms
img_286.png
1520 ms
img_287.png
1766 ms
wp7d4483e9_1a.png
1767 ms
wp24251933_1a.png
1518 ms
wp64ba37b2_1a.png
1521 ms
wp6d57c250_1a.png
2027 ms
wp667a1da7_05_1a.jpg
2330 ms
rosesheader.jpg
2531 ms
wp9c6b0b7b_05_1a.jpg
2025 ms
colourarrangementinvase.jpg
2789 ms
wpad68f1d2_05_1a.jpg
2036 ms
wp440f2002_1a.png
2026 ms
wpdcdb789c_05_1a.jpg
2529 ms
wp2fd3f442_1a.png
2034 ms
rosewater.jpg
2047 ms
wp3291489f_1a.png
2080 ms
wp32f899a9_1a.png
2283 ms
wp1c0c6dba_1a.png
2296 ms
wp5999b757_1a.png
2332 ms
valentine-3%202016.jpg
2282 ms
valentine-4%202016.jpg
2284 ms
valentine%202016.jpg
2285 ms
valentine-2%202016.jpg
2300 ms
wp7eb336ed_1a.png
2333 ms
wp7dd821e9_1a.png
2531 ms
wpc5aefeae_1a.png
2288 ms
burgessflorist.co.za 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
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.
burgessflorist.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
Browser errors were logged to the console
burgessflorist.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Burgessflorist.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 Burgessflorist.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.
burgessflorist.co.za
Open Graph description is not detected on the main page of Burgess Florist. 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: