8.5 sec in total
710 ms
7.5 sec
336 ms
Visit bloom.com.my now to see the best up-to-date Bloom content for Malaysia and also check out these interesting facts you probably never knew about bloom.com.my
Florist in KL (Kuala Lumpur). Flower Shop Petaling Jaya delight you with creative arrangements. Great Kuala Lumpur Flower Shop Brings Genuine Love To Your Recipient. Deliver Too to Petaling Jaya (PJ),...
Visit bloom.com.myWe analyzed Bloom.com.my page load time and found that the first response time was 710 ms and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
bloom.com.my performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value13.6 s
0/100
25%
Value19.1 s
0/100
10%
Value660 ms
45/100
30%
Value0.137
79/100
15%
Value15.1 s
7/100
10%
710 ms
966 ms
732 ms
1810 ms
61 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 60% of them (38 requests) were addressed to the original Bloom.com.my, 21% (13 requests) were made to Embed.tawk.to and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Bloom.com.my.
Page size can be reduced by 307.8 kB (40%)
777.6 kB
469.8 kB
In fact, the total size of Bloom.com.my main page is 777.6 kB. 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. HTML takes 339.9 kB which makes up the majority of the site volume.
Potential reduce by 282.5 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 282.5 kB or 83% of the original size.
Potential reduce by 445 B
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. Bloom images are well optimized though.
Potential reduce by 24.9 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.
Number of requests can be reduced by 35 (64%)
55
20
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bloom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and as a result speed up the page load time.
bloom.com.my
710 ms
bloom.com.my
966 ms
www.bloom.com.my
732 ms
www.bloom.com.my
1810 ms
gtm.js
61 ms
vue.min.js
51 ms
anime.min.js
88 ms
hammer.min.js
90 ms
bloom-home-3.png
351 ms
whatsapp-50.png
587 ms
phone_icon.png
703 ms
email_icon.png
704 ms
search_icon.png
717 ms
lorry.png
732 ms
order_status_icon.png
734 ms
cart_icon.png
822 ms
checkout_icon.png
936 ms
500_select_banner.jpg
937 ms
delivery_service_banner.jpg
956 ms
free_delivery_banner.jpg
975 ms
520---2021.gif
2204 ms
Special-Promo.gif
2000 ms
Pay-Less-Promo.gif
2095 ms
Express-Delivery.gif
2343 ms
Free-Delivery-Promo.gif
2404 ms
js
70 ms
glyphicons-halflings-regular.woff
1441 ms
jquery-1.10.2.min.js
1763 ms
bootstrap-337.min.js
2010 ms
jquery-ui.min.js
2047 ms
lib-min.js
2129 ms
lazyload.js
2249 ms
css
90 ms
ghostbtn.js
2344 ms
grey.gif
2345 ms
payment_method.png
2425 ms
logo1.png
2424 ms
flower_icon.png
2424 ms
quote.png
2460 ms
quote-close.png
2464 ms
social_new.png
2460 ms
analytics.js
7 ms
default
200 ms
collect
17 ms
js
51 ms
jquery.touchwipe.min.js
380 ms
KFOmCnqEu92Fr1Mu4mxM.woff
81 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
91 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
92 ms
popupimg-1521433637-3.jpg
318 ms
close.png
319 ms
twk-arr-find-polyfill.js
64 ms
twk-object-values-polyfill.js
244 ms
twk-event-polyfill.js
243 ms
twk-entries-polyfill.js
75 ms
twk-iterator-polyfill.js
243 ms
twk-promise-polyfill.js
178 ms
twk-main.js
124 ms
twk-vendor.js
92 ms
twk-chunk-vendors.js
107 ms
twk-chunk-common.js
124 ms
twk-runtime.js
185 ms
twk-app.js
138 ms
bloom.com.my accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
bloom.com.my 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
bloom.com.my SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Bloom.com.my 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 Bloom.com.my 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.
bloom.com.my
Open Graph description is not detected on the main page of Bloom. 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: