6.3 sec in total
1.8 sec
4.1 sec
360 ms
Welcome to rrforum.org homepage info - get ready to check Rr Forum best content right away, or after learning these important things about rrforum.org
RRForum - Collaborative, research-based Best Practices that help retailers and their communities prevent underage alcohol and tobacco sales and abuse
Visit rrforum.orgWe analyzed Rrforum.org page load time and found that the first response time was 1.8 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
rrforum.org performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value17.0 s
0/100
25%
Value17.2 s
0/100
10%
Value2,760 ms
3/100
30%
Value0.874
4/100
15%
Value21.6 s
1/100
10%
1788 ms
56 ms
72 ms
69 ms
27 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 75% of them (80 requests) were addressed to the original Rrforum.org, 10% (11 requests) were made to Fonts.gstatic.com and 7% (8 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Rrforum.org.
Page size can be reduced by 2.7 MB (57%)
4.7 MB
2.0 MB
In fact, the total size of Rrforum.org main page is 4.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 111.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 111.5 kB or 78% of the original size.
Potential reduce by 256.9 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, Rr Forum needs image optimization as it can save up to 256.9 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.2 MB
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 1.2 MB or 73% of the original size.
Potential reduce by 1.1 MB
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. Rrforum.org needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 83% of the original size.
Number of requests can be reduced by 73 (77%)
95
22
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rr Forum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
rrforum.org
1788 ms
wp-emoji-release.min.js
56 ms
validationEngine.jquery.css
72 ms
layerslider.css
69 ms
css
27 ms
styles.css
67 ms
events_manager.css
240 ms
go_pricing_styles.css
938 ms
mediaelementplayer.min.css
89 ms
mediaelementplayer.css
103 ms
style.css
101 ms
tp_twitter_plugin.css
99 ms
settings.css
126 ms
captions.php
922 ms
font-awesome.min.css
134 ms
css
29 ms
css
33 ms
css
29 ms
css
31 ms
main.css
276 ms
font-awesome.min.css
162 ms
custom-56ee018d11.css
1307 ms
media.css
170 ms
royalslider.css
199 ms
style.css
203 ms
jquery.js
297 ms
jquery-migrate.min.js
236 ms
layerslider.kreaturamedia.jquery.js
310 ms
greensock.js
307 ms
layerslider.transitions.js
310 ms
core.min.js
313 ms
widget.min.js
341 ms
position.min.js
346 ms
mouse.min.js
347 ms
sortable.min.js
350 ms
datepicker.min.js
490 ms
menu.min.js
383 ms
autocomplete.min.js
383 ms
resizable.min.js
385 ms
draggable.min.js
419 ms
button.min.js
417 ms
dialog.min.js
420 ms
css
24 ms
css
27 ms
css
32 ms
js_composer_front.css
455 ms
flexslider.css
400 ms
events-manager.js
434 ms
events-manager-pro.js
438 ms
app.js
415 ms
jquery.themepunch.plugins.min.js
518 ms
jquery.themepunch.revolution.min.js
446 ms
cc-widget.js
439 ms
modernizr.js
416 ms
svg-icons.js
446 ms
jquery.form.min.js
416 ms
scripts.js
409 ms
go_pricing_scripts.js
413 ms
style.css
411 ms
mediaelement-and-player.min.js
387 ms
wp-mediaelement.js
412 ms
jquery.placeholder.min.js
470 ms
jquery.royalslider.js
396 ms
plugins.js
408 ms
desktop-tablet.js
374 ms
desktop.js
410 ms
main.js
423 ms
wp-embed.min.js
410 ms
js_composer_front.js
412 ms
jquery.flexslider-min.js
427 ms
waypoints.min.js
436 ms
handslogo-whitebg-75x72.png
486 ms
handslogo.png
467 ms
banner2.png
474 ms
email.jpg
53 ms
millercoors.png
465 ms
nbwa.png
466 ms
NABCA.png
467 ms
diageo.png
470 ms
39276_BFLogoCS_AdditionalFile-7.png
472 ms
logo-wordsonly-2.png
470 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
46 ms
DXI1ORHCpsQm3Vp6mXoaTRa1RVmPjeKy21_GQJaLlJI.woff
46 ms
C2urQxGk-1w
451 ms
stock-reports.jpg
426 ms
stock-conference.jpg
466 ms
stock-programs.jpg
426 ms
tXSgPxDl7Lk8Zr_5qX8FIQfd-b-I5PxxcmB4_-MNcqw.woff
402 ms
efd6FGWWGX5Z3ztwLBrG9b2aU247V0zTzydO4RoO9Ok.woff
403 ms
timer.png
172 ms
shadow1.png
172 ms
grab.png
172 ms
hands-transparentbg.png
172 ms
www-embed-player-vfl-z2BtK.css
171 ms
www-embed-player.js
229 ms
base.js
245 ms
8N1PdXpbG6RtFvTjl-5E7YM8pfYvjMoOxygpzLVILAs.woff
114 ms
Uvi-cRwyvqFpl9j3oT2mqnl4twXkwp3_u9ZoePkT564.woff
114 ms
WZDISdyil4HsmirlOdBRFHhCUOGz7vYGh680lGh-uXM.woff
188 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
114 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
114 ms
fontawesome-webfont.woff
261 ms
fontawesome-webfont.woff
188 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
48 ms
ad_status.js
77 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
35 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
36 ms
rrforum.org 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
Heading elements are not in a sequentially-descending order
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.
rrforum.org 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
rrforum.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rrforum.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Rrforum.org 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.
rrforum.org
Open Graph description is not detected on the main page of Rr Forum. 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: