4.2 sec in total
647 ms
3.3 sec
322 ms
Visit roshen.com now to see the best up-to-date Roshen content for Ukraine and also check out these interesting facts you probably never knew about roshen.com
Main page -
Visit roshen.comWe analyzed Roshen.com page load time and found that the first response time was 647 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
roshen.com performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value33.9 s
0/100
25%
Value15.8 s
0/100
10%
Value1,360 ms
17/100
30%
Value0
100/100
15%
Value27.3 s
0/100
10%
647 ms
476 ms
550 ms
980 ms
1252 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 97% of them (62 requests) were addressed to the original Roshen.com, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Roshen.com.
Page size can be reduced by 177.8 kB (13%)
1.4 MB
1.2 MB
In fact, the total size of Roshen.com main page is 1.4 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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 10.8 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 10.8 kB or 74% of the original size.
Potential reduce by 36.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. Roshen images are well optimized though.
Potential reduce by 88.7 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 88.7 kB or 64% of the original size.
Potential reduce by 42.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. Roshen.com needs all CSS files to be minified and compressed as it can save up to 42.2 kB or 82% of the original size.
Number of requests can be reduced by 26 (41%)
63
37
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Roshen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
roshen.com
647 ms
jquery.js
476 ms
jquery.js
550 ms
jquery_002.js
980 ms
jquery_004.js
1252 ms
jquery_003.js
1253 ms
swfobject.js
1304 ms
ajax.js
594 ms
jquery.roshenslider.js
669 ms
AC_RunActiveContent.js
714 ms
thickbox.css
790 ms
thickbox.js
835 ms
style.css
1031 ms
jquery.css
955 ms
roshen-skin.css
1075 ms
jquery.fancybox-1.3.0.css
1097 ms
jqtransform.css
1152 ms
demo.css
1196 ms
jquery.jqtransform.js
1218 ms
ga.js
64 ms
bg_body.gif
122 ms
image_10.jpg
363 ms
image_14.jpg
383 ms
image_8.jpg
384 ms
image_13.jpg
363 ms
image_1.jpg
384 ms
image_4.jpg
361 ms
image_2.jpg
603 ms
image_3.jpg
485 ms
image_5.jpg
605 ms
image_9.jpg
636 ms
image_7.jpg
637 ms
image_11.jpg
767 ms
image_6.jpg
727 ms
image_15.jpg
842 ms
image_12.jpg
845 ms
global_news.jpg
763 ms
NEWS_child.jpg
892 ms
EX2.jpg
847 ms
banner_swiss_en.jpg
1020 ms
banner_fountain_en.jpg
892 ms
logo_small.png
962 ms
bg_top.png
915 ms
bg_bottom.png
917 ms
bg_line.gif
969 ms
main_side_top_en.jpg
969 ms
fb_gold.png
1032 ms
vk_gold.png
1034 ms
homepage_top.gif
1037 ms
mailus_top.gif
1094 ms
sitemap_top.gif
1094 ms
planet.png
1094 ms
bg_menu.jpg
1151 ms
global_left_header.gif
1153 ms
article_shadow.png
1156 ms
special_polosa.gif
1218 ms
__utm.gif
11 ms
global_right_header.gif
1160 ms
roshen-world.png
1048 ms
right_ng_about.png
968 ms
main_side_bottom.jpg
970 ms
loadingAnimation.gif
955 ms
select_left.png
1023 ms
select_right.png
1025 ms
roshen.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
ARIA IDs are not unique
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
roshen.com 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
roshen.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Roshen.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Roshen.com 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.
roshen.com
Open Graph description is not detected on the main page of Roshen. 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: