11.7 sec in total
739 ms
10.4 sec
518 ms
Visit floristkl.com now to see the best up-to-date Florist KL content and also check out these interesting facts you probably never knew about floristkl.com
Shirley Florist is a florist shop located in Jalan Ampang, Kuala Lumpur (KL), Malaysia. Our shop also provides flower online shopping.
Visit floristkl.comWe analyzed Floristkl.com page load time and found that the first response time was 739 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.
floristkl.com performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value11.6 s
0/100
25%
Value12.5 s
3/100
10%
Value590 ms
51/100
30%
Value0.3
39/100
15%
Value9.1 s
33/100
10%
739 ms
1374 ms
65 ms
786 ms
988 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Floristkl.com, 74% (59 requests) were made to Cdn1.npcdn.net and 5% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (7 sec) relates to the external source Cdn1.npcdn.net.
Page size can be reduced by 65.7 kB (2%)
3.5 MB
3.5 MB
In fact, the total size of Floristkl.com main page is 3.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. 55% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 43.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 43.1 kB or 76% of the original size.
Potential reduce by 9.9 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. Florist KL images are well optimized though.
Potential reduce by 6.8 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.
Potential reduce by 5.8 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. Floristkl.com needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 11% of the original size.
Number of requests can be reduced by 38 (54%)
71
33
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Florist KL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
floristkl.com
739 ms
www.floristkl.com
1374 ms
font-awesome.css
65 ms
style.css
786 ms
general_v1.css
988 ms
color_style.css
907 ms
gumby.css
312 ms
sweetalert2.min.css
58 ms
style.css
807 ms
banner.css
822 ms
jquery.min.js
51 ms
jquery-migrate-3.0.0.min.js
47 ms
jquery-ui.css
54 ms
jquery-ui.theme.min.css
322 ms
jquery.fancybox.js
337 ms
jquery.fancybox.css
347 ms
slick.css
357 ms
slick-theme.css
367 ms
slick.min.js
376 ms
jquery.qrcode-0.12.0.min.js
387 ms
validate.min.js
398 ms
janimate.js
407 ms
janimate.css
420 ms
owl.carousel.min.css
428 ms
owl.theme.newpages.css
437 ms
owl.carousel.js
449 ms
jquery.colourbrightness.min.js
457 ms
animate.css
466 ms
sweetalert2.min.js
480 ms
jquery.nivo.slider.js
490 ms
default.css
500 ms
nivo-slider.css
509 ms
jquery-ui.min.js
57 ms
jquery.matchHeight-min.js
518 ms
jquery.dotdotdot.min.js
527 ms
css
28 ms
css
42 ms
css
50 ms
css
14 ms
analytics.js
28 ms
bg.jpg
1411 ms
AM_mc_vs_dc_ae.jpg
74 ms
1471595397top.png
961 ms
1450250787b29e17e1d8011a177f675b0db1b61008.jpg
980 ms
1451132746f495248935f2ca00734f7a4c8bb49d43.jpg
1464 ms
1451120467ffc99b0f89285768bf2783c6c8df4dfa.jpg
1478 ms
1449021868_7d46fde6325be39f06a245530a9c6424_en.jpg
1525 ms
IMG_20170612_204611.png
2632 ms
icon_phone_w.png
1702 ms
icon_mail_w.png
2149 ms
1449020953d1.jpg
2893 ms
fbevents.js
99 ms
xfbml.customerchat.js
176 ms
menu_bg.png
2251 ms
loading.gif
1510 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
235 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
236 ms
QdVUSTchPBm7nuUeVf70viFg.ttf
242 ms
collect
196 ms
arrow_down.png
2203 ms
16498318336f9a8d644cc6a5b4ede53aa30bfef3f5.jpg
3245 ms
164647137692ea74ea8d4b9cf769b06055b4bd93fd.jpg
3645 ms
1649831788d07f502fa8f9a30f4fb52f35043737c4.jpg
4585 ms
16464714501420f9fc459338914f3af04e2113e722.jpg
3883 ms
1646471646ba5d15ee9106f251923b53a27decf2bd.jpg
4785 ms
15980896480a6c0721fe05609a54b8200f487bb3f6.jpg
4755 ms
15894451222d7cfd9914fd9ca81ba4ab5b35383ecf.jpg
4887 ms
16264103615696fef4e8b67345f8b605533b2fa063.jpg
5576 ms
1564045010bf190e2b83d8ff45a3d58909ee8f98fe.jpg
5624 ms
1646471822ce4aeab174369756a5c16cf89839c1f5.jpg
6310 ms
1491971392ddd9761687c11b675ba1094c1f493a1a.jpg
6685 ms
footerbg.gif
5747 ms
success_icon.png
5604 ms
icomoon.ttf
6246 ms
fontawesome-webfont.woff
7029 ms
np_add_cart.php
865 ms
68 ms
js
94 ms
arrows.png
5452 ms
bullets.png
5460 ms
floristkl.com 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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.
floristkl.com 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
Page has valid source maps
floristkl.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floristkl.com 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 Floristkl.com main page’s claimed encoding is gb2312. 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.
floristkl.com
Open Graph data is detected on the main page of Florist KL. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: