I ran my free site check on our own ebook shop. Here's what it found.
Before asking clients to trust a site check, I ran one on Evertech's own Bangla ebook shop, as a buyer on a phone. 21 problems, ranked by what they cost — and what each kind says about your site.
On this page
I offer a free site check: you send me your site's address, I record a short video of what's slowing it down or stopping enquiries, and you get a fixed price to fix it. Before I asked anyone else to trust that, I ran it on a site I'm allowed to be blunt about — our own ebook shop.
It sells a handful of Bangla PDF ebooks, checks out through aamarPay, and emails the download link after payment. It's built for people who arrive from a Facebook ad, on a phone, and that decided how I tested it.
How I ran the check
I didn't read the code. I used the shop like a buyer: the homepage, each product page, the cart, the checkout and the error pages, on a laptop and then on a phone. Every time something felt wrong, got in the way or looked off, I wrote it down.
Then I ranked the list by what each problem was costing, not by how bad it looked to a developer. A broken image that makes the shop look abandoned can cost more sales than a bug nobody ever sees.
The result was 21 problems. A few were serious, and those stay out of public write-ups, however an audit is written. The rest fall into four kinds, and you'll probably find the same four on your own site.
1. Dead ends
A buyer who can't see the next step leaves. Our cart showed what was in it, but had no way to go to checkout. The product pages had no header, so there was no way back to the shop.
2. Things that broke when used
Press "−" on a quantity of one and the page threw an error, still showing the old item and total until you reloaded. Change a quantity and the line price didn't update. An ebook could be added to the cart three times, and "Buy Now" also bought whatever was already in the cart. None of this shows up when you click through once; it shows up when someone shops the way people actually shop.
3. Trust leaks
Two products and the banners had missing images, which makes a shop look dead. Every product carried the same hard-coded rating, six stars out of five. The FAQ promised payment methods that checkout never offered. Each one is small. Together they make a stranger hesitate with their wallet in their hand.
4. Small details that cost sales
The phone field dropped the leading zero from Bangladeshi numbers. Checkout asked for a delivery address for a product that's a PDF. And the Meta Pixel only counted page views, so Facebook couldn't learn who added to cart or started checkout, and the ads couldn't improve.
What I did about it
I redesigned the homepage and the buy flow around one decision: a clear Bangla headline, a product card with the price and a single obvious button, buttons that lock while they work so a double tap can't add a book twice, a cart that leads to checkout, and a phone layout built for scrolling. The new flow is covered by 221 automated checks. The full list is in the case study.
What I'd take from it
- Walk the money path — from the first page a buyer sees to the moment they pay — before you look at anything else.
- Use it on a phone, with your thumb. Most problems hide there.
- Rank by cost, not by how technical it is.
- Trust leaks are cheap to fix and easy to miss, because you stop seeing your own site.
- Make sure you can measure it. If your ads can't see a purchase, they can't find more buyers.
If you'd like this done on your site, send me the address. I record the video, you get a fixed price for the fixes, and if I don't fix what we agreed, you don't pay. I do three free checks a week, so if the week is full I'll tell you when yours will be ready.