NCS Logo - Click for home page Northstar Developer Center
Platforms
All Platforms
.NET Framework (1.x - 4.x)
Active Server Pages
ASP.NET
C#
SQL Server
VB.NET
Visual Basic

Keywords
.NET Data Types
.NET E-mail
.NET Events
.NET Functions
.NET Object Programming
.NET System.Configuration
.NET System.Diagnostics
.NET System.IO
.NET System.Net
.NET System.Net.Sockets
Active Data Objects
ASP Architecture
ASP Black Belt
ASP Built-in Functions
ASP Built-in Objects
ASP Debugging
ASP Performance
ASP Security
ASP Syntax
ASP.NET Authentication
ASP.NET Controls
ASP.NET Data Access
ASP.NET Features
ASP.NET Master Pages
ASP.NET Page Events
ASP.NET Security
ASP.NET ViewState
Atom
Certifications
COM, DCOM, COM+
Data Access
E-Mail
Errors
Exporting Data
HTML Tips
IIS
Object-Oriented Programming
RSS
SQL
Uncategorized ASP Tips
VB API Programming
VB Forms
VB Syntax
XML

Book Support
Visual Basic 6 Bible
ASP Bible
ASP Weekend Crash Course
ASP.NET At Work
Creating Web Services

Page Size Issues

Written by Eric Smith, Northstar Computer Systems LLC

When we were all learning how to make good web sites, one of the rules of thumb was that a page should be less than 30kb, which translates to approximately 15 seconds to download on a 28.8 Kb modem. While bandwidths have slowly gotten bigger, this is still a good rule of thumb. For your ASP applications, not only do you have to worry about the graphics, but you also have to worry about how much data is being sent to the user’s browser. You can get the download size by saving the resulting HTML locally and getting the disk size of the file. Add the graphics to the text and you have your whole download size. This means that if your file is too big, you should work in some paging logic to reduce the download time. Text data takes just as long to download as graphic data does, so remember that when you’re planning your sites.

Keywords: [ Uncategorized ASP Tips ]

Publication Date: 3/1/2000