One JS/CSS for all pages

That’s a difficult question, really.

Assuming you’d really only would want to have 1 optimized css-file and not taking the current logic of Autoptimize into account, one could theoretically either;
1. exclude all non-generic CSS from aggregation and put that in an optimized file which would then be used on every page
2. add any CSS (generic and page- or segment- specific) found on any page to 1 CSS-file

advantages of (1); 1 light optimized file (but it might just be an optimized versoin of your base theme style.css)
disadvantage of (1); there would be a lot of page- or segment-specific CSS that would still have to be downloaded seperately

advantages of (2); one file to style your entire site. presuming users are not on mobile (with limited caching) and that your users on average visit several pages, this might indeed be good.
disadvantages of (2): there would probably be a lot of overhead in that one file (IE<10 has a maximum amount of CSS-selectors that are executed, the rest if just ignored) and there would be a risk of collusion of CSS rules that are not supposed to be on the same page.

The approach in between would be to try to make sure you have one CSS for home, one for normal wordpress-pages & posts, one for product pages, … the way to accomplish that would be to carefully examine what is aggregated now (resulting in too many different optimized CSS-files) and to exclude just the right amount of CSS in there to make the optimized-files more generic.

hope this helps,
frank

Ok, got it. Thanks for the response.

PS: You didn’t answered my PS on the first message! ??

Ah, the PS … Well, I’m working on “Autoptimize Power-Uppers”, which will extend the functionality of Autoptimize and which will be available in a subscription-model. So if you really like AO and want even more, you can pay me a small monthly amount once this becomes available. The beta will most likely be free though. Bummer ??

frank

*raises hand for beta testing*

Exciting! What will be in the paid-for version, Frank? To what extent will it differ from the free version?

I still think you should do an “Autoptimize PRO” (whatever), which would include the ability right from within the UI to implement the extended functionality offered by the helper and sell it on CodeCanyon… add white-labeling and caching features comparable to W3TC and, you know, corner the market and get rich lol.

I may be a dreamer, but I’m no the only one ??
AJ

– Hands up for beta as well.
– Count me in as subscriber. Don’t forget bulk discounts.
– How can i help with localization?
– Disagreeing a lit bit with AJ: don’t ever be bloated as W3TC (although i love to use it when not using WPengine)
– closing the thread as solved. We can keep the Pro conversation elsewhere.

don’t ever be bloated as W3TC

Not sure we’re disagreeing, mate(?).

Were there an Autoptimize “pro” (version) that also handled caching (e.g. page, database, object, fragment) in the manner in which W3TC does, (in addition to the optimization features AO already offers), such a plugin would utterly dominate the WordPress WPO space. Beyond a doubt. Completely. — For reasons that are immediately obvious to any and all that have dealt with W3 Total Cache…

Autoptimize is in a unique position to do precisely this; it would be nice to see the benefits go to Frank.

(although i love to use [W3tc] when not using WPengine)

And you do so because it is an awesome plugin.

bloated

Lot’s of people accuse W3TC of being “bloated” and yet none offer an actual argument as to why they’re saying it is.

The reason? Because it isn’t:
As far as code streamlining goes, the current version of W3 Total Cache is — relative to what is does — as streamlined (i.e. un-bloated) as is technically possible.

The onus, of course, is on you to prove the assertion that W3TC is “bloated”. I won’t hold my breath ??

At any rate, none of this has much to do with my premise(s), which is/are that Frank (and AO) are uniquely positioned to do wonderful things.

For Frank: Als alle gekken konden vliegen hadden we een permanente zonsverduistering. ??

AJ

Ah, you’re Dutch (or Flemish) AJ? I have to admit didn’t even know that proverb, but I instantly like it ??

Perhaps i didn’t use the right word, when i used “bloated”. I am not a native speaker.

What i meant is: there’s too many options and and features to work with. It’s great when you have the knowledge (my is partial), the right environment (W3TC doesn’t run on WPEngine, which, by the way, alread cache pages and database) and resources (human resources, time resources, et cetera).

In my company, i came to a time and place that in most projects (specially the client ones) i want to have the best solution with the minimal effort and best price possible, and, so far, Autoptmize and Better Minify are the best ones for ou mindsets. With Futta’s plugins winning the race because plays nicer with several other plugins we use and is almost effortless to set up.

In my specific case, the only thing I missed, so far, is the possibility to make only one file (this thread).

Anyway, I think it’s a great plugin and I am looking forward for the new version.

Thanks, guys.

@frank,

No, just a dabbler in languages and a sucker for a good witticism in any tongue lol.

@celso,

I see what you’re saying. ??

Best,
AJ