2.8 sec in total
209 ms
1.8 sec
788 ms
Welcome to florais.com.br homepage info - get ready to check Florais best content for Brazil right away, or after learning these important things about florais.com.br
Visit florais.com.brWe analyzed Florais.com.br page load time and found that the first response time was 209 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
florais.com.br performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value10.4 s
0/100
25%
Value7.5 s
27/100
10%
Value880 ms
32/100
30%
Value0.044
99/100
15%
Value11.3 s
19/100
10%
209 ms
92 ms
49 ms
75 ms
78 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 94% of them (142 requests) were addressed to the original Florais.com.br, 1% (2 requests) were made to Fonts.googleapis.com and 1% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (431 ms) belongs to the original domain Florais.com.br.
Page size can be reduced by 170.3 kB (11%)
1.6 MB
1.4 MB
In fact, the total size of Florais.com.br main page is 1.6 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 938.9 kB which makes up the majority of the site volume.
Potential reduce by 148.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. 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 148.8 kB or 83% of the original size.
Potential reduce by 12.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. Florais images are well optimized though.
Potential reduce by 794 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 8.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. Florais.com.br has all CSS files already compressed.
Number of requests can be reduced by 119 (82%)
146
27
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Florais. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 59 to 1 for JavaScripts and from 62 to 1 for CSS and as a result speed up the page load time.
florais.com.br
209 ms
florais.com.br
92 ms
style.min.css
49 ms
extendify-utilities.css
75 ms
mainstyles.css
78 ms
js_composer.min.css
87 ms
bootstrap-light.min.css
125 ms
base.min.css
82 ms
widget-tag-cloud.min.css
103 ms
widget-recent-post-comments.min.css
112 ms
widget-nav.min.css
119 ms
woo-widget-product-cat.min.css
115 ms
woo-widget-slider-price-filter.min.css
122 ms
wp-gutenberg.min.css
141 ms
int-wpcf7.min.css
144 ms
int-mc4wp.min.css
143 ms
int-rev-slider.min.css
149 ms
int-wpb-base.min.css
152 ms
int-wpb-base-deprecated.min.css
161 ms
woocommerce-base.min.css
173 ms
mod-star-rating.min.css
181 ms
woo-el-track-order.min.css
185 ms
woo-gutenberg.min.css
171 ms
header-base.min.css
187 ms
mod-tools.min.css
190 ms
header-el-base.min.css
208 ms
el-social-icons.min.css
192 ms
header-el-my-account-dropdown.min.css
215 ms
woo-mod-login-form.min.css
217 ms
header-el-my-account.min.css
215 ms
header-el-search.min.css
233 ms
header-el-search-form.min.css
233 ms
wd-search-results.min.css
243 ms
wd-search-form.min.css
253 ms
wd-search-cat.min.css
244 ms
header-el-cart-side.min.css
263 ms
header-el-cart.min.css
270 ms
css
54 ms
sharethis.js
41 ms
js
91 ms
css
70 ms
woo-widget-shopping-cart.min.css
276 ms
woo-widget-product-list.min.css
236 ms
el-section-title.min.css
218 ms
mod-highlighted-text.min.css
226 ms
int-wbp-el-animations.min.css
225 ms
el-section-title-style-simple-and-brd.min.css
215 ms
woo-product-loop.min.css
217 ms
woo-product-loop-icons.min.css
222 ms
woo-mod-product-labels.min.css
220 ms
woo-mod-product-labels-round.min.css
223 ms
lib-magnific-popup.min.css
251 ms
el-section-title-style-under-and-over.min.css
245 ms
el-responsive-text.min.css
193 ms
el-info-box.min.css
224 ms
el-instagram.min.css
218 ms
el-brand.min.css
216 ms
opt-widget-collapse.min.css
229 ms
footer-base.min.css
240 ms
opt-scrolltotop.min.css
214 ms
opt-bottom-toolbar.min.css
225 ms
wc-blocks.css
227 ms
v4-shims.min.css
230 ms
all.min.css
208 ms
animate.min.css
228 ms
rs6.css
253 ms
jquery.min.js
239 ms
jquery-migrate.min.js
242 ms
jquery.blockUI.min.js
246 ms
add-to-cart.min.js
217 ms
js.cookie.min.js
228 ms
woocommerce.min.js
251 ms
woocommerce-add-to-cart.js
242 ms
device.min.js
239 ms
updateCartFragmentsFix.js
291 ms
app.js
206 ms
index.js
273 ms
index.js
203 ms
rbtools.min.js
320 ms
rs6.min.js
314 ms
sourcebuster.min.js
253 ms
order-attribution.min.js
246 ms
js_composer_front.min.js
241 ms
helpers.min.js
289 ms
woocommerceNotices.min.js
277 ms
scrollBar.min.js
278 ms
headerBuilder.min.js
277 ms
wishlist.min.js
273 ms
loginDropdown.min.js
276 ms
autocomplete.min.js
274 ms
ajaxSearch.min.js
332 ms
simpleDropdown.min.js
271 ms
onRemoveFromCart.min.js
326 ms
menuOffsets.min.js
254 ms
menuSetUp.min.js
312 ms
menuDropdownsAJAX.min.js
296 ms
waypoints.min.js
300 ms
animationsOffset.min.js
294 ms
quickShop.min.js
292 ms
swatchesVariations.min.js
288 ms
addToCartAllTypes.min.js
282 ms
underscore.min.js
265 ms
wp-util.min.js
255 ms
add-to-cart-variation.min.js
400 ms
actionAfterAddToCart.min.js
400 ms
tooltips.min.js
394 ms
btnsToolTips.min.js
395 ms
owl.carousel.min.js
389 ms
magnific-popup.min.js
376 ms
productImagesGallery.min.js
377 ms
quickView.min.js
376 ms
woocommerceQuantity.min.js
319 ms
imagesloaded.min.js
318 ms
woodmartCompare.min.js
318 ms
vc-waypoints.min.js
315 ms
widgetCollapse.min.js
315 ms
js
102 ms
analytics.js
93 ms
scrollTop.min.js
263 ms
mobileNavigation.min.js
264 ms
cartWidget.min.js
264 ms
cart-fragments.min.js
263 ms
forms.js
262 ms
logo-florais-terapias.png
262 ms
dummy.png
263 ms
saint-germain-1.png
236 ms
f%C3%B3rmula-medita%C3%A7%C3%A3o-1.jpg
239 ms
02.jpg
234 ms
ansiedade-1.jpg
240 ms
03.jpg
431 ms
05.jpg
293 ms
bom-sono-saint-germain-150x150.jpg
291 ms
emergencial-saint-germain-150x150.jpg
180 ms
F%C3%93RMULA-PROTE%C3%87%C3%83O-150x150.jpg
423 ms
ANIMO-EQUILIBRIO-150x150.jpg
422 ms
florais-five-flowers-12.png
422 ms
011.png
420 ms
0158.png
421 ms
Novidades-promo%C3%A7%C3%B5es-5.png
424 ms
hearling-herbs.png
423 ms
collect
196 ms
gotas-de-orvalho-florais.png
266 ms
formas-pagamento.png
268 ms
payments.png
264 ms
botao-whats-portoes-curitiba.png
265 ms
florais-personalizados-3.jpg
265 ms
font
251 ms
font
252 ms
fa-solid-900.woff
89 ms
fa-regular-400.woff
87 ms
fa-brands-400.woff
88 ms
florais.com.br 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
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.
florais.com.br 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
florais.com.br 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 Florais.com.br 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 Florais.com.br 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.
florais.com.br
Open Graph description is not detected on the main page of Florais. 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: