You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Assess impact of pulling news from Substack on homepage load time and address if appropriate #685
For me, it's really useful if you give just a bit more detail re what you did and why, Nils.
If you believe the issue is resolved - that we understood the impact of calling and caching and made the right choice - can you write something demonstrating this and describing the result?
Sorry, I thought this individual change was small enough to not require explanation. I didn't notice any performance issues so I don't know whether there is anything else to investigate. Loading a cached response for each visit should basically be the same as loading a static asset wrt cost and performance if I understand correctly.
Makes sense.
Since the news articles are prominent on the site and key information, I'd
quite like to localize them. In that case we would move composition of news
text into build time too. Obviously we'd want "create or update key news
article" to be something very quickly reflected on the website at crunch
times , but we know the mechanism is simple: build and deploy. (The times
also coincide with likely hyper scaling as the world suddenly cares - when
we don't want much dynamic composition anyway.)
Activity
Wituareard commentedon Mar 5, 2026
It shouldn't be blocking right? But caching the endpoint could be a good idea
Cache news endpoint #685
Revert "Cache news endpoint #685"
Wituareard commentedon Mar 5, 2026
Re-applied caching, Netlify behaved differently than browser
anthonybailey commentedon Mar 9, 2026
For me, it's really useful if you give just a bit more detail re what you did and why, Nils.
If you believe the issue is resolved - that we understood the impact of calling and caching and made the right choice - can you write something demonstrating this and describing the result?
Wituareard commentedon Mar 9, 2026
Sorry, I thought this individual change was small enough to not require explanation. I didn't notice any performance issues so I don't know whether there is anything else to investigate. Loading a cached response for each visit should basically be the same as loading a static asset wrt cost and performance if I understand correctly.
Wituareard commentedon Mar 10, 2026
Other performance improvements I recently made to the homepage:
anthonybailey commentedon Mar 11, 2026