Moving time = Time the device believes you are moving
Time = The actual time between splits/intervals
The device makes a judgement as to whether it "believes" you are still moving during the entire duration of the run. If it doesn't believe you "moved" then it removes that time from the overall actual time. I'd say in almost all cases, don't trust it. I very rarely stop moving and am running 7-8 min/mile, yet I seem to always have a discrepancy in my times as well. The actual time is the one that matters.
If you believe it could be a GPS issue, then attempt to zoom in on your running path on the map online. If you find that your actual path you traveled deviates significantly (like it thinks you ran in backyards and in lakes/rivers), then it could be a GPS issue. However compare this run to other maps to see if the GPS discrepancy is common or uncommon to your typical path before judging this one run. With all that being said, I would say given the consistency of your pacing, that this is likely not a GPS issue.
So the key is: Do you feel this long run effort of 4 miles matched your previous effort outputs for a long run pace? Do you feel as if you could have run one more mile at this pace?
Your goal pace was an 11:48, yet you ran an average 10:52. So was this an improvement on your fitness or a misjudgment on the effort? Probably a combination of the two. These would be your matching paces/PRs for someone with a long run pace of 10:52:
View attachment 190612
So, I'd venture to guess that you have made some fitness improvements in the recent training cycle (as you've noted with many of the other runs seeming to be easy), but that it might be a stretch to say you're at the fitness level right now for a 10:52 long run pace.
Do you feel as if we need to bump up your paces slightly? Like to a 9:28 5K pace (like your February 5K time). You're still 9 weeks out so we could do another fitness test if you feel we need to re-assess your current training paces. Thoughts?