3 sec in total
495 ms
2.2 sec
277 ms
Click here to check amazing Fructus content. Otherwise, check out these important facts you probably never knew about fructus.rs
Čaj za vaše zlatne trenutke
Visit fructus.rsWe analyzed Fructus.rs page load time and found that the first response time was 495 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
fructus.rs performance score
name
value
score
weighting
Value14.4 s
0/100
10%
Value20.6 s
0/100
25%
Value15.4 s
0/100
10%
Value250 ms
85/100
30%
Value0.004
100/100
15%
Value24.1 s
0/100
10%
495 ms
125 ms
246 ms
235 ms
239 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 91% of them (29 requests) were addressed to the original Fructus.rs, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (943 ms) belongs to the original domain Fructus.rs.
Page size can be reduced by 663.5 kB (39%)
1.7 MB
1.1 MB
In fact, the total size of Fructus.rs main page is 1.7 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. 40% of websites need less resources to load. Images take 996.2 kB which makes up the majority of the site volume.
Potential reduce by 17.5 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 17.5 kB or 76% of the original size.
Potential reduce by 66.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. Fructus images are well optimized though.
Potential reduce by 147.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 147.2 kB or 65% of the original size.
Potential reduce by 432.2 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. Fructus.rs needs all CSS files to be minified and compressed as it can save up to 432.2 kB or 91% of the original size.
Number of requests can be reduced by 12 (39%)
31
19
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fructus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
fructus.rs
495 ms
css_RTOEeiYJ8lw3GCVsj52-QDVJIKnTa3uTUUEqyHVCu7I.css
125 ms
css_vZ_wrMQ9Og-YPPxa1q4us3N7DsZMJa-14jShHgRoRNo.css
246 ms
css_TsVRTbLFUpEZAfw-_bWPJu840QT523CPjUVJ5MRWfyk.css
235 ms
css_5xFxK_m_3l1IF2rfun5Mb1ArVZIw31CkNJpvUdbcIT8.css
239 ms
css_CsT-DMJuEcyD6TFBYVsL9_W0q9zdzZhsqk_oKjLI0Rs.css
466 ms
respond.min.js
248 ms
jquery.min.js
8 ms
js_IkgOrrVZK1UTp2HktvFi5vo1g7b25Muyr5GoySikuic.js
249 ms
js_obFUyTbqtcoGQtszVI46l1_oD927PzlDtlr_ilpYBqE.js
353 ms
js_R9UbiVw2xuTUI0GZoaqMDOdX0lrZtgX-ono8RVOUEVc.js
352 ms
js_vA5gKQ5xXvjCt3JhZg2xknEcr70DGNKNeUKhkOh-tt8.js
363 ms
js_-PMXwHkoDctr0mO4B_yEeSGfNnX1HMj5SOioDwdzf3o.js
514 ms
ga.js
77 ms
fructus_menu_btn_home.jpg
127 ms
fructus_logo.png
241 ms
fructus_menu_btn_facebook.jpg
242 ms
promo_btn_left.png
126 ms
promo_btn_right.png
130 ms
Baby_promo_0.jpg
745 ms
fructus_promo2.jpg
827 ms
fructus_promo1.jpg
943 ms
tea_i.png
256 ms
rooibos_promo_0.png
590 ms
findoutmoresmall.png
357 ms
zeleni_promo_0.png
637 ms
image.png
714 ms
sr.png
711 ms
en.png
760 ms
__utm.gif
12 ms
css_2THG1eGiBIizsWFeexsNe1iDifJ00QRS9uSd03rY9co.css
119 ms
tea_g.png
125 ms
fructus.rs 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
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
fructus.rs 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
Page has valid source maps
fructus.rs SEO score
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
EN
SR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fructus.rs can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Serbian language. Our system also found out that Fructus.rs 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.
fructus.rs
Open Graph description is not detected on the main page of Fructus. 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: