8.3 sec in total
1.7 sec
6.1 sec
531 ms
Visit webflor.pt now to see the best up-to-date Webflor content and also check out these interesting facts you probably never knew about webflor.pt
Entregas de Flores em Portugal no mesmo dia. Flores para casamentos. Coroas de Flores. Cestas de flores com presentes. Entregas no estrangeiro em 24h. Bouquets de Flores, Rosas, Plantas, chocolates, u...
Visit webflor.ptWe analyzed Webflor.pt page load time and found that the first response time was 1.7 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
webflor.pt performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value11.5 s
0/100
25%
Value20.1 s
0/100
10%
Value2,630 ms
4/100
30%
Value0.269
45/100
15%
Value21.1 s
1/100
10%
1685 ms
287 ms
486 ms
417 ms
310 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 86% of them (80 requests) were addressed to the original Webflor.pt, 5% (5 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Webflor.pt.
Page size can be reduced by 236.7 kB (10%)
2.4 MB
2.2 MB
In fact, the total size of Webflor.pt main page is 2.4 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 104.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 104.8 kB or 81% of the original size.
Potential reduce by 34.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. Webflor images are well optimized though.
Potential reduce by 94.3 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 94.3 kB or 16% of the original size.
Potential reduce by 3.2 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. Webflor.pt has all CSS files already compressed.
Number of requests can be reduced by 65 (76%)
85
20
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Webflor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
webflor.pt
1685 ms
c15nc.css
287 ms
fuumu.css
486 ms
c15nc.css
417 ms
c15na.css
310 ms
c15na.css
320 ms
c15na.css
440 ms
c15na.css
506 ms
css
47 ms
css
65 ms
css
69 ms
css
75 ms
2i6zp.css
581 ms
c15n9.css
573 ms
c15nc.js
551 ms
c15nc.js
543 ms
s-202422.js
30 ms
c15nc.js
618 ms
c15nc.js
619 ms
c15n9.css
669 ms
wpmenucart.min.js
699 ms
jquery.selectBox.min.js
714 ms
jquery.prettyPhoto.min.js
700 ms
jquery.yith-wcwl.min.js
699 ms
index.js
731 ms
index.js
773 ms
jquery.blockUI.min.js
793 ms
add-to-cart.min.js
791 ms
js.cookie.min.js
805 ms
woocommerce.min.js
827 ms
cart-fragments.min.js
836 ms
core.min.js
889 ms
mouse.min.js
890 ms
sortable.min.js
897 ms
tabs.min.js
906 ms
accordion.min.js
932 ms
plugins.js
964 ms
menu.js
1016 ms
animations.min.js
1017 ms
jplayer.min.js
1014 ms
translate3d.js
1023 ms
api.js
49 ms
e-202422.js
20 ms
scripts.js
1057 ms
draggable.min.js
800 ms
slider.min.js
827 ms
jquery.ui.touch-punch.js
830 ms
iris.min.js
737 ms
wp-polyfill-inert.min.js
706 ms
regenerator-runtime.min.js
695 ms
wp-polyfill.min.js
659 ms
hooks.min.js
697 ms
i18n.min.js
716 ms
color-picker.min.js
685 ms
datepicker.min.js
672 ms
progressbar.min.js
660 ms
underscore.min.js
643 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff
25 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrc.woff
39 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff
46 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMDrMfJg.woff
47 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LDrMfJg.woff
69 ms
wp-util.min.js
678 ms
add-to-cart-variation.min.js
677 ms
front.min.js
673 ms
index.js
688 ms
hoverIntent.min.js
745 ms
maxmegamenu.js
726 ms
owl.carousel.min.js
705 ms
custom.js
692 ms
popup.js
685 ms
mfn-icons.woff
763 ms
fontawesome-webfont.woff
792 ms
cover-sub.jpg
871 ms
webflorpt_3fc20057141462bd40e3b0eecc87b384.png
684 ms
box_shadow.png
693 ms
bouquet-flores-mix-2-webflor-350x350.jpg
699 ms
Bouquet-rosas-estilo-350x350.jpg
891 ms
BQ_12_rosas_flor_de_cera-450-350x350.jpg
746 ms
cesta-flores-portugal-15-350x350.jpg
758 ms
bouquet-lisboa-350x350.jpg
689 ms
BQ-200211-450-350x350.jpg
715 ms
roses-12-mix-350x350.png
931 ms
Caixa-com-Rosas-350x350.jpg
834 ms
bouquet-campestre-chocolate-1-350x350.jpg
773 ms
Jar-of-roses-350x350.jpg
867 ms
Serenata-de-Tulipas-2-350x350.jpg
727 ms
bouquet-margaridas-2-350x350.jpg
803 ms
white_d22efa1530bc6e8e277ce3175442f2fe.png
792 ms
livro_reclamacoes-500x-207-w.png
800 ms
parralax-bg2.jpg
1080 ms
recaptcha__en.js
20 ms
c15na.css
125 ms
webflor.pt 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
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.
webflor.pt 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
webflor.pt 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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webflor.pt 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 Webflor.pt 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.
webflor.pt
Open Graph data is detected on the main page of Webflor. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: