I took a brief look at the various images that you have displayed in your most recent post and was somewhat uncertain as to what was causing you problems.
The synchronisation rate for a circuit will always be greater than any measured throughput speed and the two sets of values that you have noted show the expected result of the WiFi connection being worse than the connection using an Ethernet cable. That said, I am rather surprised to see that both measured throughput speeds are significantly below the circuit's synchronisation speed.
I am uncertain as to how your service provider has provisioned the circuit. I would say that a ping of 12 ms would be quite reasonable in the UK and coupled with the high number of CRC errors being reported, along with no FECs, makes me believe that your circuit is currently operating in fastpath mode.
In the third image, the very odd value reported for the Received Power (in the Upstream column) must be the result of either overflow or underflow of a signed integer. That is very much an error of the VMG1312-B10D hardware and is not something that I have seen before. As such, it will not cause any problem. It is just an annoyance.
I would suggest that you carefully recheck the configuration of the VMG1312-B10D and ensure that everything is set as required for a service from your ISP, then give it some time and see if the DSLAM (at the far end) will react to the errors and adjust the current configuration.
You may find it easier to access the device either by telnet or ssh and then look at the statistics by using the xdslctl info --stats command. Granted, I do not have a G.993.2 (VDSL2) service, but here follows an example of what that xdslctl command line displays for my G.992.3 (ADSL2) service --
$ xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 8000
Last initialization procedure status: 0
Max: Upstream rate = 1024 Kbps, Downstream rate = 5520 Kbps
Bearer: 0, Upstream rate = 996 Kbps, Downstream rate = 5611 Kbps
Link Power State: L0
Mode: ADSL2 Annex A
TPS-TC: ATM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 4.7 6.8
Attn(dB): 45.0 28.3
Pwr(dBm): 0.0 12.7
ADSL2 framing
Bearer 0
MSGc: 59 10
B: 175 22
M: 1 8
T: 1 6
R: 6 6
S: 0.9979 5.8687
L: 1459 259
D: 64 4
Counters
Bearer 0
SF: 1047557 11974
SFErr: 848 2
RS: 68091125 2978915
RSCorr: 34556 35
RSUnCorr: 39961 0
Bearer 0
HEC: 16062 0
OCD: 4 0
LCD: 4 0
Total Cells: 224761711 39819792
Data Cells: 1936476 329738
Drop Cells: 0
Bit Errors: 958136 88
ES: 101 2
SES: 13 0
UAS: 46 46
AS: 16985
Bearer 0
INP: 1.00 0.00
INPRein: 0.00 0.00
delay: 16 6
PER: 16.21 17.60
OR: 32.06 7.27
AgR: 5621.64 999.38
Bitswap: 4560/4561 40/40
Total time = 4 hours 43 min 56 sec
FEC: 34556 35
CRC: 848 2
ES: 101 2
SES: 13 0
UAS: 46 46
LOS: 0 0
LOF: 0 0
LOM: 1 0
Retr: 0
Latest 15 minutes time = 13 min 56 sec
FEC: 2549 21
CRC: 7 2
ES: 4 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 2971 0
CRC: 13 0
ES: 8 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
Latest 1 day time = 4 hours 43 min 56 sec
FEC: 34556 35
CRC: 848 2
ES: 101 2
SES: 13 0
UAS: 46 46
LOS: 0 0
LOF: 0 0
LOM: 1 0
Retr: 0
Previous 1 day time = 0 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
Since Link time = 4 hours 43 min 8 sec
FEC: 34556 35
CRC: 848 2
ES: 101 2
SES: 13 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 1 0
Retr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
$
I think that is a lot easier to examine -- and show to others -- than taking a sequence of screen-captures from the GUI.