Your use case seem to be a fit case for using content fragments. They are created in dam and can be surfaced across multiple websites as needed.

Check the type of auth cookie. If it is https and secured then , cross domain, it won't be visible to client side scripts (js), but would be sever side.

2GB might not be enough. Try bumping it to 4GB and then try. I am pretty sure you'll be alright.

Howz the memory allocated to your instance?

You can also mark the links as valid by using x-cq-linkchecker=“valid”property in your <a> tag. In this case Link Checker will check the link but always mark as valid.If you also use x-cq-linkchecker=“skip”, Link checker will not check the link and mark as valid.After updating the code you would hav...

use a request scoped sling model and use that to get the selector and then use that on your sightly script.

This would work only if you are using xtype as datetime. That would store it as a Date and then you can retrieve it like you are trying.