# How to Cut Your Website’s Response Time Without Touching the Code Source: https://baqueiro.es/en/ingenieria-sin-atajos/speed-up-website-without-touching-code/ Published: 2026-04-10T03:07:13+00:00 Updated: 2026-04-10T03:07:13+00:00 Author: Baqueiro Desarrollo Web Language: en-US Usage: Attribution required: quoting allowed with a visible link back --- **TL;DR** - Many website performance problems come from configuration, not badly written code. - Changes to hosting, CDN, image compression and caching can dramatically cut load times without modifying the code. - Auditing these first saves time and money before you invest in optimization development. Picture a very typical case: a client asks us to “optimize their website because it’s slow.” We ask for access to diagnose it and, in the meantime, review their current setup. It turns out they’re on an €8/month shared hosting plan with 100 sites on the same server, no CDN, no image compression and a WordPress install loading 47 plugins. The recommendation would be to switch hosting (not optimize code), set up Cloudflare (not optimize code) and compress the images (not optimize code). In a scenario like that, the site can realistically go from loading in 6 seconds to 1.8 seconds. Total cost: about €30/month more for hosting plus an afternoon of configuration. The code isn’t perfect, but it isn’t the bottleneck. Many performance problems are solved at the infrastructure layer, not the application layer. This is the checklist we use before touching a single line of code. ## Infrastructure: hosting matters more than you think Hosting is the ground your website runs on. If it’s weak, everything else suffers. **Assess your current hosting.** - Are you on shared hosting with hundreds of sites? Performance is unpredictable: a neighbor with heavy traffic affects your speed. - How many resources are allocated to your site? RAM, CPU, disk IOPS. - Where is the server physically located? If your audience is in Spain and your server is in Arizona, there’s built-in latency. **Hosting upgrades that don’t require code:** - VPS or dedicated vs. shared: guaranteed resources. - Up-to-date PHP: PHP 8.x is significantly faster than 7.x or (horror) 5.x. Many hosts let you change the PHP version from the control panel. - A server closer to your audience: if 90% of your traffic comes from Spain, a server in Spain or France beats one in the United States. Switching hosting is the optimization with the biggest potential impact, and it requires zero lines of code. ## CDN: distribute to accelerate A CDN (Content Delivery Network) serves your static files (images, CSS, JavaScript) from servers close to the user instead of from your main server. **Setup without code:** Cloudflare has a free plan that includes a global CDN. Setup: change your domain’s DNS to point to Cloudflare (from your domain registrar). You don’t touch your website, just the DNS settings. The impact is usually most noticeable for users who are geographically far from your server. For users close to it, the benefit is smaller but still there, thanks to cache optimization. Other Cloudflare benefits that don’t involve code: automatic compression (Brotli), image optimization (Polish, on paid plans) and a firewall that blocks malicious traffic before it reaches your server. ## Images: the invisible performance villain Images usually account for most of a typical web page’s weight. Optimizing them has an outsized impact. **Optimization without touching code:** - **Bulk compression.** Tools like TinyPNG, Squoosh or ImageOptim can shrink images considerably, often by more than half, with no visible loss of quality. Replacing the originals with the compressed versions is just a matter of uploading new files. - **Modern formats.** Convert JPG and PNG to WebP (with tools like Squoosh or WordPress plugins that do it automatically). A WebP file is usually noticeably smaller than the equivalent JPEG. - **Correct dimensions.** Uploading a 4000x3000px image to display it at 400x300px wastes bandwidth. Resizing before uploading (with any image editor) eliminates that waste. - **Native lazy loading.** Modern browsers support lazy loading images without extra JavaScript: you just add the loading=”lazy” attribute to the image tag. If your CMS lets you edit HTML, it’s a trivial change. If not, WordPress plugins like WP Rocket add it with no further setup. ## Caching: avoid repeating work A cache stores copies of your content so it can be served without regenerating it every time. It’s the most effective optimization there is. **Cache levels you can configure without code:** **1. Page cache.** Plugins like WP Rocket, W3 Total Cache or LiteSpeed Cache generate static HTML versions of your pages. The first visit builds the cache; later visits get the static file, skipping PHP processing. Typical setup: install the plugin, enable page caching and exclude dynamic pages (cart, my account) if it’s an online store. **2. Browser cache.** Tells the visitor’s browser to store static files (CSS, images) locally for days or weeks so they aren’t downloaded again on every page. Configurable via .htaccess or caching plugins. **3. Object and query cache.** Stores the results of frequent database queries in memory (Redis or Memcached). Some managed hosts offer it with one click in the control panel. A well-configured cache can bring response times down from seconds to milliseconds. ## Compression: fewer bytes, more speed Serving compressed files greatly reduces transfer size for HTML, CSS and JavaScript. **Without touching code:** - Gzip or Brotli enabled on the server. Most modern hosts have it on by default. You can check with online tools like [Gift of Speed](https://www.giftofspeed.com/gzip-test/). - Cloudflare (mentioned earlier) compresses automatically if you have it enabled. - WordPress caching plugins usually include compression options you can turn on with a checkbox. ## Database: preventive cleanup WordPress in particular accumulates junk in the database that slows down queries. **Cleanup without code:** - Check your caching plugins: WP Rocket, LiteSpeed Cache and similar tools include “database cleanup” options that remove post revisions, expired transients and spam comments. - Limit post revisions: add define(‘WP_POST_REVISIONS’, 3); to wp-config.php (yes, it’s a configuration file, not application code). This prevents future buildup. - Anti-spam plugins that cut down on junk comments (Akismet, Antispam Bee). ## Audit before you optimize Before making any change, measure. If you don’t measure, you won’t know whether it worked. Free diagnostic tools: - **Google PageSpeed Insights:** flags specific problems and gives prioritized suggestions. - **GTmetrix:** speed history and waterfall analysis. - **WebPageTest:** tests from multiple locations and devices. - **Query Monitor (WordPress):** which queries are slow and which plugins add load. These tools will tell you where the bottleneck is. Sometimes it’s image number 3 weighing 3 MB. Sometimes it’s a plugin running 200 database queries. Sometimes it’s the server taking 2 seconds to respond because it’s overloaded. ## When you do need to touch the code After all these infrastructure optimizations, there are cases where the code really does need attention: - The theme has render-blocking JavaScript that delays rendering. - Plugins run inefficient database queries. - Custom code has slow algorithms or N+1 queries. - Unused CSS is blocking rendering. But these should be the second phase, not the first. It’s frustrating to pay for code optimization when a hosting change would have solved most of the problem. ## Frequently asked questions **How much can performance improve without touching code?** It depends on where you start, but big improvements are common with just decent hosting, a CDN and optimized images. Going from 6 seconds to 2 is realistic without touching code. **Do I need to be technical to make these changes?** Changing DNS for Cloudflare requires understanding basic DNS concepts. Optimizing images requires no technical knowledge. Switching hosts usually means migrating the site, which may require technical help. It varies. **How much does it cost to implement these optimizations?** Free Cloudflare: €0. Image optimization: €0 (free tools) or your time. Better hosting: between €20 and €100 a month, depending on traffic. Premium caching plugins: between €50 and €100 a year. Far less than paying for code optimization work. **What if my site is still slow after all this?** Then yes, you probably need code optimization. But at least you’ll know for sure, and the code optimization will be more effective because it starts from a solid foundation. ## Conclusion Website performance optimization has a hierarchy. Starting with the code when the infrastructure is weak is building on sand. The good news is that many of the most impactful improvements don’t need a developer: they need the right configuration. If your website is slow, go through this checklist before calling a developer. You’ll probably find significant improvements you can make yourself or with minimal help. And if, after optimizing the infrastructure, you need someone to review the code, [we can help](https://baqueiro.es/en/contact/). But we’d rather start with what has the biggest impact at the lowest cost.