Your page has no redirects. Learn more about avoiding landing page redirects.
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 https://developers.google.com/speed/docs/insights/EnableCompression (935B reduction).
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.
Leverage browser caching for the following cacheable resources:
https://www.google-analytics.com/analytics.js (2 hours)
In our test, your server responded in 1.8 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by https://developers.google.com/speed/docs/insights/MinifyResources (14.7KiB reduction).
Your HTML is minified. Learn more about minifying HTML.
Your page has 18 blocking script resources and 17 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Optimize CSS Delivery of the following:
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by https://developers.google.com/speed/docs/insights/OptimizeImages (38.7KiB reduction).
Compressing https://scontent.flux1-1.fna.fbcdn.net/v/t1.0-0/q89/p130x130/24899743_1109403402530680_593930707115685451_n.jpg?_nc_cat=0&oh=837ec804d12ccbc4936d7d56b1cf63f6&oe=5B760CE2 could save 2.2KiB (15% reduction).
Compressing https://scontent.flux1-1.fna.fbcdn.net/v/t1.0-1/c22.214.171.124/p50x50/20840949_1449886228432882_4013635127075050940_n.jpg?_nc_cat=0&oh=bab8094af34ab229b196812136f72213&oe=5B35E557 could save 443B (23% reduction).
Compressing https://scontent.flux1-1.fna.fbcdn.net/v/t1.0-1/p50x50/14199248_136417630144325_567218911571380673_n.jpg?_nc_cat=0&oh=79880af365eb477bbb29f688169c7286&oe=5B28DE6B could save 441B (29% reduction).
Compressing https://scontent.flux1-1.fna.fbcdn.net/v/t1.0-1/p50x50/13876582_319535151719493_2634553788075997916_n.jpg?_nc_cat=0&oh=961d7efda9ca1e9ccb5be72b1c5e5491&oe=5B40ADD2 could save 431B (25% reduction).
Compressing https://scontent.flux1-1.fna.fbcdn.net/v/t1.0-1/p50x50/28871118_1997338380520108_8772093169900474223_n.jpg?_nc_cat=0&oh=c002e06bcb464a336f6057c055bb33c9&oe=5B3DC3F9 could save 430B (26% reduction).
Compressing https://scontent.flux1-1.fna.fbcdn.net/v/t1.0-1/p50x50/18118971_10212728219669585_7184112818087408933_n.jpg?_nc_cat=0&oh=01700d6ee04b45b16a856034d048c205&oe=5B3353DB could save 426B (33% reduction).
Compressing https://scontent.flux1-1.fna.fbcdn.net/v/t1.0-1/p50x50/12191026_634635450007480_4344499840732000286_n.jpg?oh=cbbc734dc188d7951151936fad788bca&oe=5B387B09 could save 420B (37% reduction).
Compressing https://scontent.flux1-1.fna.fbcdn.net/v/t1.0-1/p50x50/21686128_10211805922756756_226552004448196680_n.jpg?_nc_cat=0&oh=206a99b14ea40d448606d6301e2dc0a2&oe=5B346BBC could save 415B (23% reduction).
Compressing https://scontent.flux1-1.fna.fbcdn.net/v/t1.0-1/p50x50/26229900_1863386623951883_8238693659421921006_n.jpg?_nc_cat=0&oh=10b7a6f7400ade04692d0eeb372b2cc4&oe=5B365552 could save 404B (34% reduction).
Compressing https://scontent.flux1-1.fna.fbcdn.net/v/t1.0-1/c0.0.50.50/p50x50/28168111_938801606295139_2479170612808659846_n.jpg?_nc_cat=0&oh=057615aae688013f92722f2eeb713fe0&oe=5B730ADE could save 385B (18% reduction).
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 66% of the final above-the-fold content could be rendered with the full HTML response snapshot:36.