okay... hopefully last post here on this matter..
i've learned a lot lately.
if we set the preload, initializing the push, it's a good notion to set the cache on them too... these settings are what i used
# One year for image files
<filesMatch ".(jpg|jpeg|png|gif|ico)$">
Header set Cache-Control "max-age=31536000, public"
</filesMatch>
# One month for css and js
<filesMatch ".(css|js)$">
Header set Cache-Control "max-age=2628000, public"
</filesMatch>
<FilesMatch "\.(htm|html|css|js)$">
AddDefaultCharset UTF-8
DefaultLanguage en-US
</FilesMatch>
and then the magic to escape the 'auto reduction' in rank... the protocols/ciphers you offered were very good, but wouldn't allow a secure transport. these do. in order to use them, simply update openSSL and apache2.4+, and install nghttp2...
ECDHE-ECDSA-AES128-GCM-SHA256
:ECDHE-ECDSA-AES256-GCM-SHA384
:ECDHE-ECDSA-AES128-SHA
:ECDHE-ECDSA-AES256-SHA
:ECDHE-ECDSA-AES128-SHA256
:ECDHE-ECDSA-AES256-SHA384
:ECDHE-RSA-AES128-GCM-SHA256
:ECDHE-RSA-AES256-GCM-SHA384
:ECDHE-RSA-AES128-SHA
:ECDHE-RSA-AES256-SHA
:ECDHE-RSA-AES128-SHA256
:ECDHE-RSA-AES256-SHA384
:DHE-RSA-AES128-GCM-SHA256
:DHE-RSA-AES256-GCM-SHA384
:DHE-RSA-AES128-SHA
:DHE-RSA-AES256-SHA
:DHE-RSA-AES128-SHA256
:DHE-RSA-AES256-SHA256
as of the time of this posting, every one of those offer a secure transport- which is primarily accomplished by avoiding RSA.
the single change (ciphers) bumped me above A- and a flat A, and i'm sure i can tweak it some more to get a straight across 100, but..... i still bring in those adverts and i simply can't account for them.. setting the cache to public an pushing the content took me to speeds i've never seen before- which is basically leveraging the UDP of http2/spdy in mod_http2... would kinda be crazy not to use them, huh?
thank you again, and cheers!!!