First of all, I cannot express how important it is to use the Console tab in your browser’s Inspector to debug these kinds of issues. There can be any different reasons why the scan could be getting stuck and none of them are typically expected, so you will need to look for errors logged in your browse and/or on your server error_log files to see what is causing this issue.
Your first screenshot shows that the scan is getting stuck on a core JS file as well as 40 other files, or which we cannot see in that screenshot (Note: this is not a DB Scan issue as you originally reported). Regardless, the debugging info from your browser and/or the error_log file on your server should help you discover the actual cause. If I had to guess, I would say that either your memory_limit value in the php.ini file on your server is way too small, or else maybe your server is blocking the scan URL on these last few files. Look in the Console tab for 403 or 500 errors or any other error or security warnings, then check you error_log file on the server to see what is causing the error.
Your second screenshot shows your website taking time to load, there is no way to tell how long but obviously it is long enough for you to be concerned about it. I spoke to this briefly in my last reply but I will now explain in more detail. Your site is loading quickly for me every time I have tried it, so the problem must be on your or else it is an intermittent problem that I am not catching. It is clear from your screenshot that you are trying to load your site in a new tab while the 3rd tab in your browser is still trying to finish the scan. This will give you a false impression of your website’s page speed because Chrome will not load two requests for the same site at the same time, so it may take as long as 60 seconds for the scan process to finish the attempt on that failed file that it keeps getting stuck on, and only then will the new tab be queued up to load your site. If you really want to see your site loading at the same time as the scan is running then try opening your site from your phone or another computer that is not the one you are running the scan from.
-
This reply was modified 1 year, 7 months ago by
Eli.