Do you use managed packages built with Lightning Web Components? Your Salesforce users might be losing 30+ seconds every day on their initial record load due to a Salesforce known issue that needs to be better prioritized. 

Have you noticed how on some Lightning record pages, the initial load takes 30+ seconds and seems totally unexplainable? Then after that first load, it's fine for the rest of the day. 

Here's what makes this worse than it looks: it's not a one-time delay. Every individual user hits their own cold start, so if you have 50 users opening an affected record type each morning, that's 50 separate 30-60 second delays, every single day. The productivity cost scales directly with your user count. 

We spent weeks investigating this on our managed package pages with the managed package vendor before Salesforce support confirmed it's a platform-level known issue affecting Lightning pages with shared component subtrees, not something specific to any one vendor's code: 

Known Issue: Flexipage performance degradation on DynamicComponent

 (Reference ID: W-23284931) 

This known issue feels significantly underreported for how big the impact is. If you've written it off as your imagination, blamed it on a slow server day, assumed it'll just go away, or your users have just been complaining without ever filing a ticket, this is likely why. 

If you manage Lightning pages with complex or shared component structures and have noticed this pattern, please report the known issue above against your own org and ask your AM for a timeline of when the issue will be fixed. At a minimum, it just takes clicking a checkbox on the known issue. I am hoping more visibility on the known issue means more pressure on Salesforce to prioritize a fix. 

#Lightning Performance  #Lightning Web Components  #Installed Packages  #Salesforce Admin  #Salesforce