Steps to do

Test with a performance test tool: I used userbenchmark. It gives you a nice report on what is doing good what is doing bad.
E.g. https://www.userbenchmark.com/UserRun/48037775

One of my issues was that my performance mode of “Control Center 3.0” was on Quiet mode which is better for ears but worse for performance ­čśë
For daily/normal use one can enable Entertainment and for heavy application: Performance can be used.

Apart from the slow new laptop … I seemed to suffer from network / Internet interruption. My Internet connection is pretty stable. So did some research turned out, there are option for your ethernet connection to be in a ‘green’ mode.
See this post for how to resolve this:
https://helpdesk.flexradio.com/hc/en-us/articles/202118518-Optimizing-Ethernet-Adapter-Settings-for-Maximum-Performance

Another sympton my laptop suffered from was: BSOD (blue screen of death) code: 0x00000133 with codes like: ntoskrnl.exe+3f72a0 and ntoskrnl.exe+41f67e , DPC_WATCHDOG_VIOLATION …
Ok, I knew memory dumps are available but how to analyse those?

Luckily I found some nice tools on https://www.resplendence.com
One software tool WhoCrashed allows you to analyze those dumps (typically under C:\Windows\Minidump and/or C:\Windows\MEMORY.DMP)

On Fri 19/11/2021 20:01:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111921-6406-01.dmp
This was probably caused by the following module: storport.sys (storport+0xad4d) 
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF800070FB320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). 
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Fri 19/11/2021 20:01:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: bhtsddr.sys (bhtsddr+0x15cc6) 
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF800070FB320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\bhtsddr.sys
product: BayHubTech SD Reader Driver
company: BayHubTech
description: BayHubTech SD Reader Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bhtsddr.sys (BayHubTech SD Reader Driver, BayHubTech). 
Google query: bhtsddr.sys BayHubTech DPC_WATCHDOG_VIOLATION



On Fri 19/11/2021 19:48:03 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111921-7484-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f) 
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8010FEFB320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). 
The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system. 



On Fri 19/11/2021 19:48:03 your computer crashed or a problem was reported
crash dump file: C:\Windows\19112021_1948MEMORY.DMP
This was probably caused by the following module: bhtsddr.sys (bhtsddr+0x15f87) 
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8010FEFB320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\bhtsddr.sys
product: BayHubTech SD Reader Driver
company: BayHubTech
description: BayHubTech SD Reader Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bhtsddr.sys (BayHubTech SD Reader Driver, BayHubTech). 
Google query: bhtsddr.sys BayHubTech DPC_WATCHDOG_VIOLATION



On Fri 19/11/2021 9:56:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111921-8328-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f) 
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8050B0FB320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). 
The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system. 



On Wed 17/11/2021 18:17:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111721-7593-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f) 
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8005B6FB320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). 
The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system. 


The other which seems interesting as well is WhySoSlow, this one takes an holistic approach to your laptop/pc’s performance


Devices and Drivers
PROCESSOR
11th Gen Intel┬« CoreÔäó i7-1165G7 @ 2.80GHz
GRAPHICS
Intel® Iris® Xe Graphics
AUDIO
Realtek High Definition Audio
NETWORKING AND I/O
Realtek PCIe GbE Family Controller
SonicWALL Virtual NIC
Killer® Wi-Fi 6 AX1650x 160MHz Wireless Network Adapter (200NGW)
Thunderbolt Controller 1
Intel® Wireless Bluetooth®
MEMORY
24 GB
STORAGE
Samsung SSD 980 PRO 250GB
Intel® NVMe Controller
Intel SSD 660p Series

Below are my specs

Notebook NS50_70MU
BIOS
Version
1.07.09TNB
Date
5/1/2021
MOTHERBOARD
Manufacturer
Notebook
Model
NS50_70MU
Version
Applicable
OPERATING SYSTEM
Edition
Microsoft Windows 10 Pro (64 bits)
Version (Build)
21H2 (10.0.19044)
Devices and Drivers
PROCESSOR
11th Gen Intel┬« CoreÔäó i7-1165G7 @ 2.80GHz
GRAPHICS
Intel® Iris® Xe Graphics
AUDIO
Realtek High Definition Audio
NETWORKING AND I/O
Realtek PCIe GbE Family Controller
SonicWALL Virtual NIC
Killer® Wi-Fi 6 AX1650x 160MHz Wireless Network Adapter (200NGW)
Thunderbolt Controller 1
Intel® Wireless Bluetooth®
MEMORY
24 GB
STORAGE
Samsung SSD 980 PRO 250GB
Intel® NVMe Controller
Intel SSD 660p Series
Intel Software
Intel® Memory and Storage Tool