Minecraft server lag is really three separate problems. Low ticks per second means the server cannot complete a game tick inside fifty milliseconds, which is usually caused by entity counts, badly behaved plugins or insufficient single thread CPU performance. High ping is a network problem determined mostly by physical distance between the player and the datacenter, and no server side configuration change can recover latency lost to geography. Chunk lag appears as terrain loading slowly while travelling and is driven by storage throughput and view distance. Diagnosis comes first: the tps command on Paper, the tick query command on recent vanilla versions, and the Spark profiler for per plugin tick attribution. Common fixes include lowering view distance from twelve to eight, reducing simulation distance, capping per chunk mob counts, throttling hopper transfers, pre generating the world inside a border, and migrating from vanilla to Paper. When the profile is clean and the heap has headroom but tick times remain high, the remaining bottleneck is hardware, and a higher clocked CPU core with fast SSD backed storage is the real fix.