Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 171.1KiB (80% reduction).
Compressing http://askcom.me/css/bootstrap.css could save 117.8KiB (85% reduction).
Compressing http://askcom.me/js/bootstrap.min.js could save 25.4KiB (73% reduction).
Compressing https://query.yahooapis.com/v1/public/yql?q=SELECT…471704&_=1505281471705 could save 11.2KiB (78% reduction).
Compressing http://askcom.me/css/style.css could save 7.9KiB (76% reduction).
Compressing http://cpanel.nativeads.com/js/pixel/pixel-119812-…aa77f1836a4c782fb27.js could save 2.5KiB (52% reduction).
Compressing https://d31qbv1cthcecs.cloudfront.net/atrk.js could save 2.2KiB (61% reduction).
Compressing http://askcom.me/js/FeedEk.js could save 1.7KiB (61% reduction).
Compressing https://i.simpli.fi/dpx.js?cid=36328&m=1&sifi_tuid=17450 could save 1.7KiB (62% reduction).
Compressing http://askcom.me/js/SearchFun.js could save 681B (54% reduction).
Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
Only about 18% of the final above-the-fold content could be rendered with the full HTML response.
Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.