3

Not sure how you implemented the cache tags, but I would recommend to cache each "eDrops" entry individually. I also took out {% if entry.slides|length %}. Testing if entry.slides.first() returns anything is all you need. In order to make the length filter work, Craft internally applys find() to the criteria model behind entry.slides. This means you (...


3

Any content or relationships that belong to the Matrix block will also be deleted, when you save the entry. If there were any relationships, the target elements won’t be deleted, though.


2

So... just to be clear. This /style.css is a static asset, it's not sitting in the craft/templates folder, right? Assuming that's the case, something is definitely wrong if https is taking 2 seconds to load it. Sounds like something with your server is misconfigured. How are you measuring this, exactly?


2

I often read the first user request is slowest to Craft Sites point mentioned in articles/posts, what exactly is that referring to? Probably missing some context surrounding where you originally read that, but if it was talking about caching, then maybe it was referring to the first user that triggers the request to generate the necessary cached content. ...


1

If any of your image transforms have not previously been processed they will make a call to /cpresources/... To prevent this, generate all your transforms before page load with the generateTransformsBeforePageLoad config setting: 'generateTransformsBeforePageLoad' => true


1

I used to have the same issue then I started using Eager Loading Element. It allows you to speed up your craft cms templates by fetching matrix from the database more efficiently. You can refer to this link which might help you for further understanding of Eager Loading.


Only top voted, non community-wiki answers of a minimum length are eligible