One of these routes is not like the other

Post run relaxing

Today's run (street): 3.36 or 3.41 miles

It was another mid-high intensity run this morning. My heart rate (the only performance metric I'll view while on a run) was close to target, and I knew I'd be happy with my finish time. A quick look at the Garmin confirmed that I'd managed another good run. I cooled down by the pool when I finished and tried mapping my route using the Gmaps web app on my phone

I was pleased to see that the Android OS was finally supporting Gmap's functionality. That allowed me to record my distance and calculate my true pace. I liked what I saw: 9:05. Although I worked for it, getting there didn't feel as hard as I thought it would be. Looking a gift horse in the mouth, I mapped the run on my laptop after I'd finish showering and discovered a surprising disparity in distance.

Distance: Android version

Web version, same route

For some reason, the route on my laptop registered 5/100ths of a mile shorter than the exact same map on my phone. Weird and disappointing, because that small disparity meant my average pace was actually 9:12. Not bad, but not what I wanted to see. I remapped the route to see if I'd somehow missed a street, but the distance came up the same each time.

So what if the phone mapping is actually the correct measurement? That would be nice. But I use the web version as the standard, so I'll have to go with that. In the end, the difference is measurement is minimal. Unfortunately, the difference in pace is not.