Multi-level Caching: Browser → CDN → Varnish → Redis → DB

We've worked on projects where every page request turned into dozens of SQL queries. Even a simple blog crawled. After implementing multi-level caching, response time dropped from 2000 ms to 80 ms, and database load decreased by 95%. Clients significantly reduce infrastructure costs after such optimization. Here's how to build this system.

Multi-level caching is a sequence of storage layers for responses. Each layer serves a request without passing it further. The closer to the user a cache hit occurs, the faster the response. A proper strategy reduces load on the database and application server, and improves Core Web Vitals.

Why One Level Is Not Enough?

Browser cache saves traffic but doesn't help on first visit. CDN accelerates static delivery, but dynamic pages need a faster layer. Varnish is a powerful reverse proxy but can't store complex data structures. Redis solves this but requires RAM. The combination of these tools gives maximum effect: a typical site after setup gets hit rate >80% on CDN and >70% on Varnish.

Recommended TTLs for Different Content Types

These TTLs should be adjusted based on content change frequency. For a news portal, HTML is better cached for 2 minutes; for a corporate site, one hour. We always run load testing to ensure hit rate meets target values.

How to Configure Browser Caching?

# nginx: headers for browser cache
location ~* \.(jpg|jpeg|png|gif|ico|css|js|woff2)$ {
    expires 1y;
    add_header Cache-Control "public, immutable";
}

location ~* \.html$ {
    add_header Cache-Control "public, max-age=0, s-maxage=300";
    add_header Vary "Accept-Encoding, Accept-Language";
}

The immutable directive tells the browser not to revalidate the file — it's guaranteed not to change. This gives instant loading on repeat visits.

How to Connect a CDN?

# cloudflare page rules
- pattern: "*.company.com/assets/*"
  settings:
    cache_level: cache_everything
    edge_cache_ttl: 2592000  # 30 days
    browser_cache_ttl: 31536000  # 1 year

CDN offloads the origin and reduces TTFB for geographically distant users.

Varnish: Fine Tuning

vcl 4.1;
backend default {
    .host = "app-server";
    .port = "8080";
}
sub vcl_recv {
    if (req.http.Authorization || req.http.Cookie ~ "session") { return (pass); }
    if (req.method != "GET" && req.method != "HEAD") { return (pass); }
    unset req.http.Cookie;
    return (hash);
}
sub vcl_backend_response {
    if (beresp.status == 200 || beresp.status == 301) {
        if (beresp.http.Content-Type ~ "text/html") { set beresp.ttl = 5m; }
        else if (beresp.http.Content-Type ~ "application/json") { set beresp.ttl = 1m; }
        unset beresp.http.Set-Cookie;
    }
    set beresp.grace = 1h;
}
sub vcl_deliver {
    if (obj.hits > 0) { set resp.http.X-Cache = "HIT"; }
    else { set resp.http.X-Cache = "MISS"; }
}

According to the Varnish Cache documentation, the grace period allows serving stale cache when the backend is unavailable, improving availability. The hash key can be customized to separate cache by language or device.

How to Solve Cache Invalidation?

Without proper invalidation, users see stale data. We design a unified system: on data changes, HTTP PURGE is sent to Varnish, Redis keys are deleted, and CDN tags are purged. Example in Python:

def on_product_updated(product_id):
    redis.delete(f"product:{product_id}")
    requests.request('PURGE', f"http://varnish:6081/products/{product_id}")
    # Cloudflare purge by tag
    requests.post(f"https://api.cloudflare.com/client/v4/zones/{zone_id}/purge_cache",
        headers={"Authorization": f"Bearer {token}"},
        json={"tags": [f"product-{product_id}"]})

A common mistake is setting too long TTLs without an invalidation mechanism. We recommend using tags on CDN and PURGE on Varnish to ensure data freshness. In some scenarios, we use Edge Functions for instant invalidation at the network edge.

Monitoring Hit Rate by Level

We use Prometheus metrics: varnish_main_cache_hit / (varnish_main_cache_hit + varnish_main_cache_miss), redis_keyspace_hits_total / (redis_keyspace_hits_total + redis_keyspace_misses_total). Target values are listed in the table above. Regular monitoring allows timely TTL adjustments and identifies invalidation issues.

What's Included in the Work?

1. Audit of current caching architecture — analyzing nginx logs, Varnish configs, Redis parameters, and CDN structure.
2. Browser Cache setup via nginx or .htaccess.
3. CDN (Cloudflare, CloudFront) connection with caching rules.
4. Varnish (4.1+) installation and configuration with grace and hash rules.
5. Redis (cluster, persistence, eviction policy) configuration.
6. Creation of a unified invalidation system with PURGE and API.
7. Load testing and TTL optimization.
8. Documentation and team training.

Timeline and Cost

Setting up the full stack takes 4 to 7 working days. Cost is calculated individually based on project complexity. Clients typically recoup the investment in 2–3 months through reduced server costs and increased conversion.

Common Mistake: Incorrect TTL Settings

Many set identical TTLs for all content types. This leads either to over-caching of dynamic data or too frequent invalidation of static files. We choose TTLs based on content update frequency: static — one year, HTML — 5 minutes, JSON API — 1 minute. After configuration, we check hit rate and adjust as needed.

Order a cache audit today — we'll identify bottlenecks and propose the optimal strategy. Get a consultation on multi-level caching setup for your project.

Why are Core Web Vitals critical for technical SEO?

