Saltar al contenido
AKOS
Todos los packs
StableRendimientonetwork-performance

Network Performance

Operationalizes network-layer performance: connection setup cost (DNS/TLS), HTTP/2/3 multiplexing, resource prioritization, compression, and offline/poor-network resilience — the layer beneath rendering that determines how fast bytes actually arrive.

networkhttp2http3compressioncdndns

Principios

  • · NP2 — Compress all text-based responses (HTML, CSS, JS, JSON, SVG) with Brotli (preferred) or gzip (fallback), applied at the server/CDN level.
  • · NP3 — Reduce connection setup cost for known-critical origins via <link rel="preconnect"> (and dns-prefetch as a lighter-weight fallback) for third-party origins the page definitely needs (CDN, API, font provider).
  • · NP4 — Use CDN/edge delivery for static assets, minimizing the physical distance (and thus latency) between the user and the server for content that doesn't require origin compute.
  • · NP6 — Design for intermittent/poor connectivity: requests have sensible timeouts, retries with backoff, and the UI communicates network state (offline, slow, retrying) rather than hanging silently.
  • · NP7 — Cache and serve previously-fetched content instantly where feasible (service worker cache, HTTP cache), updating in the background rather than blocking the UI on a fresh network round trip for unchanged content.

Patrones

  • · The protocol check: inspect response headers/DevTools network panel — is the site served over h2/h3, or still http/1.1? The latter is a quick, usually infrastructure-level win to flag.
  • · The compression check: inspect Content-Encoding on text responses — is Brotli/gzip applied? An uncompressed JSON API response is an easy, sizeable win.
  • · The third-party origin count: count distinct origins the page connects to (fonts, analytics, ads, APIs) — each is a fresh DNS+TCP+TLS cost unless preconnected; consider consolidating or preconnecting the critical ones.
  • · The "does this page work offline-ish" test: throttle to "Slow 3G" or go fully offline in DevTools — does the page fail silently, hang indefinitely, or communicate the network state and degrade gracefully?
  • · The priority-hint gap check: is the LCP-candidate resource marked fetchpriority="high", or is it competing on equal footing with non-critical resources for bandwidth priority?

Riesgos

  • · Ver anti-patrones específicos del dominio en el pack.

Checklist

  • [ ] HTTP/2 or HTTP/3 enabled in production. (NW1)
  • [ ] All text-based responses compressed (Brotli/gzip). (NW2)
  • [ ] Static assets served via CDN, not directly from origin. (NW4)
  • [ ] Network requests have timeouts and appropriate retry-with-backoff (transient failures only). (NW6)
  • [ ] Critical third-party origins preconnected; budget limited to 2-4 origins. (NW3)
  • [ ] LCP-critical resources use fetchpriority="high"/preload; non-critical use low priority. (NW5)

Fuentes

En la bibliografía AKOS

Este pack cita las siguientes fuentes registradas en el índice bibliográfico:

Explorar todas las fuentes →