Perché il tuo sito web è lento (e come rimediare oggi)

Website speed is not a vanity metric — it is a direct revenue driver. Google's own research shows that a one-second delay in mobile page load time reduces conversions by up to 20%. Amazon famously calculated that every 100 milliseconds of latency cost them 1% in sales. For a business generating €500,000 annually through its website, a half-second speed improvement could be worth €50,000 or more per year. Speed is money, and every slow page is a leak in your revenue pipeline.

Beyond conversions, page speed directly impacts your search engine rankings. Google has used page speed as a ranking factor since 2010, and Core Web Vitals, a set of user experience metrics that include Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Interaction to Next Paint (INP), became a formal ranking signal in 2021. Sites that fail these benchmarks are actively penalized in search results, losing visibility to faster competitors regardless of content quality.

At GRADAX, we audit website performance as part of every client engagement. The findings are remarkably consistent: most websites are significantly slower than they need to be, and the causes are almost always fixable. Unoptimized images, bloated JavaScript bundles, poor hosting, and missing caching account for over 80% of the performance problems we diagnose. What follows is a systematic guide to identifying and eliminating each of these bottlenecks.

Before optimizing anything, establish a reliable baseline. Google PageSpeed Insights is the most accessible starting point : enter your URL and receive a detailed report covering Core Web Vitals, performance scores, and specific optimization recommendations. Run it on both your homepage and your most-visited landing pages, because performance varies significantly across different page types. A lightweight homepage might score 95 while a product listing page with dozens of images scores 45.

For deeper analysis, use Google Lighthouse in Chrome DevTools with network throttling enabled. Set the connection to "Slow 4G" and CPU to "4x slowdown" to simulate conditions that a significant portion of your visitors experience on mobile devices. The performance metrics under these throttled conditions reveal bottlenecks that are invisible on your high-speed development machine. Pay special attention to Time to First Byte (TTFB), which measures server response time and is often the limiting factor for sites on shared hosting.

WebPageTest.org provides the most comprehensive analysis, including waterfall charts that show exactly when each resource loads and how resources block each other. Run tests from multiple locations and on different connection speeds to understand how your site performs for visitors worldwide. The filmstrip view is particularly valuable, it shows a frame-by-frame progression of your page rendering, making it immediately obvious when large resources cause visible delays in the loading experience.

Images are the single largest contributor to page weight on the average website, accounting for roughly 50% of total bytes transferred. An unoptimized hero image can easily weigh 3-5 MB, which alone exceeds Google's recommended total page budget of 1.5 MB. The fix is straightforward: convert images to modern formats, compress them appropriately, size them correctly, and load them lazily.

WebP and AVIF are the modern image formats you should be using. WebP delivers 25-35% smaller file sizes than JPEG at equivalent visual quality and is supported by every major browser. AVIF pushes compression even further, 50-60% smaller than JPEG, but encoding is slower and browser support, while growing, is not yet universal. We serve AVIF where supported and fall back to WebP, using the HTML picture element or server-side content negotiation to handle format selection automatically.

Responsive images are equally important. Serving a 2400-pixel-wide hero image to a mobile device with a 375-pixel viewport wastes bandwidth and processing time. Use the srcset attribute to provide multiple image sizes and let the browser choose the appropriate one. For most websites, providing images at 640px, 1024px, 1440px, and 1920px widths covers the full range of viewport sizes. Combined with lazy loading (the native loading="lazy" attribute), images below the fold are not downloaded until the user scrolls near them, dramatically improving initial load time.

Your hosting environment sets a performance floor that no amount of front-end optimization can overcome. If your server takes 800 milliseconds to generate an HTML response, your page cannot load in under one second regardless of how well you optimize images and scripts. Time to First Byte (TTFB) should be under 200 milliseconds for most pages. If yours consistently exceeds 400 milliseconds, your hosting is the bottleneck.

Shared hosting is the most common culprit. On a shared server, your website competes with dozens or hundreds of other sites for CPU, memory, and I/O bandwidth. When a neighboring site experiences a traffic spike or runs a resource-intensive script, your performance degrades. Upgrading to a VPS or dedicated cloud server eliminates this contention by guaranteeing your resource allocation. For WordPress sites specifically, a managed WordPress host that includes server-level caching, PHP opcode caching, and database query optimization can reduce TTFB by 60-80% compared to generic shared hosting.

Server location also matters more than most people realize. Physics imposes a minimum latency based on the speed of light through fiber optic cable, roughly 1 millisecond per 100 kilometers. A server in the United States responding to a user in Germany adds at minimum 60-80 milliseconds of round-trip latency before any processing begins. If the majority of your audience is in a specific region, host your server in that region. For global audiences, a CDN brings your content closer to users regardless of server location.

