<p>I am using SQL Server Reporting Services 2008 (though this seems to be an issue for me in 2005 also).  I have a report that has one page per customer (i.e. paged on customerId).  The odd thing I'm seeing is that the first report (i.e. first page of the report) has a bit of extra white space at the top than the other pages.  In general this seems to occur when you have a title for the report and paging (so that the first page has the title, but each successive page does not).  The report I'm dealing with does not have a title like that, but still has this extra white space.</p>

<p>What I'm wondering is how do I prevent that extra white space on this first page of the report.  How do I make each page of the report identical?</p>

<p>I do not have a header or footer applied to the report either.</p>

There are a couple of different causes for extra space at the top of the HTML render of a page in any version of Reporting Services.  There are a couple of tricks to working around this depending upon the cause of the problem:
Move the title from the Header to the Body of the report.  If the title is a label, this doesn't always help.
If you are using a table, then add a separate row to the header of the table.  This seems to work very well, particularly when you render to Excel.  However, not all report requirements can support this as a solution.
In SSRS 2000/2005, if you are using a container such as a rectangle or group, then the odds that you will having a spacing issue increase.  If you can move the title out of the container, then this can help reduce the likelihood of a problem.  I haven't tried using the Tablix grouping controls in SSRS 2008, so I can't tell if this will work in SSRS 2008.
If you keep the header and footer objects on even you aren't adding any labels to the regions, then these can lead to extra spaces on the first page.
It is difficult to give you better advice without reproducing your exact problem.  If you want to post the code for a sample RDL file temporarily, then I can try to reproduce the problem in SSRS 2008 on my machine and see if I can provide you with a custom solution to your problem.