Fix guides · Performance

How to fix a slow server response, redirects and missing compression

Everything waits for the first response from your server. How to cut redirects, speed up the server and turn on compression on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.

Time to fix
30 minutes – half a day
Skill needed
Developer
Who notices
Every visitor, on every page

Why it matters

Nothing on the page can start until the browser receives the HTML itself. Chrome flags this request when it was redirected, when the server took more than 600 ms to answer, or when the page wasn't compressed.

Each redirect (for example http:// → https:// → www.) is another full round trip before anything loads.

A slow server usually means the page is being built from scratch on every visit: no page caching, slow database queries, too many plugins or a busy shared host.

“The initial document request for the page is the most important because all network requests and page content depend on it.”

Chrome: Document request latency insight

Before you start

  • Check which of the three your report flags: redirects, server time, or compression. They have different fixes.
  • Redirects: make sure links, ads and your Search Console property use the final address (the right protocol, www or not, and trailing slash).
  • Server time varies with traffic and location. Re-test a few times before changing hosts.

Fix it on your platform

Shopify

  1. Shopify's servers, CDN and compression are managed for you. What you control is how long your theme's Liquid code takes to render, which is most of the server time on a Shopify store.
  2. Use the Shopify Theme Inspector for Chrome to find the slowest parts of your theme. Nested loops and metafield lookups inside loops are the usual culprits on large catalogs.
  3. Check that links and ads point to your primary domain, so visitors aren't redirected from another one.

WordPress

  1. Turn on full-page caching with a caching plugin or your host's built-in cache. Cached pages skip PHP and the database entirely.
  2. Deactivate plugins you don't need, and consider a lighter theme (ideally a block theme).
  3. If the server is still slow, consider moving to managed WordPress hosting.
  4. Compression is a web server setting. Most hosts enable it; if your report says the page isn't compressed, ask your host to enable gzip or Brotli.

Webflow

  1. Webflow's hosting, CDN and compression are managed for you. What you control is redirects.
  2. In Site settings → Publishing → 301 redirects, remove redirects you no longer need and use wildcard rules where possible. Webflow suggests staying under 1,000.
  3. Make sure links on your own site point straight to the final address, not to an old one that redirects.

Wix

  1. Wix's servers and compression are managed for you. Wix caches pages on its CDN automatically.
  2. Keep caching on: under Pages & Menu, a page's caching setting should only be turned off for pages that show live data.
  3. Make sure links point straight to the final address, not to an old one that redirects.

Squarespace

  1. Squarespace's servers and compression are managed for you. What you control is redirects.
  2. Too many redirects can slow pages down. Review them in the URL Mappings panel and remove ones you no longer need.

Next.js

  1. Make pages static or cached wherever their data allows, so the server isn't rendering on every request.
  2. Next.js compresses responses with gzip by default when you run it with next start. Hosting platforms usually compress at their CDN instead.
  3. Define permanent redirects in next.config, so they're answered before any page renders, and link straight to final URLs.

Any other site

  1. Cache pages at the server or a CDN so they aren't rebuilt for every visitor.
  2. Turn on Brotli or gzip compression for HTML, CSS, JavaScript and SVG in your web server.
  3. Redirect old addresses in one step, straight to the final URL.
nginx
gzip on;
gzip_types text/css application/javascript application/json image/svg+xml;

# One hop: http and non-www go straight to the final address
server {
  listen 80;
  server_name example.com www.example.com;
  return 301 https://www.example.com$request_uri;
}

“Over the past five years, the percentage of mobile web pages with good TTFB has remained stable, from 41% in 2021 to 42% in 2024.”

HTTP Archive Web Almanac 2024, Performance

Check that it's fixed

  • Re-run your StudioLNC audit: the document request should show no redirects, a server time under 600 ms, and compression.
  • In Chrome DevTools → Network, click the page request and check the Content-Encoding response header (br, gzip or zstd).

Find every issue like this on your site

Free audit of performance, accessibility, SEO and security, with fixes for your platform.