Modern websites ship enormous amounts of JavaScript and CSS, much of which the user's browser never needs. The median website in 2025 transfers over 500 KB of JavaScript, and pages built with heavy frameworks or loaded with third-party scripts frequently exceed 2 MB. Every kilobyte of JavaScript must be downloaded, parsed, compiled, and executed before the page becomes fully interactive. This is the primary reason why a page can appear visually complete but remain unresponsive to clicks and scrolls for several seconds.

Audit your JavaScript bundles with Chrome DevTools' Coverage tab, which shows the percentage of downloaded code that is actually executed during page load. It is common to find that 50-70% of JavaScript is unused on any given page. Tree-shaking, code splitting, and dynamic imports can dramatically reduce initial bundle sizes. If you are using a framework like Next.js or React, ensure you are leveraging built-in code splitting that loads only the JavaScript needed for the current page rather than shipping the entire application upfront.

Third-party scripts are often the worst offenders. Analytics, chat widgets, social media embeds, A/B testing tools, advertising pixels — each adds its own JavaScript payload, network requests, and processing overhead. We have seen client sites loading twelve or more third-party scripts totaling over 1.5 MB. Audit every third-party script for necessity and impact. Load non-critical scripts asynchronously with the defer attribute, and consider removing any that do not deliver measurable business value. A technical SEO audit will reveal exactly which scripts are dragging your Core Web Vitals below passing thresholds.

Caching is the most effective performance optimization you can implement because it eliminates work entirely. Instead of regenerating a page or re-downloading a resource on every request, a cache serves a stored copy in a fraction of the time. Effective caching operates at multiple layers: browser caching, server-side caching, application-level caching, and CDN caching. Each layer reduces the load on the next, and together they can reduce server resource consumption by 90% or more.

Browser caching is controlled through HTTP headers. Set Cache-Control headers with appropriate max-age values for each resource type: static assets like images, fonts, and versioned CSS/JS files should cache for one year (max-age=31536000) with immutable and public directives. HTML pages should cache for shorter periods or not at all, depending on how frequently content changes. Service workers add another layer by caching resources at the application level, enabling instant page loads for returning visitors and even offline functionality.

Server-side caching stores the fully rendered HTML output of a page so that subsequent requests skip the entire rendering pipeline. For WordPress, plugins like WP Super Cache or W3 Total Cache generate static HTML files that Apache or Nginx serves directly without invoking PHP at all. For custom applications, Redis or Memcached can cache database queries, API responses, and computed results. The key principle is to cache at the highest level possible, a cached HTML page is faster than a cached database query, which is faster than an uncached database query.

A Content Delivery Network distributes your website's static assets across a global network of edge servers, so that users download resources from a server geographically close to them rather than from your origin server, which may be thousands of kilometers away. Implementing a CDN is one of the highest-impact, lowest-effort performance improvements available, and services like Cloudflare offer generous free tiers that cover most small to mid-sized websites.

The performance gains from a CDN are most dramatic for users far from your origin server. A website hosted in Frankfurt serving an image to a user in Tokyo sees the round-trip latency drop from approximately 250 milliseconds to under 30 milliseconds when that image is cached on a Tokyo edge node. Multiply that improvement across every image, stylesheet, font, and script on the page, and the cumulative effect is transformative. We have measured CDN implementation reducing total page load time by 40-60% for international visitors.

Modern CDNs go beyond simple static asset caching. Cloudflare, Fastly, and AWS CloudFront offer edge computing capabilities that can cache entire HTML pages, perform A/B testing at the edge, optimize images on the fly, and even run serverless functions at edge locations. For WordPress sites, Cloudflare's APO (Automatic Platform Optimization) caches entire pages at the edge, achieving TTFB under 50 milliseconds globally, performance that would be impossible to achieve with origin-only hosting regardless of how powerful your server is.

If you want immediate results without a deep technical dive, here are five changes you can implement in under an hour. First, install and configure a caching plugin if you are on WordPress . WP Super Cache is free and takes five minutes to set up. Second, run your images through a bulk optimizer like ShortPixel or Imagify, which can reduce image sizes by 60-80% with no visible quality loss. Third, enable GZIP or Brotli compression on your server, which reduces text-based resource sizes by 70-90% during transfer.

Fourth, defer non-critical JavaScript by adding the defer attribute to script tags or moving them to the bottom of your HTML body. This prevents JavaScript from blocking the initial page render and can improve your LCP score by several hundred milliseconds. Fifth, enable a CDN . Cloudflare's free plan takes ten minutes to set up and immediately improves load times for every visitor not located near your server. These five changes alone can take a website from a PageSpeed score of 40 to 75 or higher.

For improvements beyond these quick wins, a comprehensive performance audit is the most cost-effective investment you can make. At GRADAX, we analyze every layer of the stack, hosting infrastructure, server configuration, application architecture, front-end assets, and third-party dependencies, and deliver a prioritized roadmap of optimizations ranked by impact and implementation effort. Most clients see their page load times cut in half within the first week of implementing our recommendations. Get in touch to schedule a performance audit for your website.