4.5 sec in total
104 ms
1.8 sec
2.6 sec
Welcome to flor360.com homepage info - get ready to check Flor360 best content right away, or after learning these important things about flor360.com
Visit flor360.comWe analyzed Flor360.com page load time and found that the first response time was 104 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
flor360.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value7.8 s
3/100
25%
Value4.4 s
75/100
10%
Value190 ms
91/100
30%
Value0.001
100/100
15%
Value7.6 s
46/100
10%
104 ms
195 ms
35 ms
71 ms
102 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 86% of them (114 requests) were addressed to the original Flor360.com, 11% (14 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (935 ms) belongs to the original domain Flor360.com.
Page size can be reduced by 369.2 kB (1%)
25.1 MB
24.7 MB
In fact, the total size of Flor360.com main page is 25.1 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. Images take 24.3 MB which makes up the majority of the site volume.
Potential reduce by 173.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 173.1 kB or 84% of the original size.
Potential reduce by 78.4 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. Flor360 images are well optimized though.
Potential reduce by 59.2 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 59.2 kB or 17% of the original size.
Potential reduce by 58.5 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. Flor360.com needs all CSS files to be minified and compressed as it can save up to 58.5 kB or 25% of the original size.
Number of requests can be reduced by 95 (84%)
113
18
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flor360. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 51 to 1 for CSS and as a result speed up the page load time.
flor360.com
104 ms
flor360.com
195 ms
style-index.css
35 ms
jquery-ui.css
71 ms
datepicker.css
102 ms
woo-shipping-display-mode-public.css
103 ms
font-awesome.min.css
105 ms
style.css
108 ms
style.css
110 ms
theme.css
139 ms
select.css
135 ms
main.css
135 ms
wysiwyg.css
136 ms
switcher.css
142 ms
blog-layouts-module.css
174 ms
woo-module.css
204 ms
css
44 ms
jet-cw.css
169 ms
jet-cw-frontend-font.css
172 ms
css
81 ms
all.min.css
179 ms
v4-shims.min.css
182 ms
public.css
207 ms
jet-menu-general.css
206 ms
style.css
210 ms
mediaelementplayer-legacy.min.css
210 ms
photoswipe.min.css
212 ms
default-skin.min.css
236 ms
jet-woo-product-gallery.css
237 ms
custom-jet-blocks.css
238 ms
jet-elements.css
280 ms
jet-elements-skin.css
246 ms
elementor-icons.min.css
248 ms
frontend-lite.min.css
269 ms
swiper.min.css
277 ms
post-9378.css
278 ms
jet-tabs-frontend.css
295 ms
jet-tricks-frontend.css
297 ms
post-334.css
303 ms
css
45 ms
w.js
23 ms
post-2615.css
303 ms
post-614.css
283 ms
chosen.min.css
220 ms
jet-search.css
223 ms
fontawesome.min.css
241 ms
regular.min.css
241 ms
solid.min.css
242 ms
widget-icon-box.min.css
224 ms
widget-icon-list.min.css
223 ms
wc-blocks.css
222 ms
frontend.css
241 ms
jetwoobuilder-frontend-font.css
241 ms
public.css
209 ms
wp-polyfill-inert.min.js
212 ms
regenerator-runtime.min.js
207 ms
wp-polyfill.min.js
206 ms
hooks.min.js
231 ms
jquery.min.js
211 ms
jquery-migrate.min.js
218 ms
imagesloaded.min.js
221 ms
core.min.js
221 ms
select2.min.js
222 ms
datepicker.min.js
236 ms
jquery.ui.datepicker-es.js
217 ms
orddd-lite-initialize-datepicker.js
216 ms
woo-shipping-display-mode-public.js
213 ms
js.cookie.min.js
332 ms
cart-fragments.min.js
328 ms
jquery.blockUI.min.js
304 ms
add-to-cart.min.js
300 ms
woocommerce.min.js
287 ms
underscore.min.js
287 ms
wp-util.min.js
283 ms
chosen.jquery.min.js
284 ms
jet-plugins.js
277 ms
jet-search.js
274 ms
accessibility.js
273 ms
sourcebuster.min.js
274 ms
order-attribution.min.js
272 ms
woo-module-script.js
361 ms
theme-script.js
340 ms
vue.min.js
333 ms
jet-menu-public-scripts.js
330 ms
jquery.jsticky.min.js
331 ms
webpack.runtime.min.js
330 ms
frontend-modules.min.js
331 ms
waypoints.min.js
310 ms
frontend.min.js
309 ms
jet-blocks.min.js
309 ms
jet-cw.min.js
306 ms
jet-elements.min.js
305 ms
widgets-scripts.js
303 ms
g.gif
19 ms
jet-tabs-frontend.min.js
275 ms
popperjs.js
263 ms
tippy-bundle.js
262 ms
jet-tricks-frontend.js
261 ms
frontend.min.js
301 ms
public.js
302 ms
Logo-Flor360.png
235 ms
Banner-Home.jpg
333 ms
IMG_4940.jpeg
427 ms
IMG_4949.png
935 ms
IMG_4944.jpeg
828 ms
IMG_4687.jpeg
536 ms
IMG_4937-scaled.jpeg
343 ms
IMG_4685-scaled.jpeg
373 ms
IMG_4684.jpeg
772 ms
IMG_4688.jpeg
471 ms
A12-Principal.jpg
437 ms
A4-Principal.jpg
753 ms
A5-Principal.jpg
571 ms
A3-Principal.jpg
731 ms
Gerberas_Rosas_y_Alstroemerias1.jpg
606 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aevHg.ttf
97 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexaFR8aevHg.ttf
122 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexc1R8aevHg.ttf
124 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexRNR8aevHg.ttf
124 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexU1W8aevHg.ttf
124 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexXRW8aevHg.ttf
122 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexRNW8aevHg.ttf
124 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexTpW8aevHg.ttf
125 ms
fa-solid-900.woff
590 ms
fa-solid-900.woff
627 ms
fa-regular-400.woff
687 ms
fa-regular-400.woff
688 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
125 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
125 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
127 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
127 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFn8kEk30e0.ttf
127 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFkQl0k30e0.ttf
128 ms
flor360.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
button, link, and menuitem elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
flor360.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
flor360.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flor360.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Flor360.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.
flor360.com
Open Graph description is not detected on the main page of Flor360. 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: