Autoptimze not working for our site

OK, some questions;
* did you have a look at the FAQ (which amongst other things lists conditions under which AO will bail)?
* what theme are you trying with?
* what does “not working mean”? does the HTML stay exactly the same with and without AO? or does the look&feel of the site break? or does some functionality (e.g. a slider/caroussel) break?
* what settings did you try AO with?
* do you see any relevant entries in the PHP errorlog?

frank

1.
2. onfleek https://themeforest.net/item/onfleek-amp-ready-responsive-magazine-theme/16039200
3. it is not aggerating js files and not compressing html the output html remains same before and after configuring
4. I have enabled html css and js, now i have only enabled Js setting but also not working
5. i have enabled error log not seeing any thing.
our test site is https://stg28mar.wpengine.com/

is “onfleek” your own theme (given “themeheap” you might be in the theme dev business)?

No, this is not our theme.

in that case; as AO works with twentyseventeen but does not work with onfleek I would create a ticket with the theme developer. you paid for the theme & support after all ??

I have investigated it a bit, also in contact with support team. cache files are being generated but not invoked in page. what can be the causes if you can point me to some files of hooks so i can have a look and solve.

hmm, that sounds like an output buffer conflict to me .. does onfleek use the output buffer?

Which hook does it use to insert tags in html ?

AO hooks into template_redirect after which the output buffer is started which results in AO getting the fully rendered HTML which is then used to extract the CSS/ JS, removing original CSS/ JS, aggregating, minifying and caching the result (which seems to work as you have files in wp-content/cache/autoptimize), injecting links to the cached autoptimized files and finally returns the HTML.

So if you have cached files in wp-content/cache/autoptimize but the HTML does not refer to those optimized files, then something must be breaking the output buffer …