Having a CDN doesn't help your performance when you tell it not to cache the page

  bragr@<>:~$ dig +short community.silabs.com
  community.silabs.com.00da0000000l2kimas.live.siteforce.com.
  sdc.prod.communities.salesforce.cdn.edgekey.net.
  e78038.dsca.akamaiedge.net.
  173.223.234.17
  173.223.234.11
  bragr@<>:~$ curl -Is https://community.silabs.com/s/share/a5UVm000000Vi1ZMAS/quake-ported-to-arduino-nano-matter-and-sparkfun-thing-plus-matter-boards?language=en_US | grep -i cache
  cache-control: no-cache,must-revalidate,max-age=0,no-store,private
  x-origin-cache-control: no-cache,must-revalidate,max-age=0,no-store,private

That said, the assets are cacheable so there was probably just a thundering hurd for the assets until they were well cached by Akamai's mid and edge tiers

When I've used a CDN, there were separate headers to control the CDN with the same semantics as cache-control... so you can serve the cache-control you want to browsers and control the CDN separately.

If it doesn't feel like it's cached, it probably isn't; but you can't assume the cache-control headers you see are controlling the CDN.

Depends on the Akamai property config which could be anything. IIRC by default it uses the standard cache headers and doesn't strip or rewrite them, although it definitely can.

ugh, old.reddit.com sends a no-store when signed in and its driving me mad because it breaks back/forward cache.

All “security” guidelines blindly suggest no-store. Also private with no-store makes no sense.

>individual elements on this page taking multiple seconds to show. is it not 2024 yet?

It's exactly what 2024 feels like. Future sucks.

Maybe it's running on an Arduino Nano Matter.