What are Negabytes?

The size of your website files impacts loading time and bandwidth. If you are concerned about either (and you should be), you'll want to start optimizing your website for low page weights and small file sizes. When you start optimizing your website, take benchmark measurements of how much bandwidth you're using per page view, and the size of all dependent files. Then while you're optimizing, take measurements to see how much you're saving.

Every byte you don't send over the web is a Negabyte.

Negabytes come in two flavours:

• Design-time Negabytes

  These are Negabytes that you gain while designing the site. Design-time Negabytes are gained by optimizing image sizes, using efficient styling techniques, and optimizing source files before they are sent to your server.

• Run-time Negabytes

  Run-time Negabytes are gained only when someone requests a page, and a process on your server does real-time manipulation to the output stream to save bandwidth. Examples of run-time Negabyte methods include GZIP, run-time whitespace compression, and handlers that intercept HTTP requests and do real-time manipulation of files as they are requested.