I am investigating different options for optimising our website. Having spent a morning of searching online, I have found the vast majority of articles refer to optimising the repositories, the OAK side, the workflows and indexing. While I am certainly not dismissing these factors, they're not quite what I am looking for - I was hoping to find more examples of how to optimise on the front-facing site. So for example:
reducing the number of HTTP requests - there appear to be quite a few extra JS files loaded on our site, some of which may not necessarily be needed but they are all dependencies of each other. Does anyone have experience of this with their website and do you have any tips on how to reduce the number of requests without breaking the site?
similarly, are there any JS/CSS files that AEM loads by default which don't need to be on the front-facing site?
I've read that it might be a good idea to use a CDN for JS/CSS assets - but how does this work in conjunction with using ClientLibraries?
Any help or advice will be a good starting point and hopefully the discussion will go on from there
I think that you first need to split the complete area of website performance optimization into 3 distinct areas:
* Server side optimization: Here you optimize the time the requests required to be responded on the server. That's something which can be found in AEM in the request.log, but also in the access.log of webservers etc (let's ignore the fact, that the dispatcher can sit on a different machine and there is network between dispatcher and AEM).
* The network aspect: everything between server and the end-user. The internet, so to call. CDNs and proxies, fiber or modem. Optimizing here is rarely possible (besides maybe CDN).