Design

• Choose the most suitable technology (#1)
• Use a framework or custom build (#2)
• Choose a design that is simple, clear and tailored to the web (#5)
• Use as few plugins as possible (#24)
• Allow for quick navigation through the history (#28)
• Adapt videos to the viewing environment (#92)
• Adapt sounds to the listening environment (#95)
• Compress documents (#97)
• Optimize PDFs (#98)
• Adapt text for the web (#100)
• Remove duplicate email addresses before sending (#102)
• Only use double opt-in email addresses (#103)
• Use plain text instead of HTML (#104)
• Remove non-essential features (#109)
• Precisely specify the need (#110)
• Improve the process flow (#111)
• Employ asynchronous processing when possible (#112)
• Limit the number of HTTP requests (#180)
• Use input help instead of autocomplete (#204)

Development

• Favor static pages (#3)
• Use performance-orientated forks of applications (#4)
• Split CSS (#9)
• Minimize the number of CSS files and compress them (#10)
• Favor CSS over images (#11)
• Use standard typefaces (#19)
• Avoid using bitmap images for the interface (#161)
• Keep the number of domains serving resources to a minimum (#170)
• Avoid expensive JavaScript/CSS animations (#810)

Hosting

• Minify CSS files (#12)
• Optimize bitmaps (#21)
• Avoid redirections (#45)
• Do not generate 404 pages (#46)
• Choose a 'green' web host (#66)
• Use 'green' electricity (#67)
• Maximize the energy efficiency of servers (#68)
• Choose servers with SSD storage (#69)
• Use virtual servers (#70)
• Store data in the cloud (#71)