Key questions to ask when reviewing a Wirral Shopify agency’s portfolio and case studies

Evaluating Agency Portfolios in the Wirral eCommerce Landscape

When searching for top-tier Shopify Wirral services, merchants are frequently presented with visually impressive agency portfolios and persuasive case studies. However, aesthetic polish often obscures fundamental technical deficiencies. A store that looks sleek in a static staging environment may harbour bloated JavaScript execution, poorly architected Liquid rendering loops, unoptimised API calls, and unstable third-party application stacks that compromise checkout velocity and conversion rates.

Before initiating a deep dive into an agency’s historical project work, review our overarching guide on How to select an accredited Shopify Partner agency in the Wirral area to ground your procurement process in vetted compliance benchmarks. Once baseline accreditation is confirmed, evaluating portfolios requires an architectural mindset, testing not just what an agency built, but how resiliently, performantly, and scalably it was executed.

1. Liquid Architecture vs. Off-the-Shelf Theme Scaffolding

Many regional agencies claiming Shopify expertise rely on heavily modified commercial themes purchased from the Shopify Theme Store or third-party marketplaces. While valid for rapid MVPs, modifying pre-built themes often creates technical debt that penalises long-term growth.

Key Questions to Pose:

  • “Was this build developed on Dawn/a clean Shopify CLI baseline, or adapted from a bloated multi-purpose marketplace theme?” Bespoke engineering built on Shopify’s reference themes or proprietary lightweight component libraries indicates modular, maintainable code rather than layered CSS overrides.
  • “How do you handle section rendering and JSON templates?” Interrogate how the agency implements Online Store 2.0. Clean architecture uses native JSON templates, custom sections, and Theme App Extensions, preventing legacy Liquid spaghetti from cluttering the template files.
  • “Can you walk us through the Liquid AST (Abstract Syntax Tree) and loop optimisation in your heaviest collection template?” Poorly engineered nested for loops iterating over product tags or metafields create critical Time to First Byte (TTFB) delays on larger catalogues.

2. Frontend Performance and Real-World Core Web Vitals (CWV)

Agencies frequently showcase historical Lighthouse audits captured in staging environments with cached assets and disabled tracking pixels. Real-world performance on live stores under live third-party script loads (Google Tag Manager, Klaviyo, Meta Pixel, heatmaps) is the true test of engineering discipline.

Key Questions to Pose:

  • “What are the 75th percentile Core Web Vitals (CWV) scores for your live portfolio projects over the past 28 days?” Run the URLs through Google PageSpeed Insights and examine Chrome User Experience Report (CrUX) data. Focus heavily on Interaction to Next Paint (INP) and Largest Contentful Paint (LCP).
  • “How do you prevent Cumulative Layout Shift (CLS) when dynamic merchandising widgets and currency switchers hydrate?” Inspect their previous builds to verify that dimensions are reserved for dynamic banners, font loading strategies (font-display: swap) are strictly enforced, and layout shifts remain below 0.1.
  • “What is your script loading strategy?” High-performing engineering teams defer non-critical JavaScript, isolate analytics within web workers using solutions like Partytown, and prevent main-thread blockage during critical checkout and collection navigation.

3. App Stack Rationalisation vs. Native Custom Code

A portfolio bloated with 30+ installed applications indicates an agency reliant on plug-and-play middleware rather than engineering custom Shopify solutions. An overabundance of third-party apps degrades DOM performance, introduces security vulnerabilities, and escalates recurring operational costs.

Key Questions to Pose:

  • “How many public third-party apps does this case-study store run, and which custom functionalities were built natively?” Progressive agencies leverage native Shopify features: Shopify Functions for custom cart transforms and discount logic, native Metafields/Metaobjects for structured content, and standard Customer Accounts APIs.
  • “Did you use external applications for custom bundles, quantity breaks, or checkout validation?” Since the release of Shopify Functions, these capabilities can be written in Rust or JavaScript and executed on Shopify’s infrastructure without external network latency. Inquire whether their portfolio reflects this modern execution.
  • “What was the total script payload introduced by third-party apps on this build?” Top technical agencies enforce strict JavaScript budgets (e.g., keeping total external JS below 300KB before third-party tracking scripts).

