Sensors and circuits

P0133Oxygen sensor slow response, bank 1 sensor 1

O2 Sensor Circuit Slow Response Bank 1 Sensor 1

Get it diagnosed soon

Generic OBD-II code

Oxygen (O2/A:F) Sensor

What this part does

Measures exhaust oxygen content so the control module can trim fuel delivery to maintain the target air-fuel ratio.

What the computer is measuring

This code is not about the sensor’s readings being wrong. It is about them being late.

In closed loop the computer runs a continuous cycle. It pushes the mixture slightly rich, waits for the sensor to confirm that it went rich, then pushes lean, waits for confirmation, and repeats. The speed of that loop is set by how quickly the sensor answers. A new sensor turns around in well under a tenth of a second, which lets the mixture oscillate around the correct point several times every second.

As a sensor ages the element responds more sluggishly. The loop slows down, and the mixture spends longer on each side of the target before the correction arrives. The average is still roughly right, which is why the car drives normally, but the excursions are bigger and last longer.

The computer measures this directly. It times the transitions and compares them with a limit, and P0133 is what happens when the sensor is consistently too slow.

Why this one is worth fixing promptly

A catalytic converter works on a narrow band of mixture, and it depends on the fuelling swinging quickly across that band rather than wandering slowly around it. A slow sensor means longer rich excursions, and unburnt fuel arriving at a hot converter is what destroys converters.

So a slow sensor left in place tends to be followed by a catalyst efficiency code, and the sensor is a fraction of the cost of the converter. Of all the oxygen sensor codes, this is the one where acting early actually saves money.

What you will notice

  • Check engine light on, usually with no complaint about how the car drives.
  • A gradual drop in fuel economy over the months before the light came on.
  • An emissions test failure, both on the monitor and sometimes on the tailpipe numbers.
  • A catalyst efficiency code appearing weeks or months later if it is left alone.

Likely causes, most common first

Ordered by how often each one actually turns out to be the problem, not alphabetically and not by part price.

  1. An aged sensor that has simply slowed down

    The most common cause. Response time degrades gradually with mileage and heat, and this code is usually the first sign that a sensor is at the end of its life.

  2. Contamination of the sensor element

    Silicone from the wrong sealant, oil from worn valve seals or coolant from a weeping gasket all coat the element and blunt its response.

  3. An exhaust leak upstream of the sensor

    Air drawn in between pulses dilutes the sample, so the transitions the sensor sees are smaller and softer than the ones the engine is actually producing.

  4. A failing sensor heater

    A sensor that never gets fully up to temperature responds slowly by definition. A heater code alongside this one settles it.

  5. Low fuel pressure or a lazy fuel delivery response

    If the mixture itself is changing slowly, the sensor reports that faithfully and takes the blame for it.

  6. Resistance in the signal or ground circuit

    Corroded pins add resistance, which softens the signal edges the computer is timing.

What to check, in order

  1. Hold the engine at about 2500 rpm warm and count how many times the sensor crosses the middle of its range in ten seconds.

    A healthy upstream sensor crosses roughly once a second or faster. Noticeably fewer crossings than that confirms the code rather than just repeating it.

  2. Compare the upstream sensor trace with the downstream one on the same bank.

    The downstream sensor should be slow and nearly flat. An upstream sensor that has started to look like the downstream one has lost its response.

  3. Check whether a heater circuit code is stored as well.

    A heater fault alongside this explains the slow response and is the thing to fix first. No heater code leaves the element itself, the wiring or the exhaust.

  4. Inspect the manifold and the joints ahead of the sensor for leaks.

    A leak found here dilutes every sample the sensor takes and can produce this code with a perfectly good sensor.

  5. Force the mixture rich briefly, by adding a little propane at the intake, and time how long the sensor takes to react.

    A prompt swing to the rich end means the sensor can still respond and something else is slowing the mixture down. A lazy climb confirms the sensor.

Where this one turns up most

  • Vehicles between a hundred and a hundred and fifty thousand miles on original sensors, which is where response time usually falls off.
  • Engines that burn a little oil, where the element is being coated continuously.

Codes that often show up alongside it

What a DriveDecode adapter can read

A DriveDecode adapter reads engine and emissions systems: the powertrain and emissions codes the OBD-II standard requires on every US vehicle it covers. It does not read ABS, airbag (SRS), TPMS or transmission-specific manufacturer codes. Those need make-specific decoding that generic OBD-II hardware cannot do.

Reading P0133 on your own car

DriveDecode pulls P0133 straight off the vehicle along with the freeze frame the computer stored when it set: the coolant temperature, engine load and speed at that exact moment. That context is what separates a fault that happens on a cold start from one that happens under load, and it is the first thing the list above asks you to narrow down.

See how DriveDecode works

Last reviewed 2026-09-08. Definition sourced from the published standard.