63.8 sec in total
2.1 sec
56.8 sec
4.8 sec
Click here to check amazing Floristan content for Russia. Otherwise, check out these important facts you probably never knew about floristan.ru
Салон работает ежедневно. Заказы принимаются круглосуточно, доставка вне рабочие часы салона принимаются заранее
Visit floristan.ruWe analyzed Floristan.ru page load time and found that the first response time was 2.1 sec and then it took 61.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
floristan.ru performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value5.7 s
17/100
25%
Value7.8 s
23/100
10%
Value1,770 ms
10/100
30%
Value0.001
100/100
15%
Value14.8 s
8/100
10%
2138 ms
93 ms
59 ms
391 ms
402 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 81% of them (109 requests) were addressed to the original Floristan.ru, 5% (7 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (20.3 sec) belongs to the original domain Floristan.ru.
Page size can be reduced by 599.7 kB (13%)
4.8 MB
4.2 MB
In fact, the total size of Floristan.ru main page is 4.8 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 4.4 MB which makes up the majority of the site volume.
Potential reduce by 95.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 12.7 kB, which is 11% 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 95.4 kB or 83% of the original size.
Potential reduce by 385.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. Floristan images are well optimized though.
Potential reduce by 77.9 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 77.9 kB or 39% of the original size.
Potential reduce by 41.3 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. Floristan.ru needs all CSS files to be minified and compressed as it can save up to 41.3 kB or 84% of the original size.
Number of requests can be reduced by 21 (18%)
120
99
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Floristan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
floristan.ru
2138 ms
css
93 ms
css
59 ms
layout.css
391 ms
jquery.fancybox.css
402 ms
jquery.min.js
118 ms
jquery.form.min.js
152 ms
jquery.easing.js
396 ms
jquery.fancybox.js
595 ms
jquery.cycle.js
392 ms
jquery.maskedinput.js
425 ms
jquery.cookie.js
588 ms
jquery.json.js
1356 ms
init.js
1950 ms
openapi.js
19876 ms
share.js
34 ms
conversion.js
108 ms
ga.js
20 ms
analytics.js
46 ms
__utm.gif
36 ms
collect
53 ms
bg-pat.jpg
6015 ms
head-bg.jpg
14714 ms
menu-catalog-flower.png
214 ms
logo.png
371 ms
header-arrow.png
217 ms
guarantee.png
498 ms
promo.png
784 ms
discount.png
698 ms
flor-separat.png
503 ms
621bd1.png
1149 ms
1153a7c.png
1374 ms
5583b6.png
1137 ms
25778b9.png
1444 ms
70b64a.png
1728 ms
1310bc7.png
1730 ms
12b5e0b.png
1947 ms
magnifying.gif
1660 ms
568d731.jpg
1842 ms
pen.png
1891 ms
vkontakte.png
1884 ms
insta.png
2019 ms
1224c4db.jpg
2802 ms
32e8d0d.jpg
2442 ms
1441b13b.jpg
2700 ms
1616e62a.jpg
2551 ms
236af7d.jpg
3020 ms
1426cf81.jpg
3176 ms
22b34cd.jpg
3310 ms
460e03b.jpg
3644 ms
382a6fe.jpg
5006 ms
505ef93.jpg
4776 ms
1579bed9.jpg
4680 ms
33e91c7.jpg
4506 ms
77dd892.jpg
5830 ms
48e0712.jpg
7783 ms
143c27e2.jpg
8685 ms
nBF2d6Y3AbOwfkBM-9HcWKCWcynf_cDxXwCLxiixG1c.ttf
264 ms
IiMFELcoPB-OzGzq14k4eqCWcynf_cDxXwCLxiixG1c.ttf
353 ms
4z2U46_RRLOfkoHsWJG3v6CWcynf_cDxXwCLxiixG1c.ttf
458 ms
RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf
386 ms
k3k702ZOKiLJc3WVjuplzPOEPOIfcPv-fZ-WyMUtx48.ttf
385 ms
PRmiXeptR36kaC0GEAetxkKHlodXgisC9y12ja1Qqzw.ttf
391 ms
xjAJXh38I15wypJXxuGMBpp-63r6doWhTEbsfBIRJ7A.ttf
386 ms
362 ms
AmazingGrotesk-DemiBold.woff
9895 ms
AmazingGrotesk.woff
7314 ms
watch.js
152 ms
b-share-form-button.png
208 ms
watch.js
8 ms
b-share-form-button_share__icon.png
223 ms
b-share-icon.png
308 ms
b-share-popup_down__tail.png
509 ms
150d2420.jpg
8170 ms
146a81da.jpg
7639 ms
149d43f8.jpg
8577 ms
198 ms
13705fd2.jpg
8010 ms
9728ddb.jpg
10391 ms
1702f6dc.jpg
10973 ms
11724090.jpg
8370 ms
1683abfe.jpg
8625 ms
10535fb0.jpg
9221 ms
175ef0ef.jpg
9204 ms
179511c9.jpg
11922 ms
377414c.jpg
11048 ms
1060bf39.jpg
9769 ms
1698bf8c.jpg
11781 ms
242b351.jpg
11085 ms
108392c0.jpg
11436 ms
1637b0f1.jpg
11564 ms
167d5cc7.jpg
11443 ms
112eb4f7.jpg
11761 ms
176dfde7.jpg
11441 ms
17157bab.jpg
16271 ms
177cfb00.jpg
14726 ms
160e15dc.jpg
12738 ms
1358e017.jpg
12439 ms
14558f7c.jpg
12503 ms
16206359.jpg
12746 ms
154c58d6.jpg
15577 ms
173ba0f7.jpg
12963 ms
121bd4b5.jpg
12559 ms
2016dd1.jpg
12750 ms
53901da.jpg
12666 ms
1591a465.jpg
11284 ms
908b6f8.jpg
11262 ms
153a110c.jpg
11044 ms
166a3d23.jpg
11478 ms
5907ff5.jpg
11009 ms
155d555c.jpg
10979 ms
165c5612.jpg
11974 ms
15839178.jpg
11348 ms
1100e306.jpg
11616 ms
99cf871.jpg
10157 ms
55714ae.jpg
11693 ms
8513dff.jpg
12302 ms
211fb9d.jpg
9937 ms
98132b6.jpg
12215 ms
5229f9e.jpg
11283 ms
111941c4.jpg
9218 ms
357bb32.jpg
10097 ms
92c5e6c.jpg
9458 ms
foot-vk.png
8939 ms
foot-logo.png
9288 ms
new.png
10699 ms
promo.png
9276 ms
hit.png
9139 ms
skidka.png
9046 ms
site-foot-flowers.png
20259 ms
foot-decor.png
7737 ms
icon1.png
7651 ms
topcart-basket.png
7451 ms
Popup1.png
6534 ms
Popup2.png
6585 ms
floristan.ru 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.
floristan.ru 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
Missing source maps for large first-party JavaScript
floristan.ru SEO score
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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floristan.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Floristan.ru 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.
floristan.ru
Open Graph description is not detected on the main page of Floristan. 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: