5.6 sec in total
234 ms
4.9 sec
433 ms
Visit flora.com now to see the best up-to-date Flora content for United Kingdom and also check out these interesting facts you probably never knew about flora.com
Flora helps keep your family happy and healthy with a delicious daily boost of plant goodness. Find simple snacks, baking and meal recipes made with Flora.
Visit flora.comWe analyzed Flora.com page load time and found that the first response time was 234 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
flora.com performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value13.7 s
0/100
25%
Value9.6 s
11/100
10%
Value2,960 ms
3/100
30%
Value0.14
79/100
15%
Value16.2 s
6/100
10%
234 ms
412 ms
21 ms
32 ms
196 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 31% of them (36 requests) were addressed to the original Flora.com, 9% (11 requests) were made to and 7% (8 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source S3-eu-west-1.amazonaws.com.
Page size can be reduced by 1.9 MB (31%)
6.3 MB
4.4 MB
In fact, the total size of Flora.com main page is 6.3 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. 80% 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 3.5 MB which makes up the majority of the site volume.
Potential reduce by 205.9 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 205.9 kB or 79% of the original size.
Potential reduce by 55.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. Flora images are well optimized though.
Potential reduce by 1.5 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.5 MB or 65% of the original size.
Potential reduce by 208.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. Flora.com needs all CSS files to be minified and compressed as it can save up to 208.4 kB or 84% of the original size.
Number of requests can be reduced by 59 (59%)
100
41
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 34 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
flora.com
234 ms
www.flora.com
412 ms
bootstrap.min.css
21 ms
core.min.css
32 ms
libs.css
196 ms
brand.css
25 ms
u.js
171 ms
vlr4squ.js
278 ms
Cookie-Popup.js
53 ms
jquery.validate.js
72 ms
libs.js
456 ms
settings.js
33 ms
core.min.js
47 ms
addthis_widget.js
48 ms
share.js
41 ms
bas.js
196 ms
print.css
5 ms
satelliteLib-7a8e653f7a928ff69428b700279a52fa312e4c54.js
7 ms
satellite-54f800293631350019b10000.js
7 ms
satellite-53b2458946a1a8d0590000b3.js
55 ms
sp.js
56 ms
linkid.js
48 ms
ecommerce.js
49 ms
__utm.gif
35 ms
__utm.gif
36 ms
d
258 ms
eventgroupmap.js
40 ms
collect
22 ms
collect
4 ms
collect
5 ms
collect
5 ms
collect
6 ms
collect
10 ms
collect
19 ms
collect
19 ms
cc.js
656 ms
logo.png
27 ms
03b04341-d380-4545-9585-b30ad8abe842.jpg
2050 ms
facebook-icon.png
24 ms
twitter-icon.png
24 ms
youtube-icon.png
25 ms
pinterest-icon.png
27 ms
3473-1102806-Hero_Banner_Mobile.jpg
25 ms
3473-1106976-Home-Teasers-Recipes-Desk_Mobile.jpg
53 ms
3473-1106978-Home-Teaser-Health-Desk_Mobile.jpg
61 ms
3473-1132096-Floraproactiv_Florasaurus_Spotlight_Image_Grass_360x360_Mobile.jpg
51 ms
3473-1133909-Flora_Spotlight_Range_360x360_Mobile.jpg
51 ms
3473-1106977-Home-Teasers-HFF-Desk_Mobile.jpg
60 ms
3473-1107054-logo.png
49 ms
66565e42-8ee2-4b00-a5dd-c445450b3cc1.jpg
2046 ms
43d4438a-79e6-4b76-ba1a-cabdf0872e96.jpg
1433 ms
365657f0-9a52-4e7e-a64d-d5e0247e22ce.jpg
2045 ms
15e3bd62-efc2-449b-9b9f-6f7455c72671.jpg
2045 ms
icn-sprite.png
182 ms
nav_circle.png
40 ms
footer_flower_bg.gif
184 ms
hp_side_flower.png
183 ms
hp_teaser_cta.png
178 ms
hp_magnify_icon.png
182 ms
sic_left_nav.png
178 ms
nl_cta_icon.png
179 ms
nl_msg_icon.png
181 ms
jquery.min.js
15 ms
qAA==
8 ms
6gA=
8 ms
19GCcvNtMLUSlaxmjWspZR1lBFkPRvYyCY2s4WtbGM7O9hJObvYzR72ss+k6AAHOcRhKqjkCEc5xnGqqOYEJ6mhllOc5gx1nOUc57nARS5xmStc5RrXucHNRK7umCyGTLruE+YBD4nwiCiPeUI9T3nGc2K84CWveM0bGmjkLe9+ALWQf+oA
6 ms
6gA=
19 ms
constantco-flora-smartproducts.js
902 ms
satellite-559b864730633400170001c0.html
239 ms
widgets.js
194 ms
pinit.js
252 ms
sdk.js
293 ms
www.flora.com
763 ms
boost
183 ms
300lo.json
178 ms
3473-1102806-Hero_Banner.jpg
179 ms
3473-1106976-Home-Teasers-Recipes-Desk.jpg
179 ms
3473-1106978-Home-Teaser-Health-Desk.jpg
184 ms
3473-1132096-Floraproactiv_Florasaurus_Spotlight_Image_Grass_360x360.jpg
185 ms
3473-1133909-Flora_Spotlight_Range_360x360.jpg
718 ms
3473-1106977-Home-Teasers-HFF-Desk.jpg
249 ms
uf9MgO3+nQGbXTMp+Asjsz0PAAA=
44 ms
mqI=
42 ms
or11FuqKn4QAAAA=
40 ms
Pzkr5VLw1p+AYZ+IAA==
39 ms
z85K+VS8NafgGGfiAA=
38 ms
AVe84eAAAA==
36 ms
fIzN+ARbsBXbsB2fYgd2YhcK8Bk+x258gT3Yi33Yj0IcwJc4iEM4jCIUo6SxcRobp7FxGhvnv944fwAL825e
29 ms
sh.07f0d9bf220d07a763adad1e.html
113 ms
p.gif
610 ms
up_loader.1.1.0.js
133 ms
layers.173914a8ea2767730b7b.js
18 ms
up
500 ms
pinit_main.js
467 ms
cqx
971 ms
cqd
160 ms
56 ms
xd_arbiter.php
100 ms
xd_arbiter.php
154 ms
ext.html
335 ms
42 ms
universal_pixel.1.1.1.js
4 ms
pixel
88 ms
tg.js
265 ms
generic
4 ms
match
3 ms
pixel
25 ms
4 ms
tg.js
460 ms
requestContainer.min.css
108 ms
PanelIC.htm
187 ms
jquery-1.7.2.min.js
157 ms
tg.js
859 ms
languageFile.js
88 ms
close.png
30 ms
btnBgLeft.png
53 ms
btnBgRight.png
59 ms
flora.com 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-*] attributes do not match their roles
[role] values are not valid
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
flora.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
flora.com 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
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 Flora.com 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 Flora.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.
flora.com
Open Graph data is detected on the main page of Flora. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: