If traffic is really bad, a left turn can sometimes actually be slower then right + uturn.
I will check what routing times are and post some examples.

Send from my S7 with Tapatalk.

As mentioned, Left turns simply can be really slow, especially in rush hour. Sometimes a right turn + uturn is faster than just a left turn.

With routespeeds script you can analyse this, and have the average speed per segment displayed. Now as you can see in the example, the segment before the left turn has an average speed of 1 km/h. That's causeing this detour to be faster, according to Waze.

Sometimes it's really true, and sometimes there's not enough data for the right-turn-detour for Waze to "know" it's wrong. So the advice I always give, is to follow Waze. It's a win-win situation
IF Waze was right, you're faster!
IF Waze was wrong, you're learning Waze that the detour is actually slower, and in the future your speed data will be helping Waze to improve it's routing.

The second Example is different.
The left turn is slow but also the detour is very slow.
What I do know, is that this junction is mapped against ALL rules. Ramps are WAAAAAY too long, the segments in the middle of the junction are cut into little pieces.
Shift+Z shows me RED TR arrows where they shouldn't be... Wrong road name on turn lanes, etc etc.

I will give it a make-over

Here's a short summary:

Ramps shouls start at the point where the solid white line starts. So at the last moment when you can turn/choose.

These segments should not exist at all. The right turn split off is only at the junction: https://www.waze.com/editor/?env=row&lo ... ,326384828

The split of for left turn lanes should start approx 100m later.

All these segments will be deleted https://www.waze.com/editor/?env=row&lo ... ,326387071
Connecting the remaining pieces is better.

These segments have the road name, where they come from, not where they are leading to. So you hear "keep left to service road" while you enter the C ring road
https://www.waze.com/editor/?env=row&lo ... ,326384829

Camera's should face the direction you are driving, independent of the direction they flash!

Yes, the C-ring is where my previous 2 posts were about.
The first example (D ring) is not so bad. I see some room for improvement though

Nice Job!

If you install Junction Angle Info script, you'll have more information about the angles between 2 segments and the native instruction that waze will give, based on road type, name and angle.

The left turn lanes currently have the name of the main road. This results in "keep left to C ring road" while you want to turn left onto Ali Bin Abi Talib St. If you remove the name on the turn lane, it will adopt the name of the next segment you'll be driving to, so it will pick the street you are heading. This works in 2 way, if you want a left, you hear "keep left and then turn left onto Ali Bin Abi Talib St." If you're planning a uturn, you'll hear "keep left and then make a uturn onto C ring road."

Also this will remove the "keep right", when you're simply following the C ring road.

Finally, the uturns, try to make them over 170 degrees instead of ~160, and you'll get the Uturn prompt automatically.

Same kind of issue here

https://www.waze.com/editor/?env=row&lo ... t=10107328

I cannot find anything wrong.

Ok let me know when you're done so I can compare to the previous version

Ok I thought you were talking about the junction of the screenshot you attached. Indeed the junction C Ring / Aku Bin Abi Talib is pretty wrong.