19.8 sec in total
2.8 sec
16.2 sec
876 ms
Welcome to iflower.hk homepage info - get ready to check Iflower best content for Hong Kong right away, or after learning these important things about iflower.hk
愛花兒茗禮網--HK$688一束鮮花,訂購852-21171188(20條線)花店,網上花店,網上花店訂花,花花世界網上花店,香港網上花店,九龍網上花店,新界網上花店,港島網上花店,香港花店,九龍花店,新界花店,港島花店,中環花店
Visit iflower.hkWe analyzed Iflower.hk page load time and found that the first response time was 2.8 sec and then it took 17.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. This domain responded with an error, which can significantly jeopardize Iflower.hk rating and web reputation
iflower.hk performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value22.7 s
0/100
25%
Value32.5 s
0/100
10%
Value1,710 ms
11/100
30%
Value0.354
31/100
15%
Value24.8 s
0/100
10%
2751 ms
1479 ms
788 ms
1098 ms
769 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 93% of them (116 requests) were addressed to the original Iflower.hk, 3% (4 requests) were made to Pagead2.googlesyndication.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (10 sec) belongs to the original domain Iflower.hk.
Page size can be reduced by 301.8 kB (7%)
4.4 MB
4.1 MB
In fact, the total size of Iflower.hk main page is 4.4 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. 40% of websites need less resources to load. Images take 4.2 MB which makes up the majority of the site volume.
Potential reduce by 144.8 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. This page needs HTML code to be minified as it can gain 47.6 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 144.8 kB or 92% of the original size.
Potential reduce by 112.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. Iflower images are well optimized though.
Potential reduce by 31.6 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 31.6 kB or 37% of the original size.
Potential reduce by 12.4 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. Iflower.hk needs all CSS files to be minified and compressed as it can save up to 12.4 kB or 85% of the original size.
Number of requests can be reduced by 18 (15%)
123
105
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iflower. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
iflower.hk
2751 ms
css.css
1479 ms
mycalendar.css
788 ms
flash.js
1098 ms
resizeImage.js
769 ms
global.js
1355 ms
Modal.js
2135 ms
show_ads.js
6 ms
left-panel-order-phone.gif
630 ms
left-panel-order-monitor.gif
630 ms
payment-options.gif
1269 ms
jiange.gif
335 ms
line1.jpg
335 ms
201222818160370.jpg
1267 ms
2012224172036311.jpg
657 ms
2011123014552404.jpg
641 ms
20111230141316990.jpg
948 ms
2011123015116872.jpg
782 ms
2012511194914968.jpg
1526 ms
2011123014531797.jpg
971 ms
20111230141025482.jpg
953 ms
2011123015226831.jpg
1076 ms
20111230141540780.jpg
1250 ms
20111230144820298.jpg
1257 ms
2012228183810140.jpg
1285 ms
20111230145514860.jpg
1376 ms
2009112414234314.jpg
1560 ms
leftkuang01.jpg
1548 ms
lefttitle01.jpg
1671 ms
line3.jpg
1589 ms
logo-whatsapp.png
1679 ms
leftkuang03.jpg
1816 ms
lefttitle02.jpg
1855 ms
lefttitle03.jpg
1857 ms
header-valentines-zh.gif
1918 ms
2012518182325565.jpg
2486 ms
201222418566781.jpg
2000 ms
2012224173043194.jpg
2230 ms
2012515192133224.jpg
2525 ms
2012223175058783.jpg
2556 ms
2012223174125794.jpg
2560 ms
2012131113356427.jpg
2326 ms
2012131113043257.jpg
2548 ms
2012131112410895.jpg
2630 ms
2012131111738411.jpg
3341 ms
201213112174863.jpg
2517 ms
20111222151214196.jpg
2547 ms
counter.js
8 ms
2011316121620979.jpg
2725 ms
20113151808972.jpg
2623 ms
Common.css
2320 ms
20111222161754684.jpg
2512 ms
2011122218212427.jpg
2425 ms
201112221832669.jpg
2355 ms
2009619193858322.jpg
2564 ms
2009625154334500.jpg
2585 ms
2009619201115541.jpg
2753 ms
header-recommended-zh.gif
2357 ms
ico_new.gif
2352 ms
20111222151639470.jpg
2509 ms
200961918489952.jpg
2542 ms
2011127121953314.jpg
2490 ms
200911520150668.jpg
2416 ms
2015112318918882.jpg
2618 ms
201222419516851.jpg
2667 ms
2015211135924664.jpg
2538 ms
2015112318621731.jpg
2488 ms
20111223182918539.jpg
2527 ms
20111223182725253.jpg
2454 ms
200962511525763.jpg
2577 ms
2011122318536795.jpg
3993 ms
2012224185455951.jpg
2611 ms
2009120105134240.jpg
2582 ms
2015211142759572.jpg
3100 ms
2011122216384235.jpg
2892 ms
2012224185056623.jpg
2421 ms
2011316121052480.jpg
2560 ms
200961919269967.jpg
2595 ms
201222415557365.jpg
2900 ms
2014714145713334.jpg
3448 ms
20111222151345271.jpg
2946 ms
2009615114420709.jpg
2854 ms
2014714145612318.jpg
3449 ms
20111223174524370.jpg
3334 ms
ca-pub-3296342756493731.js
177 ms
zrt_lookup.html
175 ms
show_ads_impl.js
120 ms
osd.js
8 ms
2014714145340861.jpg
3212 ms
t.php
56 ms
ga.js
10 ms
__utm.gif
13 ms
20111222141554256.jpg
2985 ms
20111222141841675.jpg
3031 ms
header-floral-zh.gif
3057 ms
200961515287799.jpg
3754 ms
2009615152852653.gif
3436 ms
2009114202332374.jpg
3314 ms
2009114202413280.jpg
3314 ms
2009114202453242.jpg
3374 ms
20096251149618.jpg
3317 ms
201222417409411.jpg
3596 ms
2009625111510813.jpg
3601 ms
2009116163326601.gif
3647 ms
2009619181111181.jpg
10048 ms
2009116164032844.jpg
3638 ms
link-more-floral-stand-zh.gif
3406 ms
link-more-floral-decor-zh.gif
3608 ms
link-more-floral-orchid-zh.gif
3631 ms
header-2009midautumn-zh.jpg
3617 ms
201482917059263.jpg
4828 ms
201482917334264.jpg
7825 ms
20148291752949.jpg
5950 ms
201482917846543.jpg
4239 ms
201482917124329.jpg
6071 ms
2014829171522207.jpg
5777 ms
2014829171747876.jpg
6420 ms
2014829165156751.jpg
7064 ms
homecontentbg.jpg
6163 ms
line2.jpg
6055 ms
leftkuang02.jpg
6257 ms
cross.gif
6139 ms
cross.gif
6411 ms
h2.gif
6490 ms
bottombg.jpg
6455 ms
iflower.hk 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
iflower.hk 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
iflower.hk 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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iflower.hk can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Iflower.hk 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.
iflower.hk
Open Graph description is not detected on the main page of Iflower. 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: