"My server is lagging" can mean a dozen different underlying problems, and applying a random fix without knowing which one you have wastes time and sometimes makes things worse. This is the diagnostic starting point, figuring out what is actually wrong, before jumping to a specific fix.
Step 1: Check TPS and MSPT first
These two numbers are where every diagnosis should start. On Paper, run /tps to see your ticks-per-second average over the last 1, 5, and 15 minutes, 20.0 is perfect, anything meaningfully lower means the server cannot keep up. Spark, the standard profiling tool, gives a more precise picture with /spark tps and /spark health, MSPT (milliseconds per tick) in particular tends to be the more reliable number, since TPS can occasionally show close to 20 even when individual ticks are struggling. We cover the distinction in detail in our low TPS and high MSPT guides.
Step 2: Narrow down where the time is going
Once you know the server is genuinely struggling, the next question is which part. A spark profiler report (/spark profiler start, let it run for a minute or two under normal load, then /spark profiler stop) breaks down exactly which plugins, mods, or vanilla systems are consuming tick time, this is the single most useful step in the whole process, since guessing is far slower than reading a report that names the actual culprit.
Step 3: Check the usual suspects
If you want a faster first pass before running a full profile, these are the most common causes in rough order of likelihood:
- Too many entities. Mob farms, item drop pileups, and villager breeding left unchecked. See our entity lag guide.
- View distance and simulation distance set too high. Both default to 10 in
server.properties, and each additional chunk costs real CPU. See our chunk lag guide. - Not enough RAM, or too much. Both cause different symptoms. See using too much RAM.
- A single CPU core maxed out. Minecraft's main tick loop is single-threaded, so core count matters less than single-core speed. See high CPU usage.
- Garbage collection pauses. Periodic freezes rather than constant slowness point here. See GC lag.
- A poorly optimized plugin. Spark's profiler report will name it directly if this is the cause.
Step 4: Check if it's actually the server
Before assuming the server itself is the problem, rule out network issues, a player's own connection lag looks identical to server-side lag from their perspective, but only affects them. If every player is affected simultaneously, the server is the more likely cause.
Once you know the cause
Our general lag-fixing guide covers the most impactful fixes across all of these categories, and each specific cause above links to a dedicated guide with details on that one issue.
Getting a server built for headroom
A RAM calculator and server requirements tool can confirm whether your current plan actually matches what your world and player count need. Tick Hosting's plans are sized with real headroom in mind, starting with a free tier. Get started on Tick Hosting's plans page.