An outside look at a store — what’s slowing it down, what it’s paying for and not using, and the errors sitting live on the site right now.
The storefront itself is fine. The platform is the right one, the photography is good, and the product write-ups are better than most competitors’. None of that is the problem.
The problem sits between the customer and all of it. Apps got added over the years and never taken off, and each one made every page heavier. On a phone, someone taps a product and looks at a blank screen for about four seconds. A good share leave first — and in the reports they don’t look like a lost sale, they look like traffic that bounced.
It loads on every page of the site, but we couldn’t find one page anywhere that uses it. We checked the homepage, all 18 content pages and the product pages.
Cancelling costs nothing and loses nothing. This is the sort of thing that gets found in an afternoon and never gets looked for.
Opening one product page contacts 22 different outside companies. Thirty of those pieces of code have to finish before the page can draw — so the customer watches a blank screen while they arrive.
The single most important image on the page waits until the rest has finished, which is why the product area sits empty and grey for the first few seconds. It’s a one-word change, and it’s one of the exact things Google scores a site on.
Behind every product page is a hidden summary telling Google the name, price and rating. There are two of them here and they disagree. The one written first has no rating on it.
With hundreds of genuine reviews, stars beside a listing are one of the biggest differences between someone clicking you or a competitor.
Software that reads pages aloud for blind customers speaks that line in place of the picture. Most here are blank. Google reads the same text to understand images, so it does two jobs at once — and it’s the most common thing online retailers get sent legal demand letters over.
It fires the same large request whether or not that page has a gift offer on it, including pages where it has nothing to do. That’s not the app’s fault; it’s how it was set up.
No description is set, so Google writes its own from whatever text it finds first on the page — usually a menu item or a cookie notice. You get to decide what that says, and right now nobody has.
Google reads the main headline to work out what a page is about. Four of them competing means none carries much weight.
For the first second or two the logo lands on top of the navigation and headings sit unstyled before everything snaps into place. It does resolve — but for a first-time visitor that is the first impression.
A rewards tab bottom-left and a help chat bottom-right, both hovering over the part of the screen a thumb reaches for. Small, and it happens on every mobile visit.
A real review names your specific pages and tells you exactly where to click. We’d rather you fixed the cheap things yourself than paid us for an afternoon of admin.
Send us your website and you’ll get one of these back — your numbers, your errors, your quick wins. No call required, nothing to sign, and no obligation to hire us afterward.
Several items in a typical review can be fixed in-house in an afternoon. We’ll tell you which ones and how. Plenty of people take the review and do exactly that.
Send us your websiteHow a real review is done. Public data only — no access to your admin is needed or asked for. Page weights, request counts and script totals come from browser timing on a live page. App usage is checked by fetching and inspecting the homepage, every content page, and sample product and collection pages. Catalogue figures come from the public product feed.
What a review can’t see. Everything is measured from the outside. Your own admin holds the numbers that would sharpen it — what phone visitors actually convert at against desktop, what the apps really cost each month, and how your product information is stored behind the scenes. Read-only access for a day answers all of it, and none of that requires the ability to change anything.
Load-time figures are a measurement on our connection, so treat them as indicative rather than exact. Byte counts, file counts, app findings and missing descriptions don’t depend on connection speed and are exactly as stated.