The number of HTTP requests is a major factor when using HTTP 1.1. I hear this will cease to be a factor with HTTP 2.0.
On Thursday, December 1, 2016 at 11:26:44 PM UTC-8, Steve Piercy wrote: > > On 12/1/16 at 11:47 PM, (unknown sender) pronounced: > > >On 11/25/16 3:48 PM, Venmore wrote: > > > >>What is the best way to do this within BBEdit please? > > > >Coming back to this, Why? > > > >CSS is taxt, and text is small. A single small graphic on a > >page is probably more data than all the CSS, so you're not > >saving anything by squishing it down to remove a few EOLs and > >maybe some spaces. Add to that that nearly all webservers > >compress the data and you're saving practically nothing, if > >anything at all. > > Yup. The number of HTTP requests is a major factor in > performance. The tool Google PageSpeed Insights is helpful. > https://developers.google.com/speed/pagespeed/insights/ > > Tools like webpack, gulp, or grunt automate static asset optimization. > https://webpack.github.io/ > > Google PageSpeed web server module, if your server supports it, > can squeeze out every last drop of optimization of static assets > when served. > https://developers.google.com/speed/pagespeed/module/ > > --steve > > ------------------------ > Steve Piercy, Soquel, CA > > -- This is the BBEdit Talk public discussion group. If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit> --- You received this message because you are subscribed to the Google Groups "BBEdit Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/bbedit.
