Page load time, remove query strings from static resources & defer parsing of js

Hello,

I am optimizing my website with the wp rocket caching plugin and using GTmetrix.com to conduct my speed tests for http://www.oceanportalproject.org.
There are two recommendations to improve my page load speed regarding js files. I will past the recommendations below. I am wondering if you can recommend anything for me to correct these items that GTmetrix thinks are slowing down my page loading.
Here is the first recommendation

RECOMMENDATION GRADE TYPE PRIORITY
Remove query strings from static resources

What does this mean?
Resources with a “?” in the URL are not cached by some proxy caching servers. Remove the query string and encode the parameters into the URL for the following resources:

http://oceanportalproject.org/wp-content/themes/enfold-child/style.css?ver=2
http://oceanportalproject.org/wp-content/themes/enfold/css/base.css?ver=2
http://oceanportalproject.org/wp-content/themes/enfold/css/custom.css?ver=2
http://oceanportalproject.org/wp-content/themes/enfold/css/grid.css?ver=2
http://oceanportalproject.org/wp-content/themes/enfold/css/layout.css?ver=2
http://oceanportalproject.org/wp-content/themes/enfold/css/print.css?ver=1
http://oceanportalproject.org/wp-content/themes/enfold/css/shortcodes.css?ver=2
http://oceanportalproject.org/wp-content/themes/enfold/js/avia-compat.js?ver=2
http://oceanportalproject.org/wp-content/themes/enfold/js/avia.js?ver=3
http://oceanportalproject.org/wp-content/themes/enfold/js/aviapopup/jquery.magnific-popup.min.js?ver=2
http://oceanportalproject.org/wp-content/themes/enfold/js/aviapopup/magnific-popup.css?ver=1
http://oceanportalproject.org/wp-content/themes/enfold/js/mediaelement/skin-1/mediaelementplayer.css?ver=1
http://oceanportalproject.org/wp-content/themes/enfold/js/shortcodes.js?ver=3
http://oceanportalproject.org/wp-content/uploads/dynamic_avia/enfold_child.css?ver=546674c7d047c
http://oceanportalproject.org/wp-includes/js/comment-reply.min.js?ver=4.0
http://oceanportalproject.org/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1
http://oceanportalproject.org/wp-includes/js/jquery/jquery.js?ver=1.11.1
http://oceanportalproject.org/wp-includes/js/mediaelement/mediaelement-and-player.min.js?ver=2.15.0
http://oceanportalproject.org/wp-includes/js/mediaelement/wp-mediaelement.js?ver=4.0

And here is the second:

Defer parsing of JavaScript

What does this mean?
307.3KiB of JavaScript is parsed during initial page load. Defer parsing JavaScript to reduce blocking of page rendering.

http://oceanportalproject.org/wp-includes/js/jquery/jquery.js?ver=1.11.1 (85.7KiB)
http://oceanportalproject.org/wp-content/themes/enfold/js/avia.js?ver=3 (69.3KiB)
http://oceanportalproject.org/wp-content/themes/enfold/js/shortcodes.js?ver=3 (67.1KiB)
http://oceanportalproject.org/wp-includes/js/mediaelement/mediaelement-and-player.min.js?ver=2.15.0 (60.1KiB)
http://oceanportalproject.org/wp-content/themes/enfold/js/aviapopup/jquery.magnific-popup.min.js?ver=2 (17.6KiB)
http://oceanportalproject.org/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1 (5.5KiB)
http://oceanportalproject.org/wp-includes/js/comment-reply.min.js?ver=4.0 (622B)
http://oceanportalproject.org/wp-includes/js/mediaelement/wp-mediaelement.js?ver=4.0 (562B)
http://oceanportalproject.org/wp-content/themes/enfold/js/avia-compat.js?ver=2 (498B)
http://oceanportalproject.org/ (291B of inline JavaScript)

Thanks — George