I have been using Avada for years, I have spent a lot of money on it too and I’m sorry to say guys, but I have to admit, I agree about the bloat problem.
The bloat can be massively mitigated with various compression tools – but so can every Theme. Avada appears to start off way more bloated than most, so with diligent work to compress and cache it, you can never overtake others doing the same work to compress theirs.
I have lost 3 clients this year, all to SEO agencies who convinced my clients that the website could not be made fast enough without remaking it in another theme. I didn’t get a chance to quote on that work, they were just gone, boom!
I work alongside another SEO agency and again, they try not to take on clients with websites made with Avada because it can’t go as fast as those made on some other Frameworks.
On broadband, the difference in load speed between Avada and others of similar content is not that noticeable to humans, but is seems to be to speed checking sites and in my experience, even 3% speed is enough to prove a point.
There is no way to argue that Avada is not bloated as it stands. I have tried and been gunned down by SEO people. I TOTALLY accept that it is bloated because it is so full of features, but there’s not much else it needs to be able to do at this point, except for the code to be made more modular, faster.
I think we are getting to the point where there needs to be an option to parse and republish entire websites to avoid using unnecessary cached code and to publish in a cachable form as efficiently as possible.
I am not one to complain, but I am tired enough of arguing with people about Avada that I may have to switch to a simpler Framework next year – with all the hassle that brings.
Fingers-crossed, more can be done to speed up Avada websites.