Understanding the Types of Lag on Your Minecraft Server (TPS, Network, Client)

Learn the difference between server TPS lag, network ping lag, and client FPS lag on your Minecraft Java server — and how to diagnose each.

"Lag" on Minecraft can mean three completely different things, each with a completely different fix. Knowing which type you have saves hours of pointless troubleshooting.

Type	Where it happens	Affects	How to spot it
Server lag (TPS)	The server	Everyone	All players see delay at the same time
Network lag (ping)	Between player and server	Individuals	Only some players lag — others are fine
Client lag (FPS)	Player's PC	Individuals	Choppy visuals but server actions work normally

Server Lag (Low TPS)

What it is

The server can't process all the work that fits in a 20-tick-per-second budget. Each tick should take 50 ms or less; when it takes longer, TPS drops below 20 and the world slows down.

Symptoms

Block placing/breaking has a delay
Mobs walk in slow motion
Chat messages take seconds to appear
Item drops freeze in place
All players experience it at the same time

TPS Reference

TPS	MSPT	Status	Players notice?
20.0	<50	Perfect	No
19–20	50–55	Good	No
17–19	55–65	OK	Barely
14–17	65–80	Noticeable lag	Yes
10–14	80–100	Significant lag	Yes — complaints start
<10	>100	Severe — nearly unplayable	Yes — players leave

Common Causes

Cause	How common
Too many entities (mob farms)	Very common
Chunk generation from exploration	Very common
High view-distance/simulation-distance	Very common
Heavy redstone	Common
Bad plugin or mod	Common
Insufficient RAM (GC pauses)	Common
World corruption	Occasional

Diagnosis

Run /spark tps to confirm TPS is low
Run /spark profiler start, wait 2–5 minutes, then /spark profiler stop
Read the flame graph — the widest bars are your culprit
See Setup Spark for details

Fix

Optimize Server — full performance guide
JVM Flags — Aikar's flags
Render Distance — biggest single lever
Pre-generate Chunks — eliminate exploration lag
Server Tick Loop — for "Can't keep up"

Network Lag (High Ping)

What it is

Slow or unstable connection between an individual player and the server. The server is fine — the player's packets are taking too long to arrive.

Symptoms

Delayed actions
Rubber-banding back to a previous position
Block breaks reset and have to be redone
Only affects specific players — others connect fine

Common Causes

Cause	Who it affects
Player far from the server geographically	One player or one region
Player on Wi-Fi instead of Ethernet	One player
Player's ISP routing through congested peers	One player
Player on mobile data / hotspot	One player
Server bandwidth saturation	Everyone (rare)
Datacenter network issue	Everyone (rare)

Diagnosis

In-game, run:

/list

Or with Spark:

/spark ping

This shows ping per player. If only some players have high ping, the issue is on their end. If everyone has high ping, the server's network is the problem.

Fix

Player side: switch to Ethernet, change DNS to 1.1.1.1, contact ISP
Server side: usually nothing to do unless it's a datacenter issue
Datacenter side: choose a host location closer to your community

Choppy visuals, stuttering
Game feels slow
Mouse input feels delayed
Server actions (block placing, mob behavior) are normal — only the rendering is choppy
Only affects one player

Diagnosis

Have the player press F3 in Minecraft. The top-right shows their FPS:

FPS	Status
60+	Smooth
30–60	OK
15–30	Noticeable lag
<15	Severe

If their FPS is low but the server's /spark tps is 20.0, it's a client issue.

Fix

These are all client-side, not server changes:

Lower client render distance (Settings → Video Settings)
Lower graphics quality
Install Sodium (Fabric) or Embeddium (Forge) for better FPS
Disable shaders
Allocate more RAM to the Minecraft launcher
Update GPU drivers
Close other apps

Quick Diagnosis Flowchart

Players reporting lag.
        │
        ▼
Does EVERYONE lag at the same time?
   │              │
  YES             NO
   │              │
   ▼              ▼
Server lag    Does ONE player lag?
(check TPS)        │              │
                  YES             NO
                   │              │
                   ▼              ▼
            Network or client    Many players lag
            (check their FPS     (server lag — check TPS)
             and ping)

Common Mistakes

Mistake	Fix
Treating client FPS lag as a server issue	Have the player check F3 first
Adding RAM to fix network lag	RAM doesn't fix ping — it's a network issue
Ignoring "Can't keep up" warnings	They mean TPS is dropping — investigate
Assuming all lag is the same	Diagnose first, fix second
Lowering view-distance for one laggy player	Won't help — that's a client issue

Understanding the Types of Lag on Your Minecraft Server (TPS, Network, Client)

Server Lag (Low TPS)

What it is

Symptoms

TPS Reference

Common Causes

Diagnosis

Fix

Network Lag (High Ping)

What it is

Symptoms

Common Causes

Diagnosis

Fix

Client Lag (Low FPS)

What it is

Symptoms

Diagnosis

Fix

Quick Diagnosis Flowchart

Common Mistakes

On this page