Assess impact of pulling news from Substack on homepage load time and address if appropriate

[anthonybailey]

As per #654 (comment)

[Wituareard]

It shouldn't be blocking right? But caching the endpoint could be a good idea

[Wituareard]

Re-applied caching, Netlify behaved differently than browser

[anthonybailey]

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]

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]

Other performance improvements I recently made to the homepage:

• Optimize news images at build time and through Netlify Image CDN (4c46509)
• Optimize press logos (4b89235)

[anthonybailey]

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.)

…

On Tue, 10 Mar 2026, 20:43 Wituareard, ***@***.***> wrote: *Wituareard* left a comment (PauseAI/pauseai-website#685) <#685 (comment)> Other performance improvements I recently made to the homepage: - Optimize news images at build time and through Netlify Image CDN ( 4c46509 <4c46509> ) - Optimize press logos (4b89235 <4b89235> ) — Reply to this email directly, view it on GitHub <#685 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAXXDI575IYO3B3O46WI5L4QB5ANAVCNFSM6AAAAACWIO4KG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAMZUGM2TGOBXHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>