5.9 sec in total
439 ms
4.7 sec
768 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 439 ms and then it took 5.4 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.4 s
16/100
10%
Value13.4 s
0/100
25%
Value10.0 s
9/100
10%
Value1,930 ms
8/100
30%
Value0.234
53/100
15%
Value10.0 s
27/100
10%
439 ms
440 ms
31 ms
30 ms
227 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 96% of them (107 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.9 sec) belongs to the original domain Flowers.ee.
Page size can be reduced by 145.7 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 103.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. This page needs HTML code to be minified as it can gain 17.0 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 103.7 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.1 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 (57%)
95
41
The browser has sent 95 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
439 ms
440 ms
css
31 ms
css
30 ms
bootstrap.min.css
227 ms
front.css
340 ms
visual_composer.css
341 ms
animate.min.css
343 ms
uniform.default.css
341 ms
font-awesome.css
350 ms
novverticalmenu.css
350 ms
novproductcomments.css
452 ms
font-awesome.css
454 ms
pe-icon-7-stroke.css
453 ms
settings.css
455 ms
novadvancedsearch.css
465 ms
js_composer.css
469 ms
banklinkseb.css
564 ms
productcomments.css
565 ms
banklink.css
566 ms
jquery-ui.min.css
566 ms
jquery.ui.theme.min.css
582 ms
homeslider.css
585 ms
owl.carousel.min.css
676 ms
owl.theme.default.min.css
677 ms
novlookbook.css
677 ms
theme.css
1136 ms
custom.css
698 ms
css
26 ms
core.js
721 ms
theme.js
915 ms
ps_emailsubscription.js
682 ms
front.js
682 ms
jquery.autocomplete.js
709 ms
novadvancedsearch.js
795 ms
ajax-wishlist.js
795 ms
js_composer_front.js
826 ms
jquery.rating.plugin.js
837 ms
productListingComments.js
907 ms
ajax.js
908 ms
jquery-ui.min.js
1240 ms
responsiveslides.min.js
833 ms
homeslider.js
791 ms
jquery.countdown.min.js
790 ms
jquery.lazyload.min.js
797 ms
jquery.mousewheel.js
1010 ms
jquery.sticky-kit.min.js
1003 ms
Masonry.pkgd.min.js
1002 ms
owl.carousel.min.js
902 ms
slick.min.js
901 ms
owl.carousel.min.js
898 ms
ps_searchbar.js
899 ms
ps_shoppingcart.js
952 ms
global.js
945 ms
novlookbook.js
853 ms
custom.js
852 ms
jquery.themepunch.tools.min.js
987 ms
jquery.themepunch.revolution.min.js
986 ms
flowersee-logo-1463561689-1.png
288 ms
flowers-logo-1622143279.jpg
288 ms
group-icon.png
288 ms
icon-cart.png
289 ms
1.jpg
290 ms
2.jpg
290 ms
3.jpg
347 ms
Coming_Soon_Light-2.jpg
1938 ms
separator-white.png
346 ms
bg5.jpg
1936 ms
a147-mixed-bouquet-with-chrysanthemums-and-iris.jpg
404 ms
a137-mixsed-bouquet-with-roses-and-alstromeria.jpg
404 ms
s041-bag-with-flowers.jpg
1936 ms
a040-bag-with-flowers.jpg
1937 ms
a136-bouquet-of-alstroemeria.jpg
1939 ms
a136-mixsed-bouquet-with-roses-and-alstromeria.jpg
1939 ms
a145-mix-bouquet.jpg
1939 ms
s39-flowers-in-bag.jpg
1940 ms
flowers-in-bag.jpg
1941 ms
s37-flower-arrangements.jpg
1941 ms
s21-flower-arrangements.jpg
1942 ms
bouquet-of-51-roses.jpg
1862 ms
p-18-2.png
1862 ms
p-14-2.png
1863 ms
p-15-2.png
1862 ms
payment2.png
1861 ms
Flower-bouquets.jpg
1863 ms
flowers-BASKETS.jpg
1866 ms
Flower-arrangements.jpg
1862 ms
flowers-box.jpg
1866 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
199 ms
fontawesome-webfont.woff
1801 ms
fontawesome-webfont.woff
1802 ms
Material-Design-Iconic-Font.woff
1801 ms
p8-korzina-s-campari-apelsinovym-sokom-chaemavokadomandariny-i-konfety.jpg
1664 ms
FOR-WEDDING.jpg
1665 ms
Funeral-flowers.jpg
1665 ms
card.jpg
1665 ms
CHOCOLATES-AND-SWEETS--TOYS--DRINKS.jpg
1666 ms
email-white.png
1666 ms
flowersee-logo-footer.png
1666 ms
payment.png
1665 ms
bg_testimoniol3.jpg
1644 ms
cusor.png
1610 ms
revolution.extension.carousel.min.js
1559 ms
revolution.extension.video.min.js
1555 ms
vc_carousel.css
1540 ms
prettyPhoto.css
114 ms
revolution.extension.slideanims.min.js
173 ms
revolution.extension.actions.min.js
177 ms
revolution.extension.layeranimation.min.js
174 ms
revolution.extension.kenburn.min.js
176 ms
revolution.extension.navigation.min.js
171 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: