3.6 sec in total
168 ms
3.3 sec
89 ms
Visit roll.com now to see the best up-to-date Roll content for United States and also check out these interesting facts you probably never knew about roll.com
Visit roll.comWe analyzed Roll.com page load time and found that the first response time was 168 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
roll.com performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value7.7 s
3/100
25%
Value4.1 s
79/100
10%
Value320 ms
76/100
30%
Value0
100/100
15%
Value5.0 s
77/100
10%
168 ms
1099 ms
169 ms
158 ms
144 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Roll.com, 96% (78 requests) were made to Wonderful.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Wonderful.com.
Page size can be reduced by 228.4 kB (14%)
1.7 MB
1.4 MB
In fact, the total size of Roll.com 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 12.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 12.0 kB or 77% of the original size.
Potential reduce by 29.6 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. Roll images are well optimized though.
Potential reduce by 171.5 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 171.5 kB or 65% of the original size.
Potential reduce by 15.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. Roll.com needs all CSS files to be minified and compressed as it can save up to 15.1 kB or 76% of the original size.
Number of requests can be reduced by 16 (20%)
79
63
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Roll. 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 6 to 1 for CSS and as a result speed up the page load time.
roll.com
168 ms
www.wonderful.com
1099 ms
ccm.base.css
169 ms
jquery.js
158 ms
ccm.base.js
144 ms
reset.css
185 ms
fonts.css
140 ms
site.css
211 ms
plugins.js
277 ms
main.js
297 ms
Search.js
300 ms
homepage.css
297 ms
home.css
312 ms
main.js
339 ms
Home.js
411 ms
home_landing.js
420 ms
TweenMax.min.js
402 ms
Footer.js
390 ms
TabletFooter.js
418 ms
left_arrow.png
186 ms
right_arrow.png
260 ms
pistachiosTop_ed_2.jpg
262 ms
pistachiosBottomNew.jpg
300 ms
pistachios_reveal.jpg
297 ms
almonds_top.jpg
317 ms
almonds_reveal.jpg
319 ms
almonds_bottom.jpg
391 ms
scarletts_top_3.jpg
419 ms
scarletts_bottom.jpg
455 ms
scarletts_reveal.png
431 ms
scarletts_reveal_bkg.jpg
453 ms
halos_top.jpg
477 ms
halos_reveal.jpg
530 ms
halos_bottom.jpg
1558 ms
pomtop.jpg
571 ms
pombottom.jpg
592 ms
pom_reveal.png
590 ms
justinTop.jpg
631 ms
justin_reveal.png
663 ms
justin_reveal_bkg.jpg
739 ms
justinBottom.jpg
728 ms
landmark_column.jpg
754 ms
landmarkBottom.jpg
789 ms
landmark_reveal.png
802 ms
telefloratop.jpg
879 ms
teleflora_reveal.jpg
895 ms
teleflorabottom.jpg
891 ms
fiji_bottle_top.jpg
939 ms
fiji_cover.jpg
922 ms
ProximaNova-Light-webfont.woff
988 ms
ProximaNova-Reg-webfont.woff
930 ms
fiji_title.png
928 ms
ProximaNova-Sbold-webfont.woff
936 ms
we_are_wonderful.png
939 ms
analytics.js
8 ms
search_img.png
988 ms
search-btn-submit.png
997 ms
collect
12 ms
pistachio_reveal_bkg.jpg
937 ms
almond_reveal_bkg.jpg
977 ms
halos_reveal_bkg.jpg
947 ms
pom_reveal_bkg.jpg
1114 ms
teleflora_reveal_bkg.jpg
1025 ms
fiji_bottle_bottom.jpg
1032 ms
vert_nav_bkg.jpg
976 ms
search-drop-shadow.png
955 ms
wonderful_co_logo.png
1060 ms
brand_indicator_matched.png
1035 ms
footer-drop-shadow.png
1044 ms
fiji_brand_nav.png
1057 ms
subnav_justin.png
1025 ms
landmark_brand_nav.png
1053 ms
subnav_pom.png
1058 ms
subnav_teleflora.png
1063 ms
subnav_almonds.png
1033 ms
subnav_halos.png
1036 ms
pistachios_brand_nav.png
987 ms
subnav_scarletts.png
1027 ms
search_icon.png
1052 ms
search_icon_hover.png
1015 ms
search-btn-submit_highlight.jpg
1001 ms
roll.com accessibility score
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
Form elements do not have associated labels
roll.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
roll.com 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Roll.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 Roll.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.
roll.com
Open Graph description is not detected on the main page of Roll. 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: