6.7 sec in total
750 ms
5.3 sec
707 ms
Click here to check amazing Floriol content for Romania. Otherwise, check out these important facts you probably never knew about floriol.ro
Floriol
Visit floriol.roWe analyzed Floriol.ro page load time and found that the first response time was 750 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
floriol.ro performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value21.8 s
0/100
25%
Value11.3 s
5/100
10%
Value5,980 ms
0/100
30%
Value0.202
61/100
15%
Value16.2 s
5/100
10%
750 ms
24 ms
367 ms
185 ms
185 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 73% of them (51 requests) were addressed to the original Floriol.ro, 7% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Assets.pinterest.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Floriol.ro.
Page size can be reduced by 921.1 kB (14%)
6.6 MB
5.6 MB
In fact, the total size of Floriol.ro main page is 6.6 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. 55% of websites need less resources to load. Images take 5.6 MB which makes up the majority of the site volume.
Potential reduce by 82.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 12.3 kB, which is 12% 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 82.7 kB or 81% of the original size.
Potential reduce by 117.7 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. Floriol images are well optimized though.
Potential reduce by 647.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 647.1 kB or 79% of the original size.
Potential reduce by 73.6 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. Floriol.ro needs all CSS files to be minified and compressed as it can save up to 73.6 kB or 87% of the original size.
Number of requests can be reduced by 21 (34%)
61
40
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Floriol. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
floriol.ro
750 ms
css
24 ms
style.css
367 ms
jquery.bxslider.css
185 ms
jquery.jscrollpane.css
185 ms
jquery.fancybox.css
186 ms
style_2.1.2.css
187 ms
jquery.js
560 ms
jquery-migrate.min.js
371 ms
jquery-ui.js
1026 ms
jquery.jscrollpane.min.js
374 ms
jquery.mousewheel.js
379 ms
jquery.fancybox.js
736 ms
main.js
792 ms
button.facebook.js
556 ms
script_2.1.2.js
500 ms
all.js
36 ms
button.googleplus.js
651 ms
pinit.js
24 ms
widgets.js
40 ms
analytics.js
20 ms
over2_app.png
123 ms
close_app2.png
200 ms
icon_flip.png
305 ms
logo.png
305 ms
separator.png
214 ms
fb.png
220 ms
Ardei-Iute-Rosii-Busuioc.jpg
1103 ms
Rosii-Usturoi-si-Busuioc.jpg
1223 ms
Busuioc-si-usturoi.jpg
1496 ms
Floriol-Fortis-pancakes-1024x683.jpg
859 ms
Vitality-1024x681.jpg
1038 ms
Floarea-Soarelui-1024x681.jpg
1050 ms
mediteran5-1024x734.jpg
1532 ms
savor-aprobat-1024x682.jpg
1805 ms
glow.png
1416 ms
herbs_ardei_tagline.png
1284 ms
herbs_rosii_tagline.png
1417 ms
herbs_usturoi_tagline.png
1473 ms
tagline_fortis_1.png
1602 ms
text-vitality_1.png
1605 ms
floareasoarelui1_1.png
1655 ms
mediteran7.png
1685 ms
savor_1a.png
1727 ms
ardei_iute_busuioc_rosii.png
2273 ms
rosii_usturoi_busuioc.png
2164 ms
usturoi_busuioc.png
2310 ms
fortis.png
2325 ms
vitality.png
2366 ms
floarea_soarelui.png
2723 ms
medteranean.png
2826 ms
savor1.png
2839 ms
home_featured.png
2950 ms
pattern.png
2508 ms
plusone.js
48 ms
cambriai.woff
3173 ms
cambriaz.woff
3410 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
57 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
56 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
57 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
75 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
73 ms
93 ms
pinit_main.js
83 ms
collect
50 ms
cb=gapi.loaded_0
73 ms
xd_arbiter.php
51 ms
xd_arbiter.php
118 ms
ping
49 ms
collect
115 ms
floriol.ro accessibility score
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.
floriol.ro 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
floriol.ro SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
RO
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floriol.ro can be misinterpreted by Google and other search engines. Our service has detected that Romanian is used on the page, and it does not match the claimed English language. Our system also found out that Floriol.ro 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.
floriol.ro
Open Graph data is detected on the main page of Floriol. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: