I am pretty sure the vpn traffic would receive a lower priority than normal http/mail traffic.
Also keep in mind that the company she is connecting to could have a QOS policy determining vpn traffic as well.
Thanks, so getting unshaped makes sense. Although speeds are
generally OK I want to optimise as much as possible.
Is she using a vpn connection to then rdp to her desktop?
I'm not clear on what you are asking

o), but she accesses with VPN and then has a "remote desktop" kinda thingy

p). When she's on this "remote" desktop she doesn't have access to her laptop's hdd for instance, only the network drives/folders at work.
You should also take into account the load on the other side's line. Unless they have a dedicated line for VPN connections, you'd be contending with whatever normal day to day traffic is in transit on the wire. In typical cases where companies do manage everything through one line (and have implemented QOS) you'd be contending with whatever mail traffic (usually high) and browsing traffic (also high) is on the line. Add hosted web and FTP services and whatever other junk the company allows through their infrastructure and you start having lines running flat out.
Also, taking the above into account, you'd be likely to see performance degradation during peak business hours (typically 8 to 11-ish and 1-ish to 5).
Just my take on things as I've experienced them...
I don't know what QOS is, but I get the gist of what your saying.
Thank you both for replying. I'll try unshaped and see if it makes a difference.