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 (560.4KiB reduction).
Compressing https://tracker.metricool.com/resources/be.js could save 111B (30% 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://tracker.metricool.com/resources/be.js (expiration not specified)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/1639864876076661?v=2.8.35&r=stable (20 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
In our test, your server responded in 0.55 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 (25.6KiB reduction).
Minify HTML for the following resources to reduce their size by https://developers.google.com/speed/docs/insights/MinifyResources (18.2KiB reduction).
Your page has 1 blocking CSS resources. This causes a delay in rendering your page.
Approximately 35% 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 (3.7MiB reduction).
Compressing https://scontent.cdninstagram.com/vp/e522c728b3f7ef1aa3f92c3589cb81cb/5C9A4BBC/t51.2885-15/e35/c180.0.720.720/s150x150/46366866_214261866142632_8828175317151042009_n.jpg?_nc_ht=scontent.cdninstagram.com could save 964B (20% reduction).
Compressing https://scontent.cdninstagram.com/vp/dafc902130c2a148273b7be07e78ebff/5CA528CE/t51.2885-15/e35/c179.0.721.721/s150x150/43984718_335058160629717_8436409677357752168_n.jpg?_nc_ht=scontent.cdninstagram.com could save 921B (15% reduction).
Compressing https://scontent.cdninstagram.com/vp/f4b4ee41b51a15ac00263678522c49f0/5CD84A91/t51.2885-15/e35/c179.0.721.721/s150x150/43984967_1911234922285430_1400183120085739603_n.jpg?_nc_ht=scontent.cdninstagram.com could save 921B (15% reduction).
Compressing https://scontent.cdninstagram.com/vp/fe3a2f6d51c265293717b8eec849f7f7/5C99B861/t51.2885-15/e35/c179.0.721.721/s150x150/43568277_1730219867107513_6360143413948524833_n.jpg?_nc_ht=scontent.cdninstagram.com could save 911B (22% reduction).
Compressing https://scontent.cdninstagram.com/vp/4e64e6dda20d9e0617fabc3fcaa2c074/5CB7AAC9/t51.2885-15/e35/c179.0.721.721a/s150x150/43338290_2023774071253380_8900466168457460636_n.jpg?_nc_ht=scontent.cdninstagram.com could save 835B (18% reduction).
Compressing https://scontent.cdninstagram.com/vp/cdfd04b98dcca41e0ca8c464cb7117e4/5CA27247/t51.2885-15/e35/c179.0.721.721/s150x150/43985610_295673681272627_734668139770603518_n.jpg?_nc_ht=scontent.cdninstagram.com could save 832B (12% reduction).
Compressing https://scontent.cdninstagram.com/vp/b977ca258a7c64045eea9c464c2a8fbb/5CA041B1/t51.2885-15/e35/c179.0.721.721/s150x150/46350193_2167402596857319_1961181898686974858_n.jpg?_nc_ht=scontent.cdninstagram.com could save 812B (12% 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 64% of the final above-the-fold content could be rendered with the full HTML response.
Click to see the screenshot with only the HTML response: snapshot:24