5.6 sec in total
525 ms
4.6 sec
457 ms
Click here to check amazing Flowerty content for Russia. Otherwise, check out these important facts you probably never knew about flowerty.ru
Интернет-магазин Flowerty.ru предлагает заказать цветы с доставкой на дом в Москве. У нас вы можете сделать это онлайн не выходя из дома и мы бесплатно доставим цветы в день заказа ✔. Самые красивые ц...
Visit flowerty.ruWe analyzed Flowerty.ru page load time and found that the first response time was 525 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
flowerty.ru performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value9.6 s
0/100
25%
Value10.7 s
7/100
10%
Value1,200 ms
20/100
30%
Value0.017
100/100
15%
Value21.9 s
1/100
10%
525 ms
625 ms
312 ms
780 ms
384 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 84% of them (78 requests) were addressed to the original Flowerty.ru, 11% (10 requests) were made to Cp.onicon.ru and 3% (3 requests) were made to Static.flipcat.ru. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Flowerty.ru.
Page size can be reduced by 816.7 kB (46%)
1.8 MB
976.4 kB
In fact, the total size of Flowerty.ru main page is 1.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. 35% of websites need less resources to load. Javascripts take 822.8 kB which makes up the majority of the site volume.
Potential reduce by 45.3 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 10.5 kB, which is 19% 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 45.3 kB or 82% of the original size.
Potential reduce by 41.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. Flowerty images are well optimized though.
Potential reduce by 602.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 602.5 kB or 73% of the original size.
Potential reduce by 127.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. Flowerty.ru needs all CSS files to be minified and compressed as it can save up to 127.5 kB or 79% of the original size.
Number of requests can be reduced by 21 (25%)
85
64
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flowerty. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
flowerty.ru
525 ms
www.flowerty.ru
625 ms
style_1.css
312 ms
jquery.js
780 ms
zhtqc61y.js
384 ms
jquery.smartbanner.css
133 ms
jquery.smartbanner.js
388 ms
bg.png
156 ms
simple_loader.js
325 ms
logo_bg.jpg
156 ms
logo.jpg
280 ms
konz.png
312 ms
en.png
312 ms
sk_box.jpg
312 ms
top_ul.png
315 ms
t_li_bg.png
314 ms
sub_menu_bg.png
431 ms
t_li_bg1.png
463 ms
top-payments.png
465 ms
366-0.jpg
773 ms
add1.jpg
466 ms
smal.png
775 ms
296-0.jpg
897 ms
s8.png
929 ms
208-0.jpg
662 ms
256-0.jpg
659 ms
384-0.jpg
815 ms
218-0.jpg
967 ms
ssssssStanding_Large550_105672.png
1078 ms
ssssss4323.png
1078 ms
430-0.jpg
965 ms
204-0.jpg
1043 ms
205-0.jpg
1075 ms
sssss8888Standing_Large550_85670.png
1273 ms
189-0.jpg
1120 ms
258-0.jpg
1198 ms
365-0.jpg
1382 ms
224-0.jpg
1231 ms
187-0.jpg
1231 ms
sssssssssssStanding_Large550_85671.png
1274 ms
search.png
1352 ms
input_s.png
1382 ms
sub_s.png
1384 ms
status.png
1425 ms
hit
257 ms
r_bg.jpg
1321 ms
li_bg3.png
1368 ms
mobile.png
1273 ms
simple_loader.js
425 ms
hit
127 ms
right_t.png
1241 ms
best.png
1242 ms
add2.png
1284 ms
li_bg2.png
1283 ms
zoom_1.jpg
1363 ms
2121weq21.png
1275 ms
hit.png
1243 ms
add3.png
1311 ms
li_bg.png
1311 ms
visa.jpg
1115 ms
wm.jpg
1168 ms
bootstrap.min.js
95 ms
m_mes.jpg
1088 ms
rbk.jpg
1086 ms
bootstrap.min.js
100 ms
qiwi.jpg
1047 ms
evroset.jpg
1007 ms
onicon.site.min.css
97 ms
onicon.site.min.js
185 ms
sv.jpg
975 ms
mw.jpg
1015 ms
tele.jpg
1042 ms
onicon.site.min.css
199 ms
qiwi2.jpg
965 ms
ks.jpg
939 ms
m_e.jpg
975 ms
eleck.jpg
975 ms
onicon.site.min.js
604 ms
plat.jpg
1013 ms
p_e.jpg
962 ms
wc.jpg
931 ms
cont.jpg
935 ms
vp.jpg
933 ms
a_.jpg
929 ms
hb.jpg
933 ms
beeline.jpg
933 ms
mts.jpg
931 ms
p_.jpg
937 ms
payment.jpg
932 ms
system.jpg
931 ms
logo-payu3.png
931 ms
hosts-2.js
97 ms
hosts-2.js
101 ms
flowerty.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
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.
flowerty.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
flowerty.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flowerty.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 Flowerty.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
flowerty.ru
Open Graph description is not detected on the main page of Flowerty. 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: