Kati, thanks for showing him that thread.
Andy, although we’re working on improving it, it’s still not a problem that most users are having, just a few. This indicates that it’s likely to be something in your installation that causes these load times to happen.
Since s2Member’s JS and CSS are being generated dynamically. You can store the CSS in a static file, as mentioned in other threads, but the JS has user specific info that can’t be cached as a static file to serve everyone.
Because it checks access permissions and WP user data, it loads through WP, although a slimmer version of WP. So, whatever you can do to improve WordPress’ time, will improve the load times of s2Member’s CSS and JS.
Sometimes, as a test, you need to deactivate other plugins one by one and check the load times after each. Then you may find one that is causing a conflict in some way. I know the JS file is s2Member’s, but remember that it’s loaded through WordPress.
For caching, Jason’s QuickCache plugin is very effective and helps.
Another trick a site owner that had this problem months ago used, was to use a plugin that let him enable s2Member in some pages only, the protected ones. I think he used Plugin Organizer.
Of course, like mentioned in the other thread, we’re improving s2Member removing all the dynamic parts from the JS file, so it’s static and this isn’t an issue anymore.
I hope that helps. :)