VPN and WAN Policy-Based RoutingDomain Strange Behavior

I've been using VPN and WAN Policy-Based Routing to pass along certain domains to the WAN instead of going over the default VPN path because they get blocked. Examples are kroger.com and redbox.com. Sometimes it works sometimes it doesn't. Recently I decided to do a tracert when I notice these domains are being blocked. What I've noticed is they are being routed correctly through the WAN but I am still getting blocked at the browser level. Wondering if anyone had any suggestions on how to solve this issue?

My polices

Here is a screenshot showing the kroger.com path going through my WAN correctly

Here is what happens in the browser

Here is amazon.com being routed properly through the VPN which works as it should based on the policy and allowing access when viewed in a browser