10.1 sec in total
1.1 sec
8.5 sec
500 ms
Click here to check amazing Petalbees content for Malaysia. Otherwise, check out these important facts you probably never knew about petalbees.com.my
Petalbees is a florist (Kedai Bunga) located in Ampang, Kuala Lumpur (KL). We accept order online and delivery flowers and gifts to Kuala Lumpur and Klang Valley. Friendly Services, Fast Delivery, Rea...
Visit petalbees.com.myWe analyzed Petalbees.com.my page load time and found that the first response time was 1.1 sec and then it took 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.
petalbees.com.my performance score
name
value
score
weighting
Value10.3 s
0/100
10%
Value21.4 s
0/100
25%
Value16.4 s
0/100
10%
Value2,250 ms
6/100
30%
Value0.002
100/100
15%
Value21.7 s
1/100
10%
1068 ms
1542 ms
1305 ms
753 ms
242 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 54% of them (75 requests) were addressed to the original Petalbees.com.my, 11% (16 requests) were made to Maps.google.com and 7% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Petalbees.com.my.
Page size can be reduced by 1.8 MB (47%)
3.9 MB
2.1 MB
In fact, the total size of Petalbees.com.my main page is 3.9 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 136.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 136.7 kB or 61% of the original size.
Potential reduce by 58.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. Petalbees images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 74% of the original size.
Potential reduce by 303.7 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. Petalbees.com.my needs all CSS files to be minified and compressed as it can save up to 303.7 kB or 86% of the original size.
Number of requests can be reduced by 54 (43%)
125
71
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Petalbees. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
petalbees.com.my
1068 ms
Home
1542 ms
skin.css
1305 ms
Telerik.Web.UI.WebResource.axd
753 ms
WebResource.axd
242 ms
Telerik.Web.UI.WebResource.axd
1569 ms
jquery-1.11.2.min.js
681 ms
jquery-migrate-1.2.1.min.js
548 ms
jquery.scrollTo-1.4.3.1-min.js
537 ms
bootstrap.min.js
6 ms
material.js
802 ms
ripples.js
606 ms
jquery.nanoscroller.js
813 ms
CORE.js
791 ms
jquery-ui.min.js
102 ms
js
846 ms
bootstrap.min.js
985 ms
jquery.easing.1.3.js
1067 ms
epaycommon.js
1047 ms
syndicate.cgi
267 ms
js
29 ms
css
24 ms
bootstrap.css
1091 ms
font-awesome.min.css
775 ms
pavcontentslider.css
904 ms
bootstrap-social.css
1446 ms
Phone.png
335 ms
smartphone.png
461 ms
mail.png
336 ms
dot.png
334 ms
logo.png
532 ms
tag.png
582 ms
dot.png
504 ms
ico_facebook.png
572 ms
valentine%202016.jpg
1779 ms
slide5-873x380.jpg
753 ms
slide6-873x380.jpg
1020 ms
slide4-873x380.jpg
1061 ms
slide7-873x380.jpg
1076 ms
purplerose.png
851 ms
payment.gif
983 ms
amex-logo.jpg
1140 ms
PayPal.jpg
1244 ms
maybank-logo-black.jpg
1283 ms
Public(S).png
1318 ms
hlb_logo.png
1325 ms
cimbbank(S).png
1393 ms
fpx_lg.jpg
1527 ms
HB0204.jpg
1561 ms
WF0043.JPG
1582 ms
GB0237.jpg
1583 ms
FS0090.jpg
1677 ms
CS0019_3.JPG
1848 ms
BK0184.jpg
1814 ms
GB0136.jpg
1889 ms
GB0070.jpg
1857 ms
TA0062.jpg
1946 ms
GB0266.jpg
2113 ms
CD0051.jpg
2094 ms
Get%20well%20soon.jpg
2132 ms
balloon.jpg
2135 ms
For%20Him.jpg
2105 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
33 ms
sdk.js
15 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
32 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
32 ms
52 ms
xd_arbiter.php
22 ms
xd_arbiter.php
45 ms
fontawesome-webfont.woff
2127 ms
fontawesome-webfont.woff
2010 ms
CartList
2300 ms
like_box.php
313 ms
CartListTotal
2423 ms
WebResource.axd
1876 ms
gift.jpg
1910 ms
paypal.png
2036 ms
Top_Banner.png
2050 ms
hDvwL1_H7g-.css
14 ms
udqjbTyb5Ue.css
18 ms
q68gy-v_YMF.js
21 ms
FJmpeSpHpjS.js
37 ms
0wM5s1Khldu.js
36 ms
1bNoFZUdlYZ.js
46 ms
23735_574989625859904_2083932620_n.jpg
53 ms
425517_496698110355723_164552502_n.jpg
14 ms
12187680_491105287736476_6837941187722721831_n.jpg
43 ms
12688346_1220376767991957_1045769904225465020_n.jpg
35 ms
11899832_794130220699497_4861184552844807054_n.jpg
23 ms
734389_10203190232504027_824330935_n.jpg
10 ms
1622720_10152811838513235_2429076020489216403_n.jpg
14 ms
11174831_1464182817231105_4400937673831275397_n.jpg
81 ms
wL6VQj7Ab77.png
6 ms
s7jcwEQH7Sx.png
5 ms
banner_bg.png
2211 ms
I6-MnjEovm5.js
4 ms
pQrUxxo5oQp.js
6 ms
flower2.png
2124 ms
petalbees.com.my
1887 ms
envelope.png
1945 ms
fcenter.png
1878 ms
lovechat.png
2064 ms
powered.png
1989 ms
error404.html
575 ms
Home
524 ms
fontawesome-webfont.ttf
254 ms
error404.html
240 ms
common.js
6 ms
map.js
6 ms
util.js
48 ms
marker.js
47 ms
infowindow.js
45 ms
fontawesome-webfont.svg
245 ms
StaticMapService.GetMapImage
200 ms
onion.js
17 ms
openhand_8_8.cur
50 ms
ViewportInfoService.GetViewportInfo
112 ms
stats.js
39 ms
controls.js
35 ms
css
19 ms
transparent.png
72 ms
mapcnt6.png
36 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
29 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
34 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
33 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
72 ms
google4.png
29 ms
sv5.png
33 ms
spotlight-poi.png
33 ms
tmapctrl.png
38 ms
vt
87 ms
vt
93 ms
vt
100 ms
vt
74 ms
vt
59 ms
vt
62 ms
vt
143 ms
tmapctrl4.png
32 ms
error404.html
240 ms
AuthenticationService.Authenticate
264 ms
petalbees.com.my 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
<input type="image"> elements do not have [alt] text
Links do not have a discernible 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.
petalbees.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
petalbees.com.my 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Petalbees.com.my 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 Petalbees.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.
petalbees.com.my
Open Graph description is not detected on the main page of Petalbees. 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: