--- title: "From latency to instant: Modernizing GitHub Issues navigation performance" url: https://daily.dev/posts/from-latency-to-instant-modernizing-github-issues-navigation-performance-t1jb6lu6h source_url: https://github.blog/engineering/architecture-optimization/from-latency-to-instant-modernizing-github-issues-navigation-performance type: article source: "GitHub Blog" published: 2026-05-14T16:02:39.206Z updated: 2026-05-14T16:03:06.769Z tags: ["webdev", "react"] reading_time: 15 upvotes: 14 comments: 1 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # From latency to instant: Modernizing GitHub Issues navigation performance **[GitHub Blog](https://daily.dev/sources/ghblog)** · 15 min read · 14 upvotes · 1 comments ## Summary The GitHub Issues team redesigned their navigation performance by building a client-side caching layer backed by IndexedDB with stale-while-revalidate semantics, a preheating strategy that proactively populates cache entries before users click, and a service worker that intercepts hard navigations to serve cached data. The result: P10 latency dropped from ~600ms to 70ms, P25 from ~800ms to 120ms, and the median from ~1200ms to 700ms. React soft navigations saw ~70% become instant after preheating, with a 96% cache-hit ratio. The post details the three navigation types (hard, Turbo, React soft), the HPC metric used for measurement, tradeoffs around controlled staleness (~4.7% server/cache divergence), and the remaining challenges around cold-start JavaScript boot time. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@kkurko** · 0 upvotes > It's always great to read articles like these, when big companies with huge products share their challenges and how they're solving them. You can learn a lot from such materials about maintaining and evolving products at scale. I would like to learn more about their transition from Rails to React ## Similar posts on daily.dev - [GitHub Increased Instant Navigation from 4% to 22% by Rethinking Client Side Architecture](https://daily.dev/posts/github-increased-instant-navigation-from-4-to-22-by-rethinking-client-side-architecture-kftw0wauh) · InfoQ · 0 upvotes · 0 comments --- Tags: [#webdev](https://daily.dev/tags/webdev), [#react](https://daily.dev/tags/react) [View this post on daily.dev](https://daily.dev/posts/from-latency-to-instant-modernizing-github-issues-navigation-performance-t1jb6lu6h)