{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreih3mkcxic2mj7tl73sezxysrqtza4g2kuvjmypzzcuqpl2v5lfcw4",
    "uri": "at://did:plc:2ikdxjcpbsuoe6mv3qawmazg/app.bsky.feed.post/3mlv3kx5334i2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreignazi4zb443vqyjulrlalyw22wxfdg6wevmpd5bsp2sjsle7y3h4"
    },
    "mimeType": "image/png",
    "size": 322158
  },
  "path": "/engineering/architecture-optimization/from-latency-to-instant-modernizing-github-issues-navigation-performance/",
  "publishedAt": "2026-05-14T16:00:00.000Z",
  "site": "https://github.blog",
  "tags": [
    "Architecture & optimization",
    "Engineering",
    "engineering",
    "GitHub Issues",
    "From latency to instant: Modernizing GitHub Issues navigation performance",
    "The GitHub Blog"
  ],
  "textContent": "How the GitHub Issues team used client-side caching, smart prefetching, and service workers to make navigation feel instant.\n\nThe post From latency to instant: Modernizing GitHub Issues navigation performance appeared first on The GitHub Blog.",
  "title": "From latency to instant: Modernizing GitHub Issues navigation performance"
}