You would want to verify what @Jaideep_Brar suggests.  Assuming you are talking about page load time in your "site", there might be other factors at play as well Cache ratioSpecific component logicVolume of trafficClientlibs load time in browserbreaking JSIf in author, also look at the "developer mo...

When you say homepage, this is AEM Admin page? Or is the homepage part of the site you built on AEM? In any case, for such errors, you need to troubleshoot, starting with the logs.

If I have to think through the need for this, I can assume that 1) You have (to manage) static and editable templates2) (at least some of the )New components need to be supported in both static and editable templates3) Since one is developing components with style system, might want to leverage the ...

It is possible Chrome would be expecting some headers that is missing in 6.5 vs 6.4. You might want to scan the response headers in 6.4 vs 6.5 and find if something might be missing. 

Try "Move" Page option

1. You are not able to set a higher heap size than 1GB. Please verify if there are any other system limitations - meaning, what is the memory in your computer and how much is free for AEM?2. If you have sufficient memory, try setting 4GB in a new aem instance to ensure the issue is something other t...

If this is one off, you can probably try that using crxde. However if this needs to happen frequently, then the best option is to review the content hierarchy or page building logic. May be the components could be Experience/Content fragments that could be edited and published in their own cadence.

Only caveat I would add is that - you standardize on markup. Then apply styles as needed - either at site level or more granular. Site level is easier with but more custom code need to be written if you have to make this granular - to template/page specific.In order to standardize on markup, I'd pro...

Only caveat I would add is that - you

Only caveat I would add is that