Magento UX Audit Case Study: How We Helped Meat4you

Ecommerce UX Audit and Implementation

Our UX audit process combined heuristic evaluation, real-user behavior data, and competitor benchmarking. The review covered the main user flow from product discovery through checkout.

We documented the findings in a detailed audit report with actionable recommendations for each major page template and implemented them on the site:

• Homepage. The audit found a fragmented layout with no clear call to action, so visitors’ attention was pulled in several directions. We reorganized the page around a single, clear call to action, so visitors now see the store’s main offer immediately.
• Search. We found that search results appeared as a plain-text list, with a noticeable delay before results showed up. So our team redesigned results to show product images and clear categories, and reduced the delay so customers find what they want faster.
• Category pages. The UX review found inconsistent product cards across the site, with producer branding competing with pricing for attention. Our designer made product cards consistent across the site, prioritizing pricing and product details over decorative branding. We also added quick view and price filtering, so browsing is faster and shopping decisions are easier.

• Product pages. The audit identified that there’s no way to zoom in or view products from multiple angles. It worked as a real barrier for a business selling meat by appearance and cut. We added zoom and multi-angle images, simplified pricing display, and shortened overloaded descriptions.
• Footer. We redesigned the footer to make it stand out clearly from the page. It helps customers easily find contact details, policies, and links when they need them.
• Mobile. The analysis showed that the site had undersized icons and a cluttered homepage on mobile. Our team enlarged the icons and buttons for easier tapping, and decluttered the homepage so the main offer is visible without scrolling, extending the same fixes made on desktop to most of meat4you’s traffic.

Customization and Ongoing Technical Support

Meat4you’s day-to-day complexity lives in a handful of custom systems BelVG built and maintains as part of our ongoing Magento support relationship:

• A custom weight-based pricing and invoicing engine. Because meat is cut to order, checkout reserves an estimated amount at the time of order. Once the item ships, the actual weight is recorded, a second invoice is generated, and the store’s Swiss payment processor automatically refunds any difference.
• A delivery-date calendar tied to the courier’s API, factoring in supplier working days, order cutoff times, and public holidays, so online shoppers only ever see delivery dates the business can fulfill.

• A multi-supplier fulfillment system that color-codes each order by supplier on the picking PDF, letting warehouse staff sort by supplier at a glance instead of reading line items.
• Custom catalog pricing rules ensure automatic discounts don’t stack incorrectly with promotions already applied to a product, a rule Magento doesn’t support natively.
• Security hardening includes two-factor admin authentication, a non-default admin URL, VPN- and IP-restricted access to admin and staging environments, and search engine-blocked staging sites to protect the live store’s SEO.
• Performance and SEO monitoring and automated security scanning to catch regressions and vulnerabilities before they affect customers. We also monitor Core Web Vitals to identify performance regressions that can affect the shopping experience.

For a complex store like meat4You, it means fewer manual checks and fewer errors. The team can focus on running the business instead of constantly fixing ecommerce problems.

How Optimization Affects Load Time

During the Magento audit, we found that category pages were the heaviest on the site. This is because Magento renders pricing (including per-100g pricing), stock, and promo data for every product in the grid. SEO schema and analytics tracking add more weight. Baseline load time was around 3 seconds, with roughly 2,000 database queries per page.

BelVG’s backend developer addressed this at the source:

• Removed a script block that regenerated on every page load without being needed.
• Fixed incorrect price-block behavior when a product was already in a customer’s cart.
• Added caching to a “most viewed products” block that was recalculating on every single request.
• Cached the site’s main navigation menu, removing repeated generation on every page.
• Reviewed the store’s URL structure and removed roughly 7,600 unnecessary routing entries out of nearly 13,000 total.

As a result, category page load went from almost 3 seconds to 1.7 seconds.