8.8 sec in total
2.1 sec
6.3 sec
422 ms
Visit floresyfresas.com now to see the best up-to-date Flores Y Fresas content and also check out these interesting facts you probably never knew about floresyfresas.com
Visit floresyfresas.comWe analyzed Floresyfresas.com page load time and found that the first response time was 2.1 sec and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
floresyfresas.com performance score
name
value
score
weighting
Value9.3 s
0/100
10%
Value18.2 s
0/100
25%
Value20.4 s
0/100
10%
Value840 ms
34/100
30%
Value0.079
94/100
15%
Value19.2 s
2/100
10%
2062 ms
163 ms
228 ms
258 ms
261 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 77% of them (69 requests) were addressed to the original Floresyfresas.com, 9% (8 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Floresyfresas.com.
Page size can be reduced by 3.1 MB (50%)
6.2 MB
3.1 MB
In fact, the total size of Floresyfresas.com main page is 6.2 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 2.6 MB which makes up the majority of the site volume.
Potential reduce by 62.7 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 62.7 kB or 79% of the original size.
Potential reduce by 105.7 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. Flores Y Fresas images are well optimized though.
Potential reduce by 832.4 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 832.4 kB or 72% of the original size.
Potential reduce by 2.1 MB
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. Floresyfresas.com needs all CSS files to be minified and compressed as it can save up to 2.1 MB or 87% of the original size.
Number of requests can be reduced by 44 (56%)
78
34
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flores Y Fresas. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
www.floresyfresas.com
2062 ms
wp-emoji-release.min.js
163 ms
foobox.min.css
228 ms
form.css
258 ms
common-elements.css
261 ms
settings.css
232 ms
style.php
1534 ms
styles.css
283 ms
easy-social-share-buttons.css
595 ms
essb-sidebar.css
321 ms
jquery.selectBox.css
328 ms
style.css
344 ms
font-awesome.min.css
395 ms
foundation.min.css
459 ms
font-awesome.min.css
7 ms
app.css
558 ms
selection.php
1731 ms
magnific-popup.css
462 ms
style.css
529 ms
js_composer_front_custom.css
1041 ms
Defaults.css
600 ms
css
58 ms
ultimate.min.css
780 ms
jquery.js
736 ms
jquery-migrate.min.js
663 ms
jquery.themepunch.tools.min.js
852 ms
jquery.themepunch.revolution.min.js
809 ms
add-to-cart.min.js
832 ms
woocommerce-add-to-cart.js
864 ms
modernizr.custom.min.js
867 ms
foobox.min.js
1052 ms
ultimate.min.js
1082 ms
estilos.css
924 ms
dashicons.min.css
715 ms
thickbox.css
767 ms
jquery.selectBox.min.js
797 ms
jquery.yith-wcwl.js
800 ms
vendor.min.js
856 ms
app.min.js
861 ms
thickbox.js
871 ms
js_composer_front.min.js
863 ms
css
23 ms
Logotipo-bk1.png
500 ms
dummy.png
303 ms
u7jan6Gt0WM
332 ms
xgzbb53t8j-Mo-vYa23n5tqQynqKV_9Plp7mupa0S4g.ttf
328 ms
xgzbb53t8j-Mo-vYa23n5tqQynqKV_9Plp7mupa0S4g.ttf
286 ms
C6HYlRF50SGJq1XyXj04z01QiopyrnwRtPsQZ8jWT9Y.ttf
326 ms
C6HYlRF50SGJq1XyXj04z-VEV9pFKH0Jlg6jxEKhoIU.ttf
327 ms
C6HYlRF50SGJq1XyXj04z6p5NA6AAOjfQM_HmvD0shQ.ttf
328 ms
C6HYlRF50SGJq1XyXj04z6p5NA6AAOjfQM_HmvD0shQ.ttf
327 ms
fontawesome-webfont.woff
57 ms
fontawesome-webfont.woff
356 ms
separator.png
325 ms
nuevos-disenos.jpg
327 ms
Rosas.jpg
761 ms
CANASTA-ROSAS-FRUTA-Y-VINO-1160-A.jpg
807 ms
CORONA-CONCADOR.jpg
576 ms
b-exclusivos.jpg
445 ms
image5-c.jpg
557 ms
Fresas02.jpg
527 ms
Blog.jpg
615 ms
preguntas-frecuentes-flores-y-fresas.jpg
584 ms
pagos-flores.png
637 ms
sdk.js
414 ms
revolution.extension.slideanims.min.js
402 ms
revolution.extension.navigation.min.js
391 ms
revolution.extension.parallax.min.js
434 ms
foobox.svg
384 ms
foobox.woff
452 ms
www-embed-player-vflfNyN_r.css
60 ms
www-embed-player.js
81 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
58 ms
ad_status.js
57 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
28 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
39 ms
123 ms
xd_arbiter.php
148 ms
xd_arbiter.php
297 ms
Entrada-slider02.jpg
269 ms
home-flores-y-fresas.jpg
236 ms
Entrada-slider03_1..jpg
303 ms
arrow-left.svg
55 ms
arrow-left.cur
65 ms
arrow-right.svg
114 ms
arrow-right.cur
109 ms
arrow-left-dark.svg
67 ms
arrow-left-dark.cur
55 ms
arrow-right-dark.svg
64 ms
arrow-right-dark.cur
109 ms
floresyfresas.com accessibility score
floresyfresas.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
floresyfresas.com SEO score
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floresyfresas.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 Floresyfresas.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.
floresyfresas.com
Open Graph description is not detected on the main page of Flores Y Fresas. 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: