What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To reduce input lag on Linux, first find which part of the input-to-screen path is slow: the device and kernel, input driver, display server or compositor, application, rendering, or display presentation. Then adjust a setting supported by the component actually handling your session and compare one change at a time under the same workload. Wayland is not automatically faster than X.Org, and the available architecture documentation does not establish a universal latency winner.
How do I reduce input lag on Linux?
Input delay is a chain, not a single switch. A device produces an event; the kernel makes it available; input software and the display system route it; the application responds and renders; and the compositor or display server presents the result. A slowdown or delay at any of these stages can affect how responsive the system feels. The architecture documentation describes these stages but does not assign a universal latency budget to them.
As an Amazon Associate I earn from qualifying purchases.
- Identify your session and application path. Determine whether the desktop session is Wayland or X.Org, which compositor is active, and whether the application itself is native Wayland or running through XWayland. Those are distinct paths even within a Wayland desktop.
- Identify the input path. Find out which driver handles the device and whether the compositor or X.Org is using libinput. The name of the display session alone does not tell you which settings are available.
- Check the relevant component’s documentation. Use the desktop or compositor’s supported controls on Wayland; on X.Org, check the active input driver and its configuration tools. Do not assume every libinput option can be set in every environment.
- Change one thing and compare. Keep the application, display mode, and workload the same. Record the symptom and the setting changed, then revert it if the result is worse or inconclusive.
- Follow the symptom to its likely stage. If the issue appears only in one application or under load, investigate that application’s rendering or the relevant server/compositor behavior before changing unrelated device settings or kernel boot parameters.
There is no single measurement procedure established for every Linux setup in the official documentation cited here. Treat comparisons as specific to your own system rather than as a general benchmark of Wayland or X.Org.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Is Wayland or X.Org faster for gaming?
The architecture differs, but that alone does not prove which will deliver lower input-to-screen delay in a particular game or on a particular machine. The Wayland project’s description of the display architectures is useful for understanding the paths involved, not for declaring a universal winner.
#1 Best Overall
- The next-generation optical HERO sensor delivers incredible performance and up to 10x the power efficiency over previous generations, with 400 IPS precision and up to 12,000 DPI sensitivity
- Ultra-fast LIGHTSPEED wireless technology gives you a lag-free gaming experience, delivering incredible responsiveness and reliability with 1 ms report rate for competition-level performance
- G305 wireless mouse boasts an incredible 250 hours of continuous gameplay on just 1 AA battery; switch to Endurance mode via Logitech G HUB software and extend battery life up to 9 months
- Wireless does not have to mean heavy, G305 lightweight mouse provides high maneuverability coming in at only 3.4 oz thanks to efficient lightweight mechanical design and ultra-efficient battery usage
- The durable, compact design with built-in nano receiver storage makes G305 not just a great portable desktop mouse, but also a great laptop travel companion, use with a gaming laptop and play anywhere
| Path | Documented event and display flow | What that does—and does not—tell you |
|---|---|---|
| Wayland | The kernel provides input events to the compositor. The compositor routes events to surfaces; the client updates its content; the compositor recomposites and schedules display output. | The compositor is central to event routing and composition. This description does not quantify the delay or establish that the path is always faster. |
| X.Org | The documented general flow sends kernel events to the X server, which dispatches them to clients. Client updates are rendered through the X server; a compositor may then recomposite, while X remains involved in front-buffer or page-flip handling in the described case. | X.Org’s server and any compositor are relevant parts of the path. The extra described stages do not prove a fixed or visibly worse delay on every system. |
| X11 application on a Wayland desktop | The application uses XWayland rather than the native Wayland client path. | Do not treat this as identical to either a native Wayland application or an X.Org session when comparing a game. |
For a useful comparison, keep the game, scene or workload, display mode, and other conditions consistent. Compare the actual native Wayland, XWayland, or X.Org path available to you, along with the active compositor and its presentation behavior. The reviewed official sources do not provide a controlled cross-hardware benchmark across those combinations, so architecture alone cannot settle the gaming question.
How do I reduce mouse latency on Wayland?
First confirm that the mouse is being handled by the compositor and identify the settings that compositor exposes. In a typical Wayland stack, the compositor uses libinput, but this is not mandatory for every compositor or configuration. A setting described by libinput may therefore be unavailable through a particular desktop’s controls.
Rank #2
- Pentakill, 5 DPI Levels - Geared with 5 redefinable DPI levels (default as: 500/1000/2000/3000/4000), easy to switch between different game needs. Dedicated demand of DPI options between 500-8000 is also available to be processed by software.
- Any Button is Reassignable - 11 programmable buttons are all editable with customizable tactical keybinds in whatever game or work you are engaging. 1 rapid fire + 2 side macro buttons offer you a better gaming and working experience.
- Comfort Grip with Details - The skin-friendly frosted coating is the main comfort grip of the mouse surface, which offers you the most enjoyable fingerprint-free tactility. The left side equipped with rubber texture strengthened the friction and made the mouse easier to control.
- 5 Decent Backlit Modes - Turn the backlit on and make some kills in your gaming battlefield. The hyped dynamic RGB backlit vibe will never let you down when decorating your gaming space, it would be better with other Redragon accessories with lights on.
- Fatigue Killer with Ergonomic Design - Solid frame with a streamlined and general claw-grip design offers a satisfying and comfortable gaming experience with less fatigue even though after hours of use.
Watch for the symptom’s pattern. If pointer response is poor everywhere, investigate the input device, driver, and compositor settings. If it happens only in a game or during heavy rendering, the application or presentation path may be more relevant than a mouse-specific setting. Compare changes under the same conditions so that a change in workload is not mistaken for a configuration improvement.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWhere do I change libinput settings?
libinput is an input stack for devices such as mice, keyboards, touchpads, touchscreens, and tablets. It does not store configuration for itself: the process using libinput chooses and applies options. Its overview describes its role; the FAQ explains the configuration boundary.
Rank #3
- The next-generation optical HERO sensor delivers incredible performance and up to 10x the power efficiency over previous generations, with 400 IPS precision and up to 12,000 DPI sensitivity
- Ultra-fast LIGHTSPEED wireless technology gives you a lag-free gaming experience, delivering incredible responsiveness and reliability with 1 ms report rate for competition-level performance
- G305 wireless mouse boasts an incredible 250 hours of continuous gameplay on just 1 AA battery; switch to Endurance mode via Logitech G HUB software and extend battery life up to 9 months
- Wireless does not have to mean heavy, G305 lightweight mouse provides high maneuverability coming in at only 3.4 oz thanks to efficient lightweight mechanical design and ultra-efficient battery usage
- The durable, compact design with built-in nano receiver storage makes G305 not just a great portable desktop mouse, but also a great laptop travel companion, use with a gaming laptop and play anywhere
- Wayland: Look in the desktop or compositor’s documented settings and configuration. The compositor commonly uses libinput directly, but the exact options depend on that caller.
- X.Org: If X.Org is using the xf86-input-libinput driver, configuration commonly comes through X.Org configuration snippets or runtime tools. Confirm the active driver and consult its documentation before applying a setting.
Do not assume that an option supported by libinput is exposed identically by every compositor or driver. Configuration paths and defaults can also vary by desktop version and Linux distribution.
What should I check in an X.Org session?
X.Org’s performance documentation identifies transport latency and round trips as important for some operations, and notes that slow server-side paths—including software rendering paths—can make the server feel laggy. These are reasons to investigate the workload and server behavior, not evidence that every X.Org session has worse input latency.
Rank #4
- The next-generation optical HERO sensor delivers incredible performance and up to 10x the power efficiency over previous generations, with 400 IPS precision and up to 12,000 DPI sensitivity
- Ultra-fast LIGHTSPEED wireless technology gives you a lag-free gaming experience, delivering incredible responsiveness and reliability with 1 ms report rate for competition-level performance
- G305 wireless mouse boasts an incredible 250 hours of continuous gameplay on just 1 AA battery; switch to Endurance mode via Logitech G HUB software and extend battery life up to 9 months
- Wireless does not have to mean heavy, G305 lightweight mouse provides high maneuverability coming in at only 3.4 oz thanks to efficient lightweight mechanical design and ultra-efficient battery usage
- The durable, compact design with built-in nano receiver storage makes G305 not just a great portable desktop mouse, but also a great laptop travel companion, use with a gaming laptop and play anywhere
The same documentation discusses unsynchronized drawing and tearing. A screen that looks uneven or torn may feel slow, but visual smoothness is not itself a measurement of end-to-end input-to-photon delay. Distinguish what you see from what you can compare consistently.
Free tools Windows power users keep installed
One-click scans. No signup required.
Are compositor latency settings interchangeable?
No. Controls belong to the compositor that implements them. For example, Canonical’s Mir configuration reference documents composite-delay, which controls how long Mir waits for new client frames before compositing. The reference gives a default of zero and states that higher values increase latency and can risk skipped frames. This is a Mir-specific example, not a setting or default to copy into Mutter, KWin, wlroots compositors, or other desktops.
Best Value
- HIGH-PRECISION 6,400 DPI OPTICAL SENSOR — Offers on-the-fly sensitivity adjustment through dedicated DPI buttons (reprogrammable) for gaming and creative work
- DURABLE MECHANICAL SWITCHES — Supports up to 10 million clicks
- RIDGED, RUBBERIZED SCROLL WHEEL FOR MAXIMUM ACCURACY — Small, tactile bumps increases grip and allows for more controlled scrolling in high-stakes gaming situations
- 5 PROGRAMMABLE BUTTONS — Allows for button remapping and assignment of complex macro functions through Razer Synapse
- PC GAMING PERIPHERALS BRAND IN THE U.S. — Source — Circana, Retail Tracking Service, U.S., Dollar Sales, Gaming Designed Mice, Keyboards, and PC Headsets, Jan. 2019- Dec. 2023 combined
Check the documentation for the compositor actually running your session, and change only controls it supports. A setting intended to alter frame scheduling may trade one behavior for another rather than simply making every input feel faster.
How should I compare two Linux display sessions?
When both sessions are available, compare the real combinations you use rather than labeling the result “Wayland versus X.Org” without qualification.
- Record the session type, compositor, and whether the application is native Wayland, XWayland, or running in X.Org.
- Keep the device and input-driver path in view, including whether libinput is used and which component applies its options.
- Use the same application, workload, display mode, and other relevant conditions for each comparison.
- Change one supported setting at a time, note the result, and restore the original value if the result is worse or unclear.
- If the symptom occurs only under load or in a particular application, focus on that path before making unrelated system-wide changes.
Official documentation supports the architectural and configuration distinctions above, but does not establish a universal latency ranking, a named general-purpose latency statistic, or one end-to-end test procedure for all hardware and software combinations.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