4. Data Integrity, Attribution, and Revenue Claims in Case Studies

Case studies frequently claim substantial uplifts: “Increased revenue by 140%” or “Boosted conversion rate from 1.2% to 3.8%.” Without context, these metrics are vanity statistics. Growth may stem from aggressive paid ad spend, seasonality, product releases, or macroeconomic conditions rather than agency intervention.

Key Questions to Pose:

  • “How did you isolate the agency’s technical and UX contribution from external marketing factors?” Demand attribution specifics. Did the agency execute controlled A/B testing (e.g., using Intelligems or Elevar) to prove that the new information architecture drove the lift?
  • “What were the exact migration baseline metrics?” If the case study highlights a migration to Shopify from Magento 1/2, WooCommerce, or Salesforce Commerce Cloud, examine how organic search visibility was preserved. Request data on 301 redirect management, XML sitemap indexing, and post-launch organic session continuity.
  • “What was the impact on Average Order Value (AOV) and Customer Lifetime Value (LTV)?” Conversion rate increases achieved through discounting hurt profitability. Elite agencies align UX changes with sustainable metrics, such as upsell adoption within the native checkout flow or optimized post-purchase funnels.

5. Architecture Interrogation: Headless, Hybrids, and Integrations

If an agency portfolio features headless builds (Hydrogen, Next.js, Gatsby), verify whether the complexity was commercially warranted or simply an exercise in engineering overreach. Conversely, if your business requires enterprise systems connectivity, you must validate their integration depth.

Key Questions to Pose:

  • “If this project is headless, why was headless chosen over an Online Store 2.0 Liquid build?” The agency should articulate clear business logic—such as sub-millisecond edge routing, bespoke multi-platform design systems, or decoupling legacy content systems—rather than a dogmatic push for headless architectures that increase client maintenance overhead.
  • “How were backend ERP, WMS, and CRM systems integrated?” Review projects requiring synchronization with systems like NetSuite, Brightpearl, SAP, or Linnworks. Inquire whether middleware was custom-built via AWS Lambda/Shopify Webhooks, managed via iPaaS (e.g., Patchworks, Celigo), or pushed through legacy private apps.
  • “How do you handle API rate limits and webhook failures in your portfolio stores?” In high-volume environments (flash sales, product drops), standard Shopify REST and GraphQL endpoints face throttling. Confirm that their past builds leverage robust queuing systems (e.g., Redis, SQS) to manage webhook payloads without data loss.

A Technical Checklist for Reviewing Shopify Case Studies

When interviewing a prospective team for your Shopify Wirral project, bring this diagnostic checklist to dissect their presented portfolio:

  • Code Inspection: Inspect the live site’s DOM. Are assets minified, images served in next-gen formats (WebP/AVIF) with adaptive sizing (srcset), and CSS modularised?
  • Liquid Quality: Look for evidence of legacy jQuery dependencies or inline JavaScript handlers in the page source. Modern implementations rely on ES modules and native Web Components.
  • Checkout Customisation: For Shopify Plus merchants, check whether checkout modifications rely on legacy checkout.liquid (deprecated) or modern Checkout UI Extensions and Shopify Pixels.
  • Mobile Responsiveness: Test portfolio sites on actual mobile hardware with CPU throttling applied in DevTools to reveal jank, layout recalculation delays, and sluggish input response.
  • Longevity Audit: Review stores launched 12 to 24 months ago. Have they degraded under ongoing client management, or did the agency build a durable, fool-proof content management architecture?

Conducting this level of technical review filters out agencies that rely on surface-level design and uncovers teams with the engineering rigor required to build robust, high-converting Shopify platforms.

Tagged