Now, let see the gains... We added another processing layer per page load, that is the plugin. This uses up both processing and time resources on the [shared] server. On the other hand, this cuts some latency and processing on the client's side.
In proper cases, the css and js files are likely cached on the client side, thus are only an issue on the first visit. The server side too usually deploys some sort of caching [plugin], ammortizing the local assets serving latency.
The bottom line? Do not use the themes which come bloated with unused css and js (layout managers, you make user's life so deceptively 'simple'). Adding another plugin to the mix just postpones the reckoning.
It should be possible to detect such bloat from theme's demo.
1 comment
[ 3.4 ms ] story [ 13.8 ms ] threadIn proper cases, the css and js files are likely cached on the client side, thus are only an issue on the first visit. The server side too usually deploys some sort of caching [plugin], ammortizing the local assets serving latency.
The bottom line? Do not use the themes which come bloated with unused css and js (layout managers, you make user's life so deceptively 'simple'). Adding another plugin to the mix just postpones the reckoning.
It should be possible to detect such bloat from theme's demo.