Hacker News new | past | comments | ask | show | jobs | submit login

I'm not sure your advice here is the best.

it often advices to compress images and even suggests to download "optimally" compressed versions

Compressing images is useful, and this advice can be beneficial – though I'm sure it's more effective to optimise them yourself rather than relying on the Google-generated versions.

"embed CSS code necessary to display the top of the page, right into the page".

This is good advice. For larger sites with more extensive stylesheets, this approach allows the initial 'above-the-fold' to be rendered better before the full stylesheet is loaded. Just because it doesn't hit every case – like when users scroll during load – does not render it ineffective. It's also neither difficult to implement, nor does it add enough load time to pages to be a practical issue (unless you're inlining 100kB of text, in which case – rethink your stylesheet!)

For example, it never advices to remove or replace web fonts

It would be a bit silly to do so; web fonts are added on purpose, and advising that they be removed is pretty useless advice, along the lines of "you can speed up your website by removing images". It would be nice if the tool supported analysis of web font use though, such as testing to see if particular styles are used, or if the font could be effectively subsetted.

Also it never advices to remove ads althogh ads often cause high CPU and memory consumption. Why is that I wonder.

Again, it would be useless information to tell someone who has deliberately added advertising to their website to remove it.

The tool always requires to move JS scripts to the bottom of the page. But is it always the best idea? I think in most cases it is not.

Yes, it is – either that, or loading the scripts deferrably or asynchronously.

it will give a JS error if the button is clicked before the scripts in the bottom of the page have loaded

This is only the case if you write bad Javascript – binding to DOM elements and their events should be done asynchronously.

And what if you have a SPA? In this case the earlier you start to load the scripts the sooner the user will be able to see the data.

If you have an SPA, then either there is no real markup on the page (and the difference will be minimal) or you are pre-rendering it, and the content will be visible anyway.

Also it always recommends to use a CDN which is not always good idea.

Using a CDN is almost always a good idea unless you have a very specific reason not to do so.

So Google's script might help you in identifying problems with your site but you should not ever blindly trust any of the recommendations. Please leave client side optimization to people who have expertise in this area.

I would say this much is obvious – it's a tool, and like any others, experienced professionals can use it to make appropriate decisions. It can help with that.

SEO rankings and obviously they are more important than image quality.

The unfortunate thing is that they probably are!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: