Your account was suspended because you hit the CPU limits.
To learn more about the limits, please check the knowledge base articles about the CPU limits.
Accounts that hit a daily limit are suspended for 24 hours. After 24 hours, your account will be reactivated automatically.
Your account will be reactivated automatically in 17 hours from now.
Please evaluate your website and consider taking actions that may reduce your account’s resource usage. Accounts that repeatedly hit limits may get taken down permanently.
To increase the limits, please consider upgrading to premium hosting. Premium hosting has much higher limits than free hosting, and hitting these limits will never result in your account getting suspended. iFastNet can even migrate your data from your free account while the account is still suspended
Other Information
I figured out that the images I loaded up in the WooCommerce Plugin are in PNG, so they size 2-3 MBs per image. I need to convert these images in webp, so they size lesser and the site can work again.
Can I ask to get unsuspended so I can change the images and work it out?
Account cannot be reactivated earlier upon request, you will be able to edit your account once the timer ends.
Also, large images are probably not the cause of the suspension. Although making those images smaller is a good idea, I don’t believe it the cause behind your suspension.
Hello, I understand completely the dynamic of the situation so I’ll just wait since it’s a few hours more. What do you think it’s the problem behind the CPU Limits reaching? I thought about the images, WooCommerce Product Images to be exact, cause they sized about 3-5 MB each, maybe compressing them to WebP, which is better should have worked.
I’m also gonna install a cache plugin and maybe figure out some plugin I can remove and maybe use some line of code.
Well… image conversion can be a fairly computationally expensive process, especially when the images are pretty big and there are a lot of them.
For the purpose of reducing CPU usage, reducing the size of the image doesn’t help much because serving static files uses basically no CPU. But having very big images isn’t great for user experience, so reducing their size is still a good idea.
Were you already trying to convert the images when the suspension hit? Or did you think of this afterward?