Your page has no redirects. Learn more about avoiding landing page redirects.
You have compression enabled. Learn more about enabling compression.
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.googletagmanager.com/gtm.js?id=GTM-KDNG3MW (15 minutes)
https://connect.facebook.net/signals/config/519597331918753?v=2.9.5&r=stable (20 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://cdn.iubenda.com/cs/iubenda_cs.js (3 hours)
In our test, your server responded in 15.6 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.
Your CSS is minified. Learn more about minifying CSS.
Your HTML is minified. Learn more about minifying HTML.
Your page has 1 blocking script resources and 3 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 (16KiB reduction).
Compressing and resizing https://www.ristorantecolapasta.it/wp-content/uploads/2016/06/colapasta.gif could save 7.6KiB (60% reduction).
Compressing and resizing https://www.ristorantecolapasta.it/wp-content/uploads/2017/12/tripadvisor.png could save 7.1KiB (89% reduction).
Compressing and resizing https://www.ristorantecolapasta.it/wp-content/uploads/2017/12/facebook.png could save 1.4KiB (85% 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 52% 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:4