4.9 sec in total
515 ms
3.3 sec
1 sec
Visit floridence.ru now to see the best up-to-date Floridence content for Russia and also check out these interesting facts you probably never knew about floridence.ru
Сайт интернет-магазина по доставке живых цветов в Ростове-на-Дону
Visit floridence.ruWe analyzed Floridence.ru page load time and found that the first response time was 515 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
floridence.ru performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value18.6 s
0/100
25%
Value8.1 s
21/100
10%
Value1,370 ms
16/100
30%
Value0
100/100
15%
Value14.4 s
9/100
10%
515 ms
77 ms
85 ms
188 ms
186 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 61% of them (65 requests) were addressed to the original Floridence.ru, 11% (12 requests) were made to Vk.com and 5% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Floridence.ru.
Page size can be reduced by 729.8 kB (32%)
2.3 MB
1.5 MB
In fact, the total size of Floridence.ru main page is 2.3 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. 65% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 49.1 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 49.1 kB or 73% of the original size.
Potential reduce by 48.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. Floridence images are well optimized though.
Potential reduce by 503.4 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 503.4 kB or 70% of the original size.
Potential reduce by 129.1 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. Floridence.ru needs all CSS files to be minified and compressed as it can save up to 129.1 kB or 83% of the original size.
Number of requests can be reduced by 27 (27%)
100
73
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Floridence. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
floridence.ru
515 ms
css
77 ms
jquery.min.js
85 ms
jquery.maskedinput.js
188 ms
module.js
186 ms
main.js
274 ms
kernel_main.css
380 ms
template_777f8957c40ac23a1f3c72a93f4b8937.css
585 ms
kernel_main.js
793 ms
kernel_socialservices.js
288 ms
openapi.js
381 ms
ba.js
225 ms
3_1_FFFFFFFF_EFEFEFFF_1_pageviews
307 ms
icons.png
125 ms
d00927017f5e653fc1cb3dda3d6334e1.jpg
257 ms
194acbb4effdfc4464e630d507e00281.jpg
256 ms
f0a850b505dc4eef8f4fd4f4b2ef0601.jpg
264 ms
810692050b345a19f51e36833bbe5463.jpg
259 ms
82970069a229d7cdce42fe38c7299da5.jpg
122 ms
5ff0043839d1114a61ace410bdf80803.jpg
466 ms
afae286568de29bf606376e9187d6cec.jpg
255 ms
780226b302516433c84429135b533e24.jpg
1164 ms
1cf9b39d09b8aee60d1f20fa66cef00e.jpg
1084 ms
559b0178d3b8b2bcf97ba84f3147664d.jpg
381 ms
a3fa0dd522565ac99f10c025d2493db6.jpg
1311 ms
f973e9a0c4adab5a44930a0e8f07f9c2.jpg
495 ms
5bcceb39c63d8387cb76a51d4b31b9d8.jpg
494 ms
1669bc1e29efda4b94bcd18722b4ad22.jpg
699 ms
bc6de2d5693205f7f378601458c1c82f.jpg
578 ms
7aca3290b4aad537c96caeac4f17790f.jpg
583 ms
7be31b7e4070ea8c49c0b959a66f5be1.jpg
704 ms
4e0206f21020e4aff059a6ad5f213a1b.jpg
707 ms
954b196030dd46090eb57a0b8e2dad37.jpg
806 ms
979209ba9825604261f5022d90d5c4b8.jpg
808 ms
88e165b4e8352484a5fcb836bffb7627.png
810 ms
266ce16af4c26f37b0d415a90c21669e.jpg
1013 ms
f79aa119697fad8219bd65288f3c3ab1.jpg
1009 ms
b334161940b1633258e8b452fea5a73e.jpg
942 ms
8dc5e1757ffb35d8282def9bf1ffb286.jpg
1040 ms
d28370e178a82bdfd8d69da6a9ed5c66.jpg
1195 ms
8997e36cf6d7c4a4e1fb954b34a8128d.jpg
1204 ms
52fbe05104ddc5237d220d160861e997.jpg
1139 ms
abbdc4af5063b2ee3bf6bf70f4b23d2f.jpg
1511 ms
8e11e651f01e1740d9216c8b04ccab3c.jpg
1237 ms
c6f50f59d3302786d371fe7c1908cb8f.jpg
1561 ms
fbab29c412f7d582e33e6693a0e04fb1.jpg
1375 ms
e6dd5b3f6cb9d8ef8e7cee7311a0ad57.jpg
1412 ms
df7765d02cf3253fafe6d4cfd1d2027c.jpg
1327 ms
705b957f0f094994882a1af160aea71e.jpg
1597 ms
k3k702ZOKiLJc3WVjuplzIqVA00DzgUWtGeqqZO9M7Q.ttf
129 ms
EInbV5DfGHOiMmvb1Xr-hoqVA00DzgUWtGeqqZO9M7Q.ttf
173 ms
MTP_ySUJH_bn48VBG8sNSoqVA00DzgUWtGeqqZO9M7Q.ttf
220 ms
K88pR3goAWT7BTt32Z01myZ2oysoEQEeKwjgmXLRnTc.ttf
260 ms
DXI1ORHCpsQm3Vp6mXoaTYqVA00DzgUWtGeqqZO9M7Q.ttf
262 ms
upload.gif
175 ms
sdk.js
215 ms
widget_community.php
337 ms
watch.js
13 ms
analytics.js
57 ms
leadback.js
393 ms
rur.woff
1327 ms
rurbd.woff
1365 ms
collect
52 ms
bx_stat
288 ms
opensanscondensed.woff
1271 ms
5ecd2123eba2b84088bba38d2f0e527e.jpg
1305 ms
5a5464efcc8d2a438c1dec8f9c060372.jpg
1453 ms
5621ce4f766927491dcbcd7edf1d1830.jpg
1557 ms
a6c7824532111964800f717d43e52b91.jpg
1439 ms
266 ms
xd_arbiter.php
112 ms
xd_arbiter.php
142 ms
01575189bde480fa439034a240936840.jpg
1269 ms
loader_nav19239_3.js
137 ms
lite.css
165 ms
lite.js
543 ms
lang3_0.js
287 ms
widget_community.css
297 ms
xdm.js
300 ms
al_community.js
313 ms
57fee27edc9846d2adde188c87b30b28.jpg
1480 ms
abf53ae7822111a9bf20d13524056397.jpg
1237 ms
fdefda6e659bb1b6b41234624052a329.jpg
1260 ms
collect
13 ms
jquery.cookie.js
239 ms
round_social_icons.png
1226 ms
logo.png
1285 ms
rating.png
1172 ms
botw.png
1183 ms
separator.png
1255 ms
widget_uuid.php
209 ms
widget_data.php
213 ms
advantages.png
1159 ms
grab.cur
1169 ms
pl.png
1168 ms
social.png
1042 ms
PaQ36SAsT0E.jpg
259 ms
e_f6ca5520.jpg
387 ms
81SVjpm1_j8.jpg
374 ms
TcmYJ1Eqgek.jpg
384 ms
6cE1SUCbA-c.jpg
246 ms
m30IC0xF5FQ.jpg
382 ms
uEHRbMpbLgk.jpg
386 ms
camera_50.png
129 ms
w_logo.png
133 ms
ymap.png
1030 ms
rating_3_0.jpg
436 ms
floridence.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.
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
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.
floridence.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
Page has valid source maps
floridence.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floridence.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Floridence.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.
floridence.ru
Open Graph description is not detected on the main page of Floridence. 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: