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 (30KiB reduction).
Compressing https://fronteando.net/ could save 30KiB (78% 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://m.addthisedge.com/live/boost/ra-5a2ead7772834ca4/_ate.track.config_resp (51 seconds)
https://rules.quantcount.com/rules-p-4_WAtYsMD0gBS.js (5 minutes)
https://s7.addthis.com/js/300/addthis_widget.js (10 minutes)
https://ssl.google-analytics.com/ga.js (2 hours)
Your server responded quickly. Learn more about server response time optimization.
Your CSS is minified. Learn more about minifying CSS.
Minify HTML for the following resources to reduce their size by https://developers.google.com/speed/docs/insights/MinifyResources (4.5KiB reduction).
Minifying https://fronteando.net/ could save 4.5KiB (12% reduction).
You have no render-blocking resources. Learn more about removing render-blocking resources.
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 (32.4KiB reduction).
Compressing https://fronteando.net/img-h/cover/?id=298670&d=2 could save 28.5KiB (73% reduction).
Compressing https://fronteando.net/img-h/fronteando.png could save 2.9KiB (52% reduction).
Compressing https://fronteando.net/img-h/cover/?id=833746&d=2 could save 1.1KiB (20% reduction).
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.