Your site is probably slow because of images

When someone tells me their website feels slow, I check the images first. It is the most common cause by a wide margin, and usually the cheapest thing to fix. The usual story goes like this. Somebody uploads a photo straight off a phone or a camera. It is four thousand pixels wide and around six megabytes. On the page it displays in a box six hundred pixels across. The browser still downloads the whole six megabytes, then shrinks it. Do that with eight photos on a homepage and you have asked a visitor on mobile data to download roughly fifty megabytes to look at your opening hours. Three fixes, in the order I would do them. Resize before uploading. If the largest it will ever display is eight hundred pixels wide, upload it at sixteen hundred for sharpness on high resolution screens and stop there. Any photo editor does this, including the one already on your phone. Save as WebP. It typically lands around a quarter to a third the size of an equivalent JPEG with no visible difference. Every browser people actually use has supported it for years now. There are free converters that will do a whole folder at once. Lazy load anything below the fold. Images further down the page should not load until someone scrolls toward them. Most website platforms have a checkbox for this. If yours is custom built, it is one attribute in the markup. You can usually get a page from four seconds to under one with those three, and none of them require touching how the site is built. Test it honestly, though. Load your site on a phone, on mobile data, not on your office wifi next to the router. That is the experience most of your visitors are having, and it is the one that decides whether they wait. If you have done all that and it is still slow, then it is worth looking at hosting, at how many fonts and tracking scripts are loading, or at whether the platform itself is the problem. But start with the images. I would guess three quarters of the time, that is the whole answer.