circagraph
Sign inSign up

openchronology/timeline-app on GitHub

The OpenChronology repository on GitHub, mirrored by och-import-github: issues and pull requests as durations (ongoing while open), what happened to them as moments, plus releases, milestones, commits and branches. The Branches view shows the most recently active branches each in a track of its own.

Source: https://github.com/openchronology/timeline-app

3,131 moments · 2026-10-05 CE 20:21:49 UTC – 2026-11-16 CE 12:10:45 UTC · by @athan · @athan

#473 Public pages are never cached; measure Core Web Vitals

–

  • github
  • github/openchronology/timeline-app
  • github/openchronology/timeline-app#473
  • issue
  • state:closed

Every page, including public timeline and event pages seen signed out, is sent with `cache-control: private, no-cache, no-store, max-age=0, must-revalidate`. So each visit and crawl renders the page again. From one location the first byte took about 0.4 s for `/`, `/explore` and a timeline page. Core Web Vitals weren't measured. Wanted: 1. Measure with PageSpeed Insights or Lighthouse: LCP, INP and CLS on the landing page, Explore, a timeline and an event page. 2. Consider caching signed-out views of public timeline and event pages briefly, through nginx or `s-maxage` with revalidation. Changes should clear or expire the cache quickly. Pages that differ by session must not be cached. Found in an SEO audit of timescale.info on 2026-11-06. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/issues/473

Related

Open #473 Public pages are never cached; measure Core Web Vitals in the timeline

#473 Public pages are never cached; measure Core Web Vitals