Skip to content

Instantly share code, notes, and snippets.

@mikka23
Last active August 6, 2020 10:20
Show Gist options
  • Save mikka23/cf17cc9696abc7c49f1a06197a23759b to your computer and use it in GitHub Desktop.
Save mikka23/cf17cc9696abc7c49f1a06197a23759b to your computer and use it in GitHub Desktop.
reply
Hey everyone!
It is great to see customers being active parts of the community and we are sorry if anyone faces inconveniences.
However, when providing feedback, we always ask users to stay calm and friendly, even if something might go wrong at times. Please also do not present personal opinion as a fact. And please only present facts, not assertions. That will make things easier for all of us.
Just a few remarks regarding this thread:
- This is a forum for users to help users. This forum is neither actively moderated by ThemeFusion nor is it an official means of support. This is stated in the terms of the forum, so shouldn’t be a surprise.
And while we understand that frustration can happen from time to time it is not a place for ranting for the sake of it or even swearing.
- ThemeFusion obviously does care a lot for their users and their needs. The mere fact of the number of updates that are rolled out is proof of that.
- If someone assumes that there is no need to add more features and that this would not be what our users want, well then that is just personal opinion. Here is just a few examples of others users thinking differently: https://i.imgur.com/psgGryO.png, https://i.imgur.com/EmrXIcP.png.
- It is simply untrue and absurd to say, we would be aware of issue and not care about them. Dozens of updates and big changelogs prove the contrary. We are not sure why someone would think false claims would be necessary to back his arguments.
- The changes in CSS loading for elements in Avada 7 are just as Michael C has stated above. Obviously, there is shared styles and these will be loaded for other areas. Apart from that, this is an area of constant refactoring.
- Regarding CSS validation errors: These are usually automated reports. A lot of it are false positives and just judging by a number isn’t the best idea. E.g. you will find parse errors for anything related to var( --a-variable-name). Well these are just CSS variables and all of that is correct CSS, yet the automatic validators complain. Now one can complain about that or try to understand if the report is correct. None of these slows down your website. Asserting this would be proof that we don’t care about performance is unsubstantial and just wrong.
Nevertheless, there will be issues from time to time as that is the nature of software. Obviously, we want to correct them as much as possible.
- Render-blocking assets do depend a lot on the actual site. Sites using sliders as a hero area e.g. have more overhead than others, as JS assets need to be loaded for them to work. Similar is true for fonts or the compiled CSS. You have options to load the CSS in the footer and to swap out default fonts once the custom ones are loaded. That will reduce render-blocking but comes with the trade-off of FOUC. A lot of users don’t like that, so we added options for everyone to choose for themselves.
- It is incorrect the JS files could not be dequeued by users. You are free to do so. And it is incorrect that these changes would revert with the next update. If one is doing it correctly nothing will be overwritten. Such changes should always be made in a child theme.
- The updating of the jQuery library has nothing to do with Avada. jQuery is loaded by WordPress natively.
- Regarding unused resources: this is an area we are already targeting to improve. There will be incremental improvements to this along the way but this needs to be part of a larger performance focused release and will include wideranging changes to the way content is delivered - not just the CSS. Also as stated above, there is a lot more to performance than the this. If you do check this in other vendors you will find very similar results.
- We do not deny that there are always areas to improve and we are actively working on them. Some things can take a little longer, some take a little more time, but everyone at ThemeFusion works hard to improve the user experience even further. Site performance is an important topic and we’ll keep working on it.
Thanks!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment