I will try to answer these as best I can.
1) Giving high CPU load on my digital ocean 2gb 2cpu and 50gb storage server (cloudways)
I can’t speak to your specific scenario but I can say that most of the ‘heavy lifting’ of this plugin does not happen on your server. This plugin sends out a page URL to the Google Pagespeed Insights API, and waits for the response. Google scores your page on their servers, sends back the results, and this plugin stores those results in the DB. I would wager that any server that has performance issues running this plugin is also going to have performance issues if the server received a similar amount of web traffic from real users.
2) Execution rate/speed is very low for 3k+ pages website like ours
Yes 3000 pages to check is going to take a long time. We are limited here by how quickly the pagespeed API checks your page. Theoretically I could retool this plugin to check multiple pages at a time, but I have avoided doing so because of fears of it putting too heavy of a performance burden on the server. So it just checks a single page at a time. My advice would be to create a ‘sample’ set of pages that represent the different types of pages across your site that you want to get reports on. You can add those pages in the custom URLs area. Checking that sample set instead of all 3k+ pages would be much quicker.
3) Giving false Google analytics user visit data and high bounce rate
This should be something that you can filter/block in Google Analytics to keep your data clean. I do not know the exact steps to do so, but some googling should hopefully get you the info you need to do this.
4) In initial run or setup, advance configuration or scheduling tabs are not accessible.
I’m not exactly sure what you mean. Is there an error on the page not letting you expand/collapse those tabs? If so can you share the error you are seeing (probably in the browser inspector console).
I hope this all helps!
Matt Keys