PageSpeed 34/100 on mobile. Search Console shows red on all category pages. A competitor with an older site outranks you despite weaker content. Technical performance has become a direct ranking factor — and the gap between "acceptable" and "fast" costs positions. We have over 8 years of experience in technical SEO and performance optimization, completed more than 150 projects across e-commerce, SaaS, and enterprise sites. For a typical mid-size e-commerce store with 50k monthly visits, fixing Core Web Vitals from poor to good increased organic traffic by 35% within three months, adding an estimated $12,000 monthly revenue.

Core Web Vitals: what really affects rankings

Google uses three metrics as ranking signals (Page Experience): Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), Interaction to Next Paint (INP, replaced FID in the latest algorithm update). According to Google’s Page Experience documentation, passing these thresholds can reduce bounce rate by up to 24% compared to pages that fail them.

LCP: why 8 seconds is not an image problem

LCP measures rendering time of the largest visible element. Good <2.5s, poor >4s.

Real case: online clothing store, LCP 7.8s on mobile. Hero image 4.2MB JPEG without srcset, loaded via CSS background-image (not <img>). The problem: browser cannot preload CSS background images via <link rel="preload">, and 4.2MB on mobile connection is slow.

Solution:

1. Move to <img> with fetchpriority="high" and loading="eager"
2. Convert to WebP, add srcset: 800w for mobile, 1400w for desktop
3. <link rel="preload" as="image" href="hero-800.webp" media="(max-width: 768px)"> in <head>
4. Remove render-blocking scripts above hero with defer

Result: LCP 7.8s → 1.9s without changing hosting or CDN. That's 4x faster — a competitive advantage in search ranking.

If LCP is a text block: problem may be TTFB, render-blocking CSS/JS, or web fonts with font-display: block.

CLS: what causes layout shifts and how to stop them

CLS measures cumulative layout shift. Good <0.1, poor >0.25. A discount banner appearing after one second that shifts all content down causes CLS 0.35.

Sources:

• Images without dimensions. <img src="photo.jpg"> without width/height — browser doesn't reserve space. Fix: explicit width/height or aspect-ratio in CSS.
• Ad blocks and widgets — Google Ads, chat, cookie consent. Reserve space via min-height or load before main content.
• Web fonts. font-display: swap with size-adjust minimizes CLS.
• Dynamic content — add skeleton placeholder with dimensions.

INP: why interface freezes for 500ms

INP measures response delay to any user interaction. Good <200ms, poor >500ms. INP 680ms means user presses filter button and waits half a second.

Main cause: blocked main thread. A 2.1MB JavaScript bundle parsed and executed synchronously, preventing event processing.

Diagnosis: Chrome DevTools → Performance → interact → find Long Tasks (>50ms). Typical culprits:

• Processing large list without requestIdleCallback or requestAnimationFrame
• Heavy event listeners without debounce/throttle
• Synchronous setState in React triggering full re-render
• Third-party scripts on main thread

Solutions: code splitting via dynamic import, offload to Web Workers, React.memo + useMemo, Scheduler API.

How do structured data and Schema.org improve search visibility?

Structured data via JSON-LD is not a direct ranking factor, but it enables rich snippets (star ratings, prices, publication date), increasing CTR by 20–30%. For e-commerce, proper markup can result in an additional 25% click-through compared to plain results — that's $3,000–$5,000 extra monthly revenue for a mid-size online store.

Markup types by scenario:

• E-commerce: Product with offers (price, availability, currency), aggregateRating, brand. BreadcrumbList, ItemList.
• Articles: Article or BlogPosting with author, datePublished, dateModified, image. Organization and WebSite.
• Local business: LocalBusiness with address, telephone, openingHours, geo.
• FAQ: FAQPage with mainEntity — questions appear as expandable block.

Validation: Google Rich Results Test, Schema Markup Validator. Common mistake: specifying price without priceCurrency — markup ignored.

How to conduct a technical SEO audit

Crawlability. robots.txt blocks necessary pages or doesn't block service pages. Canonical URLs incorrectly set — duplicates with UTM parameters. Sitemap contains noindex pages. Tools like Screaming Frog or Sitebulb show this in an hour.

Core Web Vitals at scale. Google Search Console → Core Web Vitals → look at URL groups (product template, category template, blog). Problem is usually systemic.

JavaScript SEO. Google renders JS with delay. For critical content, SSR or SSG are mandatory. Check via Search Console → Inspect URL → View Crawled Page.

Internal linking. Orphan pages lose PageRank. Broken links (404) are a quality signal.

Common mistakes when implementing Schema.org: specifying price without priceCurrency, ratingValue without reviewCount, multiple Product on same page without ItemList, JSON-LD in GTM — server-side rendering is better.

What does the optimization process look like?

What deliverables do you receive?

• Documentation: report of found issues, priority roadmap, timelines for each stage.
• Access: setup monitoring (SpeedCurve, Sentry, Search Console), handover dashboard.
• Training: one or two calls reviewing typical mistakes for your team.
• Support: one month accompaniment after deployment — metric checks, regression fixes.

How many positions can you regain through technical SEO?

We have 5+ years on the market and 150+ projects completed. For a case study: a SaaS platform with 200k monthly visits had LCP 6.2s, CLS 0.45, INP 600ms. After optimization, LCP dropped to 1.8s, CLS to 0.02, INP to 180ms. Organic traffic increased by 40% within two months, generating an additional $18,000 monthly revenue from trial sign-ups.

Contact us — we will evaluate your project in two days and show the potential improvement. Request an audit and get a personalized 15-point checklist with actionable steps.