10.6 sec in total
996 ms
9.3 sec
281 ms
Visit floresce.com now to see the best up-to-date Floresce content for Brazil and also check out these interesting facts you probably never knew about floresce.com
Arranjos e Buquês de Flores, Cestas de Café da Manhã e Presentes. Entregas em todo Brasil. Aproveite as Ofertas e Frete GRÁTIS p/ MG. Compre, agora!
Visit floresce.comWe analyzed Floresce.com page load time and found that the first response time was 996 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
floresce.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value4.9 s
28/100
25%
Value12.2 s
3/100
10%
Value6,450 ms
0/100
30%
Value0.033
100/100
15%
Value18.3 s
3/100
10%
996 ms
267 ms
539 ms
400 ms
289 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 81% of them (35 requests) were addressed to the original Floresce.com, 12% (5 requests) were made to Floresce.lojablindada.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.3 sec) relates to the external source Floresce.lojablindada.com.
Page size can be reduced by 404.0 kB (50%)
815.5 kB
411.6 kB
In fact, the total size of Floresce.com main page is 815.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 364.2 kB which makes up the majority of the site volume.
Potential reduce by 39.4 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 6.2 kB, which is 13% 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 39.4 kB or 81% of the original size.
Potential reduce by 15.1 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. Floresce images are well optimized though.
Potential reduce by 286.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 286.4 kB or 79% of the original size.
Potential reduce by 63.0 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. Floresce.com needs all CSS files to be minified and compressed as it can save up to 63.0 kB or 84% of the original size.
Number of requests can be reduced by 20 (48%)
42
22
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Floresce. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.floresce.com
996 ms
reset.css
267 ms
boxes.css
539 ms
menu.css
400 ms
clears.css
289 ms
fix.css
287 ms
103abe1449a244426c56079ea853d591.js
1749 ms
glider.js
401 ms
getSelo.js
410 ms
frete-gratis-rj-banner-lateral-4.jpg
6002 ms
aplicativo-20.jpg
6008 ms
em-branco-2.jpg
5882 ms
rosas-natura-11.jpg
6194 ms
buque-exuberante-de-rosas-2.jpg
6293 ms
fundo_geral.gif
139 ms
logo.png
269 ms
btn_go.gif
139 ms
mes-da-mulher-2016-lirio.jpg
568 ms
flower-shop-gerbera.jpg
669 ms
orquideas-ofertas-2016.jpg
550 ms
dia-da-mulher-2016-flores-3.jpg
716 ms
faixa-parcelamento.jpg
553 ms
rosas_red.jpg
543 ms
buque_astromelias.jpg
819 ms
cesta_bom_dia.jpg
988 ms
cesta_da_tarde.jpg
822 ms
buque_explendido_de_rosas_vermelhas.jpg
699 ms
flores_simpaticas.jpg
1066 ms
ga.js
17 ms
fundo_barra_menu.png
817 ms
links_separator.gif
836 ms
fundo_barra_categoria.png
938 ms
nav_top_level_arrow.gif
944 ms
nav_parent_arrow.gif
950 ms
fundo_busca.png
971 ms
head_search.gif
1091 ms
__utm.gif
14 ms
aprev.gif
1049 ms
astop.gif
1051 ms
aplay.gif
1076 ms
anext.gif
1075 ms
btn_add_to_cart.gif
1149 ms
print.css
138 ms
floresce.com 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
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
floresce.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
floresce.com 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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floresce.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Floresce.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.
floresce.com
Open Graph description is not detected on the main page of Floresce. 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: