That's because Waze just says "cut straight through this cornfield and don't worry about the intersection."

On a serious note, my wife and I both noticed that Google Maps had an "upgrade" about six months ago that caused it to be much more resource-intensive. I thought maybe my phone was acting up, but literally the same day I noticed Google Maps running slow, my wife said she could barely get it to load. We were both using Galaxy S7's, a two-year-old phone but one that still had comparable tech specs to many other phones being sold new in 2018.

We recently upgraded to Pixel 3's, and now Google Maps runs fine. It's always given me enough warnings about upcoming turns...I'd say it's only minor shortcoming is in very busy interstate interchanges where there are multiple exit ramps and then different exits from each ramp. My old-fashioned Garmin device did a better job of showing a visual image of what the signs and ramps actually looked like and provided a clear yellow arrow on the lane you should be in.

Usually when I map a route, I take a moment to look through the whole route just to get an idea of where I'm going. The whole idea of Google Maps is that you don't have to memorize the whole thing, but I agree with those who say you should have a general idea of where you are and where you're going.