3 ms·
More often than not, the slowness end users experience is problems in the front end - not the database. Think uncompressed assets, cache misses, or unused javas
by ClifReeder 12y ago
More often than not, the slowness end users experience is problems in the front end - not the database. Think uncompressed assets, cache misses, or unused javascript and stylesheets. It's very likely most pages in your application are (or should) be served entirely from cache, so end users will benefit much more from front end optimizations.
- solomone 12y agoThis statement is dangerously false. Unused javascript and stylesheets is where you would start your performance debugging when users complain of slowness ?
- tonyarkles 12y agoThe Network pane is where I'd start. It covers all the bases, and then you can start narrowing in to whatever is the biggest win.p