1.2 sec in total
259 ms
670 ms
276 ms
Click here to check amazing Florex content. Otherwise, check out these important facts you probably never knew about florex.ua
Купити декоративні дерева в інтернет-магазині Florex.ua. Найкраще місце для покупки рослин онлайн! Рідкісні сорти алейних дерев з Канади та США. Професійний розсадник декоративних рослин Флорекс Украї...
Visit florex.uaWe analyzed Florex.ua page load time and found that the first response time was 259 ms and then it took 946 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
florex.ua performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value10.3 s
0/100
25%
Value6.6 s
37/100
10%
Value2,250 ms
6/100
30%
Value0
100/100
15%
Value15.2 s
7/100
10%
259 ms
10 ms
19 ms
26 ms
16 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 85% of them (46 requests) were addressed to the original Florex.ua, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (259 ms) belongs to the original domain Florex.ua.
Page size can be reduced by 243.6 kB (38%)
640.9 kB
397.4 kB
In fact, the total size of Florex.ua main page is 640.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 361.9 kB which makes up the majority of the site volume.
Potential reduce by 26.0 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 26.0 kB or 78% of the original size.
Potential reduce by 48.4 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. Obviously, Florex needs image optimization as it can save up to 48.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 137.2 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 137.2 kB or 66% of the original size.
Potential reduce by 31.9 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. Florex.ua needs all CSS files to be minified and compressed as it can save up to 31.9 kB or 82% of the original size.
Number of requests can be reduced by 26 (49%)
53
27
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Florex. 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 6 to 1 for CSS and as a result speed up the page load time.
florex.ua
259 ms
template.css
10 ms
s.css
19 ms
jquery.fancybox-1.3.4.css
26 ms
style.css
16 ms
jquery-1.4.3.min.js
28 ms
wowslider.js
24 ms
easyTooltip.js
20 ms
startstop-slider.js
26 ms
hoverIntent.js
27 ms
jquery.fancybox-1.3.4.js
36 ms
share.js
256 ms
skypeCheck.js
14 ms
jqueryslidemenu.js
38 ms
SevenJS.js
38 ms
jqueryslidemenu.css
37 ms
jquery.jcarousel.js
37 ms
skin.css
37 ms
wrapper_top.png
14 ms
logo.png
45 ms
all.js
13 ms
wrapper_bottom.png
13 ms
top_shadow.png
12 ms
bottom_header.png
34 ms
top_main_menu_bg.png
32 ms
main_menu_right_bot.png
26 ms
top_menu_bg.png
28 ms
bottom_top_menu_li.gif
28 ms
slider_rep.png
28 ms
ts_top_border.gif
26 ms
ts_bottom_border.png
28 ms
352_92.jpg
29 ms
351_92.jpg
28 ms
350_92.jpg
29 ms
349_92.jpg
30 ms
348_92.jpg
31 ms
353_92.jpg
30 ms
354_92.jpg
30 ms
355_92.jpg
31 ms
main1.jpg
64 ms
left_menu_li.png
64 ms
91 ms
1_165.png
48 ms
2_165.png
67 ms
3_165.png
65 ms
4_165.png
66 ms
content_bottom_border.png
44 ms
bottomlogo.png
44 ms
ga.js
35 ms
xd_arbiter.php
36 ms
xd_arbiter.php
42 ms
arrow_prev.png
26 ms
arrow_next.png
26 ms
__utm.gif
12 ms
florex.ua 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
<frame> or <iframe> elements do not have a title
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.
florex.ua best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
florex.ua 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
UK
EN
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Florex.ua can be misinterpreted by Google and other search engines. Our service has detected that Ukrainian is used on the page, and it does not match the claimed English language. Our system also found out that Florex.ua 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.
florex.ua
Open Graph description is not detected on the main page of Florex. 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: