5.3 sec in total
322 ms
4.2 sec
750 ms
Welcome to flowers.ee homepage info - get ready to check FLOWERS best content for Estonia right away, or after learning these important things about flowers.ee
Flowers delivery in Tallinn. Flower bouquets, send flowers. Fresh, stunning flowers from skilled florists. Flowers shop in Tallinn, florists service
Visit flowers.eeWe analyzed Flowers.ee page load time and found that the first response time was 322 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
flowers.ee performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value13.6 s
0/100
25%
Value8.8 s
15/100
10%
Value1,480 ms
14/100
30%
Value0.235
53/100
15%
Value9.4 s
30/100
10%
322 ms
415 ms
31 ms
34 ms
197 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 97% of them (111 requests) were addressed to the original Flowers.ee, 3% (3 requests) were made to Fonts.googleapis.com and 1% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Flowers.ee.
Page size can be reduced by 147.6 kB (6%)
2.4 MB
2.2 MB
In fact, the total size of Flowers.ee 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. 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 105.2 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 17.2 kB, which is 14% 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 105.2 kB or 86% of the original size.
Potential reduce by 19.2 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. FLOWERS images are well optimized though.
Potential reduce by 15.5 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. This website has mostly compressed JavaScripts.
Potential reduce by 7.7 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. Flowers.ee has all CSS files already compressed.
Number of requests can be reduced by 54 (55%)
98
44
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FLOWERS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
flowers.ee
322 ms
415 ms
css
31 ms
css
34 ms
bootstrap.min.css
197 ms
front.css
296 ms
visual_composer.css
296 ms
animate.min.css
298 ms
uniform.default.css
294 ms
font-awesome.css
318 ms
novverticalmenu.css
317 ms
novproductcomments.css
390 ms
font-awesome.css
393 ms
pe-icon-7-stroke.css
391 ms
settings.css
396 ms
novadvancedsearch.css
421 ms
js_composer.css
424 ms
banklinkseb.css
486 ms
productcomments.css
487 ms
banklink.css
488 ms
jquery-ui.min.css
488 ms
jquery.ui.theme.min.css
525 ms
homeslider.css
528 ms
owl.carousel.min.css
582 ms
owl.theme.default.min.css
584 ms
novlookbook.css
583 ms
theme.css
892 ms
custom.css
630 ms
css
28 ms
core.js
650 ms
theme.js
692 ms
ps_emailsubscription.js
589 ms
front.js
590 ms
jquery.autocomplete.js
645 ms
novadvancedsearch.js
685 ms
ajax-wishlist.js
687 ms
js_composer_front.js
751 ms
jquery.rating.plugin.js
755 ms
productListingComments.js
783 ms
ajax.js
784 ms
jquery-ui.min.js
1023 ms
responsiveslides.min.js
914 ms
homeslider.js
823 ms
jquery.countdown.min.js
822 ms
jquery.lazyload.min.js
823 ms
jquery.mousewheel.js
820 ms
jquery.sticky-kit.min.js
804 ms
Masonry.pkgd.min.js
801 ms
owl.carousel.min.js
729 ms
slick.min.js
730 ms
owl.carousel.min.js
723 ms
ps_searchbar.js
724 ms
ps_shoppingcart.js
881 ms
global.js
875 ms
novlookbook.js
816 ms
custom.js
815 ms
jquery.themepunch.tools.min.js
814 ms
jquery.themepunch.revolution.min.js
812 ms
flowersee-logo-1463561689-1.png
280 ms
flowers-logo-1622143279.jpg
280 ms
group-icon.png
386 ms
icon-cart.png
280 ms
1.jpg
279 ms
2.jpg
278 ms
3.jpg
384 ms
Coming_Soon_Light-2.jpg
1737 ms
separator-white.png
385 ms
bg5.jpg
1733 ms
s043-flower-arrangements.jpg
385 ms
b041round-wreath.jpg
1734 ms
a147-mixed-bouquet-with-chrysanthemums-and-iris.jpg
1734 ms
a137-mixsed-bouquet-with-roses-and-alstromeria.jpg
1735 ms
s041-bag-with-flowers.jpg
1736 ms
a040-bag-with-flowers.jpg
1738 ms
a136-bouquet-of-alstroemeria.jpg
1737 ms
a136-mixsed-bouquet-with-roses-and-alstromeria.jpg
1649 ms
a145-mix-bouquet.jpg
1649 ms
s39-flowers-in-bag.jpg
1650 ms
flowers-in-bag.jpg
1649 ms
s37-flower-arrangements.jpg
1649 ms
p-18-2.png
1649 ms
p-14-2.png
1650 ms
p-15-2.png
1651 ms
payment2.png
1648 ms
Flower-bouquets.jpg
1649 ms
flowers-BASKETS.jpg
1649 ms
Flower-arrangements.jpg
1650 ms
fontawesome-webfont.woff
1650 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
182 ms
fontawesome-webfont.woff
1471 ms
Material-Design-Iconic-Font.woff
1471 ms
flowers-box.jpg
1470 ms
p8-korzina-s-campari-apelsinovym-sokom-chaemavokadomandariny-i-konfety.jpg
1471 ms
FOR-WEDDING.jpg
1473 ms
Funeral-flowers.jpg
1470 ms
card.jpg
1470 ms
CHOCOLATES-AND-SWEETS--TOYS--DRINKS.jpg
1470 ms
email-white.png
1473 ms
flowersee-logo-footer.png
1473 ms
payment.png
1449 ms
revolution.extension.carousel.min.js
1365 ms
revolution.extension.video.min.js
1365 ms
revolution.extension.slideanims.min.js
1370 ms
vc_carousel.css
1358 ms
prettyPhoto.css
99 ms
revolution.extension.actions.min.js
139 ms
revolution.extension.layeranimation.min.js
160 ms
revolution.extension.kenburn.min.js
158 ms
revolution.extension.navigation.min.js
156 ms
revolution.extension.migration.min.js
155 ms
revolution.extension.parallax.min.js
192 ms
bg_testimoniol3.jpg
266 ms
cusor.png
193 ms
loader.gif
98 ms
revicons.woff
106 ms
flowers.ee 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
Image elements do not have [alt] attributes
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.
flowers.ee 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
flowers.ee SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flowers.ee can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Flowers.ee 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.
flowers.ee
Open Graph description is not detected on the main page of FLOWERS. 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: