# Bandwidth Transfer Limits and Port Speed Explained

- Link: https://offshorehosting.pk/bandwidth-transfer-limits-and-port-speed-explained/
- Published: 2026-10-25T10:27:00+00:00
- Author: admin

# Bandwidth Transfer Limits and Port Speed Explained

Two numbers on a hosting plan cause more confusion than any others: bandwidth and
port speed. They sound similar, they are both measured in bits, and providers do
not always explain them the same way. The result is predictable — a store owner 
buys a plan with a generous-looking number, then discovers at the end of the month
that the number measured the wrong thing.

This guide separates the two concepts, shows how to estimate what you actually need,
and explains what happens when you exceed a limit.

## Bandwidth vs port speed: the two different numbers

**Bandwidth (transfer allowance)** is a _volume_: how much data your server may 
send and receive in a billing period, usually a month. It is measured in gigabytes
or terabytes — for example, 2 TB per month. Every page, image, video, download, 
backup and API response counts toward it, in both directions unless the provider
says otherwise.

**Port speed** is a _rate_: how fast data may flow at any single moment. It is measured
in megabits or gigabits per second — for example, 100 Mbps or 1 Gbps. It is the 
width of the pipe, and it limits how quickly one visitor can download a large file,
and how many simultaneous visitors the server can serve at full speed.

A useful analogy: bandwidth is the total water your household may use in a month;
port speed is the diameter of the pipe into the house. A wide pipe does not help
if your monthly allowance is exhausted, and a large allowance does not help if the
pipe is so narrow that a single download takes minutes.

## What counts toward your transfer allowance

Almost everything that leaves or enters the server counts, unless the plan says 
otherwise. The main contributors are:

 * **Outbound traffic (egress):** pages, images, CSS, JavaScript, videos, downloads
   and API responses sent to visitors. This is usually the largest share.
    - **Backups and replication:** off-site backups and file sync all move data.
 * **Bots and crawlers:** search engines, monitors and scrapers all download your
   pages, using transfer beyond human visits.
 * **CDN origin traffic:** a CDN reduces what visitors pull from your origin, but
   the CDN still has to fetch content from the origin the first time, and dynamic
   pages usually bypass the cache entirely.

## How to estimate what you need

You do not need a precise forecast — a rough estimate with headroom is enough. Work
through it in three steps.

**Step 1: measure your average page weight.** Use your browser’s developer tools
or a speed test to find the total transferred size of a typical page, including 
images, CSS and JavaScript. A text-heavy page may be 500 KB; an image-heavy store
page may be 2–5 MB. Multiply by the number of pages a typical visit loads.

**Step 2: multiply by visits.** Monthly transfer ≈ average page weight × pages per
visit × visits per month. For example, 2 MB × 3 pages × 10,000 visits = 60 GB per
month for page traffic alone. Then add downloads, video, API traffic and backups.

**Step 3: add headroom.** Traffic is uneven. A sale, a viral post or a bot surge
can double a day’s usage. A common rule is to keep your typical usage below about
70% of the allowance, so a busy month does not push you over. If you are consistently
above that, it is time to move up a plan — or to reduce what you serve, for example
by optimising images and using a CDN.

## Port speed: what 100 Mbps, 1 Gbps and 10 Gbps actually mean

Port speed is shared in practice. A 1 Gbps port does not guarantee 1 Gbps to every
visitor at once; it is the maximum rate of the server’s network interface, shared
across all simultaneous connections. Still, the number matters:

  |  Port speed |  Rough maximum throughput |  Typical fit |  
   |  100 Mbps |  ~12.5 MB/s |  Small sites, low concurrency |  
 |  1 Gbps |  ~125 MB/s |  Most VPS workloads, busy stores, media sites |  
 |  10 Gbps |  ~1.25 GB/s |  Dedicated servers, heavy media, large concurrent load |

A single visitor downloading a 100 MB file on a 100 Mbps port waits at least 8 seconds
at full speed, and longer in practice. On a 1 Gbps port, the same download takes
under a second in theory. For web pages, the difference is less dramatic — a 2 MB
page downloads in well under a second even at 100 Mbps — but when dozens of visitors
arrive at once, a narrow port becomes a queue, and pages slow down for everyone.

## What happens when you exceed a limit

Providers handle overages in different ways, and the difference matters more than
the price of the overage itself:

 * **Overage billing:** you are charged per additional GB or TB. Check the per-unit
   price before you need it — it is often higher than the cost of the next plan 
   up.
 * **Throttling:** your port speed is reduced for the rest of the billing period.
   The site stays up, but everything is slower, which is painful during a sale.
 * **Suspension or blocking:** in the strictest case, the server is suspended or
   traffic is blocked until you upgrade or the month resets. This is rare on reputable
   VPS plans but it exists, so confirm the policy in writing.
 * **Automatic upgrade:** some providers move you to the next tier automatically.
   Convenient, but it changes your bill without a decision from you.

The practical defence is monitoring. Set an alert at 70% and 90% of your allowance,
and check the trend weekly during busy periods. An alert is cheap; discovering an
overage from a throttled checkout is not. [TO BE CONFIRMED: Offshore Hosting’s bandwidth
overage policy, whether ingress is metered, and what alerting is available on VPS
plans.]

## How to reduce transfer without reducing service

Before paying for a bigger allowance, check whether you are serving more data than
you need to:

 1. **Optimise images.** Compress them, serve modern formats, and size them to the 
    display size. Images are usually the largest part of a page.
 2. **Use a CDN.** A CDN serves cached static content from edge locations close to 
    visitors, so your origin sends each file once instead of once per visitor. Dynamic
    pages still come from your server, but the static majority does not.
 3. **Enable compression.** Gzip or Brotli compression on text (HTML, CSS, JavaScript)
    typically cuts transfer by more than half.
 4. **Set sensible cache headers.** Returning visitors should reuse cached files instead
    of downloading them again.
 5. **Block abusive bots.** A robots.txt file, rate limiting, or a firewall rule can
    cut bot transfer sharply. Check your access logs first — do not block search engines
    by accident.
 6. **Do not serve video from the origin if you can avoid it.** Host video on a dedicated
    video platform or a CDN designed for it; video dominates transfer budgets.

These steps also improve speed, which is why they appear in our checkout and performance
guides. See [How to Keep WooCommerce Checkout Fast](https://offshorehosting.pk/blog/how-to-keep-woocommerce-checkout-fast/)
for the store-specific version.

## Location, latency and the speed of light

Port speed is not the same as latency. Latency is the round-trip time for a request,
and it is bounded by distance and the speed of light through fibre. A visitor far
from your server will always wait longer for the first byte, however wide the port
is. That is why data-centre location matters alongside bandwidth: a fast port in
the wrong region still feels slow to your actual audience. Cloudflare’s network,
for example, is designed so that most of the world’s connected population is within
about 50 ms of one of its data centres — the point being that proximity, not just
raw speed, shapes the experience. Read [How to Choose a Data Center Location](https://offshorehosting.pk/blog/how-to-choose-a-data-center-location/)
before you choose a region on bandwidth alone.

## Questions to ask before you choose a plan

 * Is the allowance for outbound traffic only, or inbound too?
 * What is the port speed, and is it dedicated, shared, or burstable?
 * What happens on overage — billing, throttling, or suspension — and at what rate?
 * Is there a usage dashboard and can I set alerts at 70% and 90%?
 * Does traffic between my own servers, or to the provider’s backup service, count?
 * Is there a fair-use policy that overrides the headline allowance?

If a provider cannot answer those questions clearly, treat the headline number with
caution.

## The bottom line

Bandwidth is how much you may move; port speed is how fast you may move it. Estimate
your real usage from page weight and visits, leave headroom, monitor the trend, 
and reduce waste with images, compression and a CDN before you pay for more. A plan
that fits your actual traffic pattern is worth more than a plan with the biggest
number on the page.

For a server with room to grow, see our [VPS hosting](https://offshorehosting.pk/vps-hosting/)
plans. [TO BE CONFIRMED: bandwidth allowances and port speeds for each Offshore 
Hosting VPS plan.]

## Sources

 * Cloudflare — Smart Placement speeds up applications by moving code close to your
   backend: https://blog.cloudflare.com/announcing-workers-smart-placement/
 * The Internet Papers — CDN Architecture: Why Cloudflare, CloudFront, Akamai, and
   Fastly Are Actually Running the Internet: https://www.theinternetpapers.com/posts/
   cdn-architecture-cloudflare-cloudfront-akamai-fastly-cdn-architecture-why-cloudflare-
   cloudfront-akamai-and-fastly-are-actually-running-the-internet.html
 * Punits Dev — Think Cloudflare Always Speeds You Up? Not in India: http://punits.
   dev/blog/cloudflare-latency-india/
 * GigeNET — NVMe vs SATA SSD speed: 2026 numbers: https://www.gigenet.com/blog/
   nvme-vs-sata-ssd-speed-comparison/

## Sources

 * https://blog.cloudflare.com/announcing-workers-smart-placement/
 * https://www.theinternetpapers.com/posts/cdn-architecture-cloudflare-cloudfront-
   akamai-fastly-cdn-architecture-why-cloudflare-cloudfront-akamai-and-fastly-are-
   actually-running-the-internet.html
 * http://punits.dev/blog/cloudflare-latency-india/
 * https://www.gigenet.com/blog/nvme-vs-sata-ssd-speed-comparison/