Daily Blogger

HTML Minify Or Death Of W3C Standards

Posted on: 02/08/2010

The SEO worthy of the name knows that web performance (understanding the loading time of pages of a site) is one of many criteria taken into account by Google in its ranking algorithm results.

In 2009, Matt Cutts, head of the cell antispam and official spokesperson for Google, spoke once on the subject, indicating that the load time still did not affect the results. More recently Matt stated that if the sites were not necessarily penalized slow however quick sites could get a little bonus on the final grade performance that determines the order of results.

htmlminify

htmlminify

 On April 9, 2010 in a letter signed by the college principal engineers of Google information was formalized: the loading rate is one of the criteria taken into account by the Google algorithm. And if there is one thing any SEO black, gray and white hat has to do is maximize the benefit of levers “on page”. Besides SEO, optimize site performance can also: to significantly improve the user experience, lower bounce rate, to avoid having a penalty in SEA, improve conversion rates in light of improving the profitability of a site.

Almost all of the web is not properly optimized (except maybe some of the Gurus and perf Google SERPs), there are many levers to optimize the loading time of pages and if I did not intended to develop all this article I invite you to visit the two most successful documentation on the subject:

  • Web Performance Best Practices par Google
  • Best Practices for Speeding Up Your Web Site par Yahoo!
  • Caution
    Optimization of HTML is not part of “Quick Wins” performance unless you work on static html pages then it can go pretty fast, do not consider “Minifier” your HTML code that from the moment you have taken seriously in hand the performance of your pages and you have already achieved a higher score 90/100 on PageSpeed or an A on YSlow. Most of the time you reduce the size of your HTML document “only” 5% to 20%.

    HTML is not a programming language optimized

    Whatever the ayatollahs of W3C standards, whether html3, 4, 5, or xhtml html is not optimized and has many tags and attributes redundant and unnecessary.
    The development team behind the project at Google HTMLminify has identified several HTML elements that when removed has no impact on display and let the page fully accessible to note that these optimizations are applied on the results pages of Google for a year already.

    What is HTMLminify?

    A detailed listing of optimizations made with HTMLminify is present in the source code of firefox addon PageSpeed, the original is available on Google Code html.compactor, but since it was in English I will propose the translation:

    Removing the “quotes” when possible, and is good, while a must keep the quotes because of the space.
    Except, spaces, line breaks and tabs between excessive HTML tags are removed.
    Removing comments (with exceptions).
    Removing unnecessary tags that do not affect the rendering of the page.
    complete list of tags: , , < / optgroup> , you will notice that many of these tags are tags closure.
    Passage lowercase tag names.
    Removing default attributes as or

    But develop “HTMLminifié is quite tedious that means they already have a strong command of HTML and its most rigorous standards, but flawless when it comes to test your pages on different browsers and operating systems existing .

    The addon PageSpeed, downloadable from Google, you will be a great help because after a scan offers an optimized version of the pages it audits, it optimizes the pages for a very simple static pages built Dynamically will require patience and optimize each piece of code.

    Risks
    I emphasize that the HTMLminify is not put into everyone’s hands, first because with this kind of optimizations, integrators are working without a net, once implemented the W3C validation does moulinettes more you can help correct the HTML of your pages. Another difficulty is that if you push the logic of reducing the code to the extreme by removing most line breaks, the html will be almost unreadable, you’ll soon find your strength brands, but this kind of condition does not facilitate development work Collaborative fortunately many software indentent code automatically.

    The web is a performance business critical issue and it is clear that web standards do not meet this need for efficiency, optimization techniques such HTMLminify going to know my opinion a real success in the years to come, Referrals will add another string to their bow if they want to stay on top.

    To go further, you can follow and participate to the Google Groups PageSpeed, there discovers that when a call to a file. Js or. Css less than 500 bytes it is better to include the code on the page (inline. js and inline. css) to the economy of a round trip HTTP header. Finally I invite you to consult the Google search pages that are extremely well at byte coded minifiées near …

    Advertisements

    1 Response to "HTML Minify Or Death Of W3C Standards"

    […] URL: HTML Minify Or Death Of W3C Standards « Daily Blogger more-you, validation-does This entry was posted on sie 2nd, 2010 at 04:00 and is filed under […]

    Comments are closed.

    RSS Unknown Feed

    • An error has occurred; the feed is probably down. Try again later.

    链接


    Promote Your Blog

    Add this page to SheToldMe.com

    August 2010
    M T W T F S S
    « Jul   Sep »
     1
    2345678
    9101112131415
    16171819202122
    23242526272829
    3031  

    Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 143 other followers

    Archives

    Top Rated

    Blog Stats

    • 32,075 hits
    %d bloggers like this: