3 ms·

I (naively) read Google's performance tips as fact and wouldn't have thought twice about it. Lesson learned.

• tjogin 17y ago
  Their tips on how to optimize HTML pages are similarly silly. They suggest removing all end tags, as well as start and end tags that aren't strictly necessary according to the HTML standard, such as the 'html', 'head' and 'body' tags. Saving a byte here and there for the sake of transfer-speed, without a thought for rendering speed or maintainability, is apparently ideal.
  • gojomo 17y ago
    Re: dropping HTML end-tags that can be inferred At a large enough scale, it might be worth it, especially if the stripping were automated as part of deployment, so origin-side authors can use whatever's most readable. Do you know for sure that rendering engines are slower when having to infer end-tags? I would think the most common case is when you elide a end-tag by just ending a containing element, instead. I can't imagine that being a big rendering delay.
    • DougBTX 17y ago
      It's probably just a factor in parsing, which is plenty fast anyway; it would have no effect on rendering.
    • tjogin 17y ago
      Wouldn't it be kind of weird if Google's optimization tips were primarily meant for the relatively scarce few websites that operate on the scale at which their tips are even meaningful, whilst not even dropping a single hint to that fact, and in the process confusing everybody else?