Web-friendly PDFs
If you have a website that serves up PDFs you’ll want to make sure you are delivering them in a web-friendly way. While HTML web pages tend to be relatively small in terms of size, a PDF can be much larger depending on its content. Several factors contribute to this such as embedded fonts, a large number of pages or high-resolution graphics. Therefore, as a thoughtful provider of PDF content, you’ll want to spend a little time upfront in preparing your PDF rather than make your end users spend a lot of time waiting to view your PDF - if they decide to stick around and wait.
For the most part, small to medium size web pages typically render in the browser quickly. This is partly due to the fact that the browser will display certain items while it continues to work on other parts of the page so the page has the illusion of loading quickly. You may notice some sites with lengthy tables tend to take longer as the browser has to work to determine the optimal size for each column based on all the data in the table. Even though it may take some time (few seconds to a minute or more) to render an HTML page, when you can see various items start to populate in the window you can begin to focus on those areas while the rest populates.
A standard PDF works differently when you view it in your browser from a website. In this case, the entire PDF must be downloaded to you computer before the PDF viewer will show this first bit of content. The main reason for this is the way a PDF is structured. A PDF is not required to be physically setup in the same order its pages are laid out. That is, the data required for page 1 of the PDF isn’t necessarily near the top of the file. In fact, PDFs have what is called a cross-reference table that specifies where all the objects or logical pieces are located. The cross-reference table is located (not always in its entirety) at the end of PDF. Thus, the entire PDF must be sent down the wire first to determine which pieces are needed and where they are within the PDF.
Optimization/Linearization
First up is optimization, which you might also hear referred to as linearization or fast-web view. The point behind this is to physically restructure the PDF in such a way that the PDF viewer can begin to render the PDF without waiting for the entire PDF to download. Different software will have different ways of setting this feature - there is a checkbox in Adobe Acrobat when you save the PDF to specify this and most FyTek software has an option that can be set. Check the documentation if you are using other software to see if the option is available.
Optimizing a PDF is a method by which the first page of the PDF and bookmarks are moved to the top of the file along with part of the cross-reference table. Some special settings are also made in the PDF file to denote to the PDF reader that this happens to be an optimized PDF. When a web browser instructs the PDF plug-in to open and display the PDF, the browser will begin to show the first page (almost) right away. Once the first page is displayed along with any bookmarks the browser will continue downloading the rest of the PDF in the background. There may be a slight delay as you click to different bookmarks as that page might not yet be downloaded. The total time to download the entire PDF will not be affected - but end users can begin to read the PDF much quicker rather than stare at the spinning wheel or globe in their favorite browser.

Optimized PDF Loading in Firefox
I should point out that optimization does not physically reduce the size of your PDF. In fact, with the extra information needed to specify it is an optimized PDF, you will likely notice a small increase in the byte size. Typically by only a few hundred to a few thousand bytes of the original size of the PDF before optimization. Also, optimization will have no effect on PDFs outside of the web. Opening an optimized PDF from your hard drive will be no faster than opening the same un-optimized version. That is because the web server combined with the PDF Reader browser plug-in is what allows optimization to work and neither are in play when you open a locally stored PDF.
Other options
There are a few other options to consider in addition to optimization. One is to use lower resolution images if possible. Next, if your software supports it, use font subsets. This option will place only the needed glyphs for fonts in your PDF rather than the entire character set. Check the documentation for the software you are using to see if this option is available. Better yet, do you need a custom font? Try using a built-in font instead so you don’t need to include any extra font information. PDF readers contain built-in fonts for Times Roman, Helvetica (Arial) and Courier.
Another consideration is to break up the PDF into smaller PDFs. Perhaps use the bookmark structure of your current PDF to split it into more manageable sizes. Even if you don’t have access to the document the PDF was created from there are other software programs available (including PDF Meld) to perform this function automatically. Doing this means users may need to download multiple smaller PDFs rather than a single large PDF containing everything they need.
Summary
Use PDF optimization when you have large PDFs (probably a couple megabytes or more) not to reduce their size but to make them display faster in a web browser. Optimization is only beneficial when you are making large PDFs available for viewing or download on a website. It will not help with other delivery methods such as email. Try using lower resolution images, font subsets to make the PDF physically smaller if you need to email or just want a smaller PDF. Lastly, you might want to split up a large PDF based on some logical grouping such as bookmarks to create multiple smaller PDFs.