Hello,
I am getting the following suggestions from:
https://developers.google.com/speed/pagespeed/insights/
Should Fix:
Optimize images
Leverage browser caching
Consider Fixing:
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Minify CSS
Minify HTML
What is the best practi
What have you tried?
On Mon, Jun 8, 2015 at 5:35 PM, Motty Cruz wrote:
> Hello,
> I am getting the following suggestions from:
> https://developers.google.com/speed/pagespeed/insights/
>
>
> Should Fix:
> Optimize images
> Leverage browser caching
> Consider Fixing:
> Eliminate render-blocking J
And CDNs are your friend.
On Mon, Jun 8, 2015 at 5:41 PM, Darryle Steplight wrote:
> Look into grunt or gulp first for Minify CSS,Minify HTML and optimizing
> images.
>
> On Mon, Jun 8, 2015 at 5:38 PM, Emir Ibrahimbegovic
> wrote:
>> What have you tried?
>>
>> On Mon, Jun 8, 2015 at 5:35 PM, M
Look into grunt or gulp first for Minify CSS,Minify HTML and optimizing images.
On Mon, Jun 8, 2015 at 5:38 PM, Emir Ibrahimbegovic
wrote:
> What have you tried?
>
> On Mon, Jun 8, 2015 at 5:35 PM, Motty Cruz wrote:
>>
>> Hello,
>> I am getting the following suggestions from:
>> https://develope
Hello,
I added this code on .htaccess
AddType application/x-javascript .js
AddType text/css .css
*AddOutputFilterByType DEFLATE text/css application/x-javascript
text/x-component text/html text/richtext image/svg+xml text/plain text/xsd
text/xsl text/xml image/x-icon application/javascrip
On Mon, Jun 08, 2015 at 02:35:24PM -0700, Motty Cruz wrote:
> Should Fix:
> Optimize images
> Leverage browser caching
> Consider Fixing:
> Eliminate render-blocking JavaScript and CSS in above-the-fold content
> Minify CSS
> Minify HTML
All of those bar one are content issues and therefore unconn
From Apache point of view...
* Don't use .htaccess files... put everything in httpd.conf (or
equivalent) there is a huge file system performance hit {Apache has
to look for .htaccess files in the directory and any parent directories}
include "AllowOverride None" in httpd.conf
* Remov
Hi James,
On 06/09/2015 10:24 AM, James Smith wrote:
From Apache point of view...
* Don't use .htaccess files... put everything in httpd.conf (or
equivalent) there is a huge file system performance hit {Apache
has to look for .htaccess files in the directory and any parent
direc
Yes - it is the request over head - the client will still make the
request at which point the server has got to decide has it changed
before even - which for most static requests is the heaviest (slowest)
part before returning the not-changed response - and then serving the
content!
You are
>> Remove etags (Header unset Etag/FileETag None)
> Won't this disable conditional requests, ex. If-None-Match and friends? Is
> your recomendation because of the header overhead or am I missing something?
Just if-None-Match. If-Modified-Since would still work. I believe
people recommend disabli
At 09:24 AM 6/9/2015 +0100, James Smith wrote:
[snip good advice]
* For minifying CSS/JS: look at yui compressor and google closure
compiler... (Use jshint to check your js to make sure that it will
merge/compress OK)
* Can use a number of build tools to do some of this auto-magically..
Hi Rainer,
On 06/09/2015 02:53 PM, Rainer Canavan wrote:
Remove etags (Header unset Etag/FileETag None)
Won't this disable conditional requests, ex. If-None-Match and friends? Is
your recomendation because of the header overhead or am I missing something?
Just if-None-Match. If-Modified-Sinc
It's not the etag calc it's actually the round tripping to the server
that is the main over head - better to get the client to cache content...
Apache will still have to touch the file system to see if the content
has changed (however it is done) and on some filesystems just
locating the file and
Hi James,
On 06/09/2015 02:36 PM, James Smith wrote:
Yes - it is the request over head - the client will still make the
request at which point the server has got to decide has it changed
before even - which for most static requests is the heaviest
(slowest) part before returning the not-chan
In many cases it will only be a few packets anyway so won't actually
make that much difference!
The point is that it is better to stop the request in the first place by
setting the appropriate expires/cache control header... than use the
etag mechanism...
James
On 09/06/2015 14:56, Frederik
Thanks for your suggestions!
Thanks,
Motty
On 06/09/2015 06:59 AM, James Smith wrote:
In many cases it will only be a few packets anyway so won't actually
make that much difference!
The point is that it is better to stop the request in the first place
by setting the appropriate expires/cache
Hi James,
On 06/09/2015 03:59 PM, James Smith wrote:
In many cases it will only be a few packets anyway so won't actually
make that much difference!
The point is that it is better to stop the request in the first place
by setting the appropriate expires/cache control header... than use
the et
17 matches
Mail list logo
