Hi jasmeet ghai,
The original page (mpn) might have some differences in its code or resource loading compared to the copy (mpn1), which could be triggering the excessive CPU usage. Sometimes even minor differences—such as an extra script, an additional event listener, or a subtle change in the DOM structure—can lead to performance issues. It would be beneficial to compare the HTML, JavaScript, and CSS of both pages using a diff tool to identify any discrepancies.
It is important to analyze the JavaScript performance on the mpn page. Profiling tools can help you record a CPU profile while loading the page. This may pinpoint specific functions or scripts that are consuming an abnormal amount of CPU. Heavy DOM manipulations, repeated reflows, or repaints might also be contributing factors that you can detect through such profiling.
check if, mpn page is loading additional third-party scripts or resources that are not present on the mpn1 copy. External libraries, analytics, ad scripts, or even differences in the number and size of images, fonts, or other assets could increase the load on the CPU. Verifying that both pages are requesting the same resources can help narrow down the issue.
Once review any server-side processing that might be happening when the mpn page loads. For example, if the page triggers more complex API calls or database queries compared to the copy, this could contribute indirectly to higher CPU usage. Checking server logs or monitoring tools might reveal discrepancies in behavior between the two pages.
Profiling tools- https://learn.microsoft.com/en-us/windows/apps/performance/choose-between-tools
https://learn.microsoft.com/en-us/dotnet/core/diagnostics/debug-highcpu?tabs=windows#cpu-counters
If you have any further assistant, do let me know.
If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.