P0133 Code: Slow O2 Sensor Response (Bank 1 Sensor 1)
P0133 Code: O2 Sensor Slow Response Fix. See symptoms, common causes, driving risk and checks that help confirm the fault before parts are replaced.

Save all codes and freeze-frame data. The code tells you what the control module detected, not which component must be replaced.
Quick answer
Code P0133 indicates that the upstream oxygen sensor on Bank 1 (Sensor 1) is responding too slowly to changes in the air-fuel mixture. The engine control module (ECM) detects this lag when the sensor's voltage output fails to switch between rich and lean states within the expected time frame.
Why the P0133 Code Means Slow Response in Bank 1 Sensor 1
The P0133 code is triggered when the ECM monitors the oxygen sensor's ability to react to fuel mixture changes and finds it sluggish. Bank 1 Sensor 1 refers to the first oxygen sensor in the exhaust stream before the catalytic converter on the engine bank that contains cylinder #1. This sensor plays a critical role in closed-loop fuel control, providing real-time feedback to the ECM so it can adjust the air-fuel ratio for optimal combustion and emissions.
During closed-loop operation, the ECM periodically enriches and leans the fuel mixture to test the sensor's responsiveness. A properly functioning O2 sensor should toggle its voltage output between ~0.1V (lean) and ~0.9V (rich) within approximately 100-200 milliseconds. If the sensor's transition time exceeds the programmed threshold; often around 300-600 milliseconds depending on the vehicle; the ECM logs P0133. This slow response typically stems from internal degradation of the sensor's zirconia element, contamination from fuel additives or oil ash, or electrical issues like poor grounding or damaged wiring.
In most cases, the slow response is due to an aging sensor. Oxygen sensors degrade over time as their internal components become coated or chemically altered, reducing their ability to generate voltage quickly. Heat and vibration also contribute to wear, and sensors older than 60,000-100,000 miles are prime suspects. However, the code can also appear if the sensor is new but the heater circuit is malfunctioning, preventing it from reaching the ~600°F operating temperature needed for accurate readings. Less commonly, exhaust leaks near the sensor or excessive fuel additives (like silicone from certain gasket sealers) can foul the sensor tip, causing the same slow reaction.
The ECM uses a specific diagnostic routine to confirm the slow response. It may run this test during steady cruising or after a cold start, depending on the vehicle. If the sensor fails the test multiple times, the check engine light illuminates. Importantly, P0133 is distinct from codes like P0130 (sensor circuit malfunction) or P0131 (low voltage), as it specifically targets the sensor's reaction time, not its signal integrity or range.
Common Symptoms of the P0133 Code
Drivers often notice poor fuel economy as the ECM struggles to maintain the correct air-fuel ratio. A rough or unstable idle may occur because the slow sensor feedback causes inconsistent fuel delivery. Under acceleration, the engine might hesitate or lack power as the ECM can't adjust quickly enough to demand changes. See the full P0133 repair cost guide for a detailed breakdown.
Typical Fixes for the P0133 Code
Replacing the Bank 1 Sensor 1 oxygen sensor is the most common repair, as the sensor itself is usually the culprit. However, the wiring harness and connector should be inspected for damage or corrosion before replacement. In some cases, cleaning the sensor or addressing an exhaust leak near the sensor can resolve the issue. Repairs typically range from $150 to $1,000+ depending on the cause.
Can You Still Drive With Code P0133?
Yes, you can usually continue driving with P0133, but it's not advisable long-term. The vehicle may run poorly, waste fuel, and risk damaging the catalytic converter over time due to an improper air-fuel mixture. Addressing the issue promptly prevents more costly repairs.
Details that improve the diagnosis
Compare the reported value with engine temperature, barometric pressure, throttle position and related sensors. A signal that is electrically valid can still be implausible. Fuel trims at idle and at a steady higher speed help separate an intake leak from a fuel-delivery or measurement problem.
Before clearing anything, record whether the code is current, pending, history or permanent. Save companion codes and freeze-frame conditions, then note recent repairs, a weak battery, weather changes and the exact moment the symptom appears. After a confirmed repair, clear only the erasable codes and complete the appropriate drive cycle. A permanent code normally clears only after the onboard monitor verifies that the fault is gone.
Related trouble codes
Information to record before any repair
Write down the exact code, its status and every companion code reported by a complete vehicle scan. Save the freeze-frame values, including engine speed, load, coolant temperature, vehicle speed, battery voltage and fuel trims when available. Note whether the warning appeared during a cold start, at idle, under acceleration, after refueling, in wet weather or immediately after other work. These details help separate an intermittent electrical problem from a repeatable mechanical or operating-condition fault.
Identify the exact year, make, model, engine, transmission and market version before using a wiring diagram or specification. Connector pinouts, monitor thresholds, component locations and test procedures can change within the same model line. Check current manufacturer service information and relevant technical service bulletins. A bulletin can improve the test sequence, but it should not be treated as proof that the same fault exists on every vehicle.
How to verify the repair
A warning light that stays off immediately after codes are cleared does not by itself confirm a repair. Recheck live data, repeat the operating condition that originally set the code when it is safe to do so, and confirm that no pending code returns. Some monitors need a specific drive cycle before they run. Permanent codes are normally removed by the control module only after it sees enough successful monitor results. If symptoms remain or the code returns, continue testing instead of replacing another part by guesswork.