StatusCake

Why Visitors to e-Commerce Websites Don’t Make Purchases

There is a good reason why brick-and-mortar retailers spend a lot of time and effort on their counter displays and store windows. Their goal is to provide their customers with as much visual content as possible to entice them to buy their merchandise. The same principle holds true for online retailers. A recent study by international e-commerce consulting firm Episerver demonstrates just how important the content of a website is to convince visitors to become customers.

Episerver surveyed 1,112 consumers who had made an online purchase within the past year. The company found that 98% of the respondents had not made a purchase on at least one of the sites they visited due to incomplete or incorrect content. When aggregated across all sites visited, a percentage breakdown of the specific reasons for not making a purchase was price concerns (65%), difficult-to-navigate website (42%), found a product that better suited needs elsewhere (39%), difficult check-out process (34%), slow loading website (29%), incomplete content (21%), incorrect content (14%) and non-personalized shopping experience (4%).

Another problem noted by the study was inconsistent customer expectation based on website content, with 37% of the respondents stating they had received a product that looked different from the product they saw online. Also, 27% of the respondents said they had received a product that did not match the description on the website.

These inconsistent expectations also had a significant financial impact on the retailers, with 48% of the respondents saying they had returned a product that had not met their expectations. The study noted that returns cost retailers billions and that the amount is expected to increase as the volume of online sales continues to increase.

The study also found that 92% of the respondents visited a website for the first time for reasons other than to make a purchase. About 45% said that they visited a website to search for products and learn more about them, 26% visited to make a price comparison, and 11% were looking for more information about a retailer. Only 9% said they made their first visit to a website specifically to make a purchase.

The study concluded that online retailers needed to spend more time concentrating on website content and the quality of the interactions consumers had with their site.

Commenting on the study, Ed Kennedy, Episerver’s senior director of commerce, said: “Our study shows consumers really care about content when shopping online, not only the quality and accuracy but also how it’s delivered to them. Complete and accurate content is now table stakes, and brands looking to go above and beyond must consider personalization.

“What shoppers see on a website or mobile app, and how it is delivered to them, can make or break their final decision to make a purchase. Consumers expect the content they’re shown to be relevant, accurate, and, increasingly, customized to their preferences and location. To compete in 2017, strong content is no longer negotiable.”

Share this

More from StatusCake

What the Namecheap Outage Revealed About DNS Recovery

4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes

Monzo’s Stand-In Held Up on Wednesday. Some Customers Still Had a Bad Day.

3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and

What Broke GitHub on August 17 and How Retries Made the Incident Worse

3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests

Automate StatusCake Monitoring with viaSocket

3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect

Website Monitoring Checklist: What to Track Beyond Uptime

7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and

Want to know how much website downtime costs, and the impact it can have on your business?

Find out everything you need to know in our new uptime monitoring whitepaper 2021

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.