3.6 sec in total
416 ms
2.3 sec
824 ms
Click here to check amazing FruitN Flora content for Thailand. Otherwise, check out these important facts you probably never knew about fruitnflora.com
ส่งมอบความรู้สึกดี ๆ แทนความห่วงใยให้กับคนพิเศษของคุณ ด้วยบริการจัดส่งดอกไม้สวย ๆ และผลไม้คุณภาพดี จากร้านดอกไม้ Fruit N Flora จัดส่งฟรีทั่วกรุงเทพ
Visit fruitnflora.comWe analyzed Fruitnflora.com page load time and found that the first response time was 416 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
fruitnflora.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value12.1 s
0/100
25%
Value10.9 s
7/100
10%
Value1,910 ms
9/100
30%
Value0.334
34/100
15%
Value15.5 s
7/100
10%
416 ms
61 ms
56 ms
65 ms
61 ms
Our browser made a total of 187 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Fruitnflora.com, 63% (117 requests) were made to Cdn6.bigcommerce.com and 24% (45 requests) were made to Cdn5.bigcommerce.com. The less responsive or slowest element that took the longest time to load (563 ms) relates to the external source Cdn5.bigcommerce.com.
Page size can be reduced by 748.7 kB (10%)
7.8 MB
7.0 MB
In fact, the total size of Fruitnflora.com main page is 7.8 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. 85% 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. Images take 7.0 MB which makes up the majority of the site volume.
Potential reduce by 151.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 33.8 kB, which is 20% 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 151.8 kB or 88% of the original size.
Potential reduce by 177.3 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. FruitN Flora images are well optimized though.
Potential reduce by 351.5 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 351.5 kB or 71% of the original size.
Potential reduce by 68.2 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. Fruitnflora.com needs all CSS files to be minified and compressed as it can save up to 68.2 kB or 80% of the original size.
Number of requests can be reduced by 72 (41%)
174
102
The browser has sent 174 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FruitN Flora. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
www.fruitnflora.com
416 ms
font-awesome.min.css
61 ms
jquery.idealforms.css
56 ms
font-awesome.min.css
65 ms
uniform.default.css
61 ms
css
92 ms
css
137 ms
css
138 ms
styles.css
52 ms
iselector.css
70 ms
flexslider.css
68 ms
slide-show.css
70 ms
styles-slide-show.css
89 ms
social.css
83 ms
styles.css
87 ms
responsive.css
99 ms
white.css
82 ms
hipster.css
106 ms
theme.css
127 ms
custom.css
124 ms
imodal.css
114 ms
product.attributes.css
113 ms
ui.all.css
114 ms
product.quickview.css
140 ms
jquery.min.js
116 ms
jquery.min.js
191 ms
menudrop.js
93 ms
jquery.masonry.js
77 ms
common.js
76 ms
iselector.js
105 ms
viewport.js
105 ms
jquery.uniform.min.js
121 ms
modernizr.js
117 ms
jquery.autobox.js
120 ms
init.js
118 ms
imagesLoaded.js
124 ms
quickview.js
125 ms
main.js
134 ms
imodal.js
134 ms
jquery-ui.min.js
202 ms
jquery.validate.js
128 ms
product.functions.js
128 ms
product.attributes.js
125 ms
quickview.js
125 ms
quickview.initialise.js
127 ms
quicksearch.js
122 ms
demo.css
158 ms
style2.css
145 ms
modernizr.custom.28468.js
143 ms
css
116 ms
jquery.cslider.js
140 ms
visitor.js
123 ms
copyenrich.js
320 ms
copyenrich-filter.js
312 ms
jquery.flexslider.js
149 ms
flexslider.css
149 ms
jquery.idealforms.js
148 ms
css
29 ms
analytics.min.js
54 ms
bg-body-2.jpg
256 ms
thaisansneue-regular-webfont.woff
34 ms
beacon_api.js
29 ms
fbds.js
27 ms
analytics.js
63 ms
ajax-loader.gif
53 ms
logo_1435551142__78932.png
112 ms
FNF_PROMOTION_ICON.gif
276 ms
phone.png
108 ms
contact.png
109 ms
cart.png
108 ms
search-icon.png
111 ms
banner-home1.jpg
445 ms
Banner_3.jpg
445 ms
Banner_4.jpg
446 ms
logonewfnf.png
106 ms
capture-fnf2-03.png
272 ms
_6108434_orig__96377.1423050984.356.300.png
271 ms
_6665130_orig__34902.1423051845.356.300.png
215 ms
_2916773_orig__00006.1423051993.356.300.png
263 ms
_7235886_orig__74325.1422962058.356.300.png
262 ms
_6779942_orig__65796.1422961771.356.300.png
269 ms
_7916738_orig__50068.1422960340.356.300.png
423 ms
_2786672_orig__87334.1422958913.356.300.png
424 ms
_8288056_orig__35288.1422958405.356.300.png
426 ms
_1532538_orig__16144.1422958007.356.300.png
427 ms
_2164159_orig__68451.1422956877.356.300.png
424 ms
capture-fnf2-06.png
266 ms
_7837988_orig__04399.1423050242.356.300.png
420 ms
_3302648_orig__07525.1423050636.356.300.png
430 ms
_9430467_orig__42851.1423051154.356.300.png
442 ms
_7395830_orig__03562.1423051190.356.300.png
431 ms
_6051893_orig__35615.1423051554.356.300.png
430 ms
_5512096_orig__59226.1423051955.356.300.png
434 ms
_9964096_orig__69712.1423052261.356.300.png
428 ms
_8141014_orig__98527.1423052443.356.300.png
431 ms
capture-fnf2-09.png
418 ms
_5771534_orig__63634.1422963309.356.300.png
525 ms
_9649620_orig__84022.1422962247.356.300.png
432 ms
_9553049_orig__69104.1422961950.356.300.png
441 ms
_4485470_orig__21265.1422961657.356.300.png
438 ms
fornax.min.js
175 ms
234 ms
377 ms
collect
172 ms
_4206733_orig__03764.1422960385.356.300.png
425 ms
_7062729_orig__51805.1422960297.356.300.png
426 ms
_2923014_orig__93419.1422960199.356.300.png
422 ms
capture-fnf2-11.png
319 ms
_8469426_orig__64217.1422959803.356.300.png
444 ms
_6446672_orig__40804.1422959433.356.300.png
419 ms
BebasNeue-webfont.woff
291 ms
_5785185_orig__45788.1422958964.356.300.png
331 ms
_2203940_orig__12010.1422958844.356.300.png
314 ms
_8709585_orig__55887.1422957826.356.300.png
322 ms
collect
271 ms
_8061580_orig__70461.1422957739.356.300.png
287 ms
capture-fnf2-17.png
161 ms
_187812_orig__66616.1422957437.356.300.png
307 ms
_8508226_orig__99837.1422957391.356.300.png
295 ms
_8286269_orig__11966.1422957349.356.300.png
318 ms
_2037961_orig__20371.1422957265.356.300.png
314 ms
gtm.js
130 ms
social-icon-font.woff
70 ms
fontawesome-webfont.woff
154 ms
fontawesome-webfont.woff
153 ms
_8320709_orig__86144.1422956783.356.300.png
243 ms
_4415754_orig__75923.1422956658.356.300.png
170 ms
_3261659_orig__97224.1422953505.356.300.png
166 ms
_8929611_orig__31047.1422951878.356.300.png
279 ms
capture-fnf2-20.png
107 ms
10.jpg
106 ms
3.jpg
156 ms
25.jpg
121 ms
21.jpg
100 ms
19.jpg
131 ms
14.jpg
138 ms
13.jpg
118 ms
1-1.jpg
149 ms
6.jpg
123 ms
4.jpg
151 ms
2.jpg
136 ms
22.jpg
141 ms
5.jpg
140 ms
7.jpg
136 ms
8.jpg
146 ms
9.jpg
224 ms
11.jpg
143 ms
12.jpg
141 ms
15.jpg
141 ms
17.jpg
158 ms
18.jpg
156 ms
20.jpg
156 ms
24.jpg
153 ms
ga-audiences
168 ms
23..jpg
152 ms
i1.png
145 ms
i2.png
153 ms
i3.png
151 ms
i4.png
147 ms
icon-fnf1.png
147 ms
icon-fnf2.png
142 ms
icon-fnf3.png
139 ms
icon-fnf4.png
265 ms
icon-banner1.png
255 ms
icon-banner2.png
255 ms
icon-banner3.png
255 ms
banner-wre-for-fnf2.jpg
255 ms
arrows.png
108 ms
hero_prev.gif
108 ms
hero_next.gif
110 ms
icon-contact.png
246 ms
capture-fnf2-14.png
249 ms
pre.png
251 ms
next.png
249 ms
icon-contact-black.png
248 ms
BebasNeue-webfont.ttf
563 ms
widget_v2.134.js
27 ms
conversion_async.js
27 ms
fontawesome-webfont.ttf
157 ms
350 ms
fontawesome-webfont.svg
291 ms
blue-up-arrow.png
91 ms
index.php
132 ms
sub-nav-arrow.png
70 ms
68 ms
BebasNeue-webfont.svg
190 ms
8 ms
fruitnflora.com 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.
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
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.
fruitnflora.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Uses deprecated APIs
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
fruitnflora.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
TH
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fruitnflora.com can be misinterpreted by Google and other search engines. Our service has detected that Thai is used on the page, and it does not match the claimed English language. Our system also found out that Fruitnflora.com 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.
fruitnflora.com
Open Graph description is not detected on the main page of FruitN Flora. 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: