Response Time Test
Inspect visible ghosting, overshoot, and motion clarity with browser-rendered moving patterns.
This check opens a focused test surface. You can return with Escape. Review what this browser test can and cannot measure.
Before you start
- Confirm the intended refresh rate, display mode, and overdrive setting.
- Use 100% browser zoom and keep those settings fixed between observations.
How to run this check
- Start the Response Time Test
- Choose a motion pattern such as UFO, Moving Squares, Strobe, or Pursuit
- Adjust the speed and follow the moving object with your eyes
- Note visible blur, dark trails, or bright overshoot halos
- Repeat under the same browser, display, and overdrive settings before comparing observations
What this browser test can tell you
Can help you check
- Visible ghosting, overshoot, and motion clarity with moving patterns.
Cannot measure
- This test cannot produce a panel response-time value in milliseconds.
Setup, interpretation, and sources
Recommended setup
- Let the display warm up and use its normal gaming or motion setting.
- Keep the browser visible and compare several motion speeds.
How to interpret what you see
- Record the speed and background where trails, bright halos, or blur become noticeable.
- Browser frame cadence, operating-system compositing, refresh rate, scaling, and display overdrive settings can all change the visible motion.
- Exact pixel transition timing requires a photodiode and oscilloscope or equivalent lab equipment.
Sources
Methodology reviewed:
💡 Why This Test?
This test supplies moving patterns that make visible blur, trailing, and bright overshoot halos easier to observe while you follow the object with your eyes. It records which patterns and speeds you reviewed, but it cannot convert that visual observation into a panel response-time value in milliseconds.
✅ What You'll Check:
- Motion blur (smearing behind moving objects)
- Ghosting (faint trailing copies of objects)
- Overshoot/inverse ghosting (bright halos around objects)
- Color transition speed (white, red, green, blue)
- Overall motion clarity at different speeds
📖 How to Use This Test
- Start the test in fullscreen for best visibility
- Begin with UFO test mode to check classic motion blur
- Adjust speed slider to test different motion speeds
- Follow the moving objects with your eyes (pursuit tracking)
- Look for trails, halos, or blurring behind/around objects
- Try all test modes: UFO, Moving Squares, Strobe, and Pursuit
- Test with different overdrive settings if available on your monitor
Tip: If you see bright halos, compare a lower overdrive setting. Keep browser zoom, operating-system scaling, refresh rate, and display mode unchanged between observations.
Inspect motion clarity in fullscreen; this pattern does not calculate milliseconds.
👁️ What You're Looking For
Clean Motion Example
Clean, sharp edges with no trailing artifacts
❌ Motion Blur (Slow Response)
Smeared, blurry edges indicate slow pixel transitions
⚠️ Ghosting (Overshoot)
Faint copies following the moving object
⚡ Overshoot (Too Fast)
Bright halos or inverse ghosting around objects
⏱️ Response Time Guide
🎮 Test Modes
- ● UFO: Classic motion blur test
- ● Squares: Color transition test
- ● Strobe: Flicker and persistence test
- ● Pursuit: Eye-tracking motion test
🔍 Quick Tips
- • Test at different speeds for detail
- • Try overdrive settings if available
- • Compare light and dark objects
- • Test in darkened room for visibility
📋 How to Test
Start Fullscreen Test
Click the test button and enable fullscreen for accurate motion assessment.
Choose Test Mode
Start with UFO test for classic motion blur, then try other modes for comprehensive testing.
Adjust Speed
Test at different speeds. Slow motion reveals more detail, fast motion tests real-world gaming.
Watch Moving Objects
Follow objects with your eyes and look for blur, ghosting, or trailing artifacts.
Test Different Settings
If your monitor has overdrive settings, try different levels to find the optimal balance.
📊 Understanding Results
No obvious trail noted
- • Sharp, clean motion
- • No visible ghosting
- • Minimal blur
- • Record the tested speed and mode
Minor trail noted
- • Acceptable clarity
- • Minor ghosting
- • Some blur at speed
- • Compare the same settings again
Obvious trail or halo noted
- • Significant blur
- • Visible trails
- • Strong overshoot
- • Compare display overdrive modes
🔧 Common Issues & Solutions
👻 "The motion pattern shows multiple trailing copies"
What you observed: The moving object left visible dark or repeated trails under the current test conditions. Browser frame cadence, operating-system compositing, refresh rate, scaling, eye tracking or camera capture, display processing, and overdrive settings can all affect the appearance.
How to interpret it: Record the pattern, speed, background, refresh setting, and whether you viewed it directly or through a camera. This browser observation cannot assign a GtG value in milliseconds or diagnose an inherently slow panel.
✅ Next step: Compare one display preset or overdrive setting at a time while keeping the browser, refresh rate, motion speed, and viewing method unchanged. Use instrumented measurements when a numeric response time is required.
⚡ "Bright white/colored halos around moving objects (inverse ghosting)"
What you observed: A bright or colored halo appeared around the moving object under the current settings. Browser cadence, refresh behavior, viewing or capture method, display processing, and overdrive settings can all influence the appearance.
How to compare: Record the pattern speed, refresh setting, display preset, and whether the halo was seen directly or through a camera. The page cannot measure overshoot percentage or isolate one hardware cause.
✅ Next step: Compare one supported display or overdrive preset at a time while keeping all other conditions fixed. Use instrumented testing for numeric overshoot analysis.
🌫️ "Motion still looks blurry under the current settings"
What you observed: The moving object appeared smeared while your eyes followed it. Browser frame cadence, refresh setting, motion speed, eye tracking, capture method, scaling, and display processing can all affect perceived clarity.
How to compare: Record the refresh setting, pattern speed, display preset, and viewing method, then repeat with one variable changed. This observation cannot separate pixel transitions from eye-tracking or frame-presentation effects.
✅ Next step: Compare supported refresh and display modes under identical content and room conditions. Use a controlled pursuit-camera or instrumented method when quantitative motion clarity is required.
🔦 "A display motion mode looks flickery or uncomfortable"
What you observed: Flicker, double images, discomfort, or a brightness change appeared with a display motion mode enabled. Mode implementation, refresh setting, content, sensitivity, camera capture, and display processing can affect the result.
How to compare: Record the motion mode, refresh setting, brightness, and whether you viewed directly or through a camera. This browser page cannot measure flicker frequency, duty cycle, crosstalk, or safety.
✅ Next step: Stop using a mode that causes discomfort and follow the display manufacturer's guidance. Use camera-assisted or instrumented flicker testing when a measurement is needed.
🎨 "Dark scenes show purple, green, or brown trails" (Dark-background observation)
What you observed: Moving objects left colored or dark trails against a dark background under the current settings. Browser frame cadence, refresh behavior, color management, scaling, direct viewing or camera capture, display processing, and overdrive can all change their appearance.
How to compare: Record the background, pattern speed, refresh setting, display preset, and viewing method. This browser pattern cannot assign transition milliseconds, identify panel technology, or diagnose a hardware limitation.
✅ Next step: Compare one display or overdrive preset at a time while keeping the browser, refresh rate, motion speed, and viewing method fixed. Use instrumented testing when numeric transition timing is required.