Cusic Digital

Sample report

A real audit, so you know what you’d get.

This is a technical audit of Great Lakes Additive's original WooCommerce store, shared with their permission. The store has been rebuilt, so nothing here describes a live system. It follows the same structure as every audit we deliver.

Business
3D printing manufacturer, Michigan
Platform
WordPress and WooCommerce
Audited
October 2026, from an archived copy
Status
Retired: now a custom platform

01 · Summary

The short version

The store works, but it is slow in a way no single setting fixes. Every page waits 6 to 13 seconds on the server, then downloads 3 to 5 MB, nearly half of it code from the theme, page builder and 15 plugins. Caching and a plugin clean-up would buy time. The staff’s own problems with inventory and database time-outs come from the same plugin stack, though, so the lasting fix is a platform built for how the business works.

Recommendation: rebuildwith the quick fixes below in the meantime

02 · Scores by area

Where the store stands

  • Speed (mobile)

    54

    Product page: 45

  • Search basics

    85

    No H1 or meta description on the homepage

  • Accessibility

    86

    Product page: 75

  • Best practices

    79

    79 on both pages tested

  • Plugins on every page

    15

    Each one its own update stream

Lighthouse scores out of 100 for the homepage on a simulated mid-range phone; median of three runs.

03 · Findings

Ranked by business impact

  1. Finding 1Critical

    Every page waits 6 to 13 seconds before the server starts sending it

    What we found
    The homepage took 6.3 to 12.7 seconds to start arriving across repeated tests, the shop 7.1 to 7.8 and a product page 7.1 to 11.4. On the homepage, the CDN in front of the site reported a cache miss every time, so visitors were never served a stored copy.
    Why it matters
    Nothing can appear until the page arrives, so this delay sits on top of everything else. Google treats under 0.8 seconds as good. On a phone, a shopper is looking at a blank screen long enough to give up.
    What to do
    Turn on full-page caching for visitors who aren’t logged in, so the CDN can serve stored pages. Then profile what WordPress does on each request: with 15 plugins loading, each adds its own database queries and code.

    EffortCaching: small. Finding the slow plugins: medium.

  2. Finding 2High

    Pages download 3 to 5 MB, nearly half of it code

    What we found
    The homepage downloads 3.1 MB in 183 files, including 39 scripts and 49 stylesheets (1.26 MB of JavaScript). A product page downloads 5.4 MB in 276 files. On a simulated mid-range phone with a slow mobile connection, the homepage’s main content took 18.2 seconds to appear.
    Why it matters
    Mobile shoppers pay for every megabyte in time and data. On the homepage, about 1.45 MB of the 3.1 MB is JavaScript and CSS from the theme, page builder and plugins, and the browser has to process all of it before the page settles.
    What to do
    Remove plugins that aren’t earning their keep (see the next finding), stop loading slider and page-builder code where it isn’t used, and resize product images to the size they’re shown at.

    EffortMedium

  3. Finding 3High

    Fifteen plugins load on every page, including duplicates

    What we found
    A page builder and its add-on, a theme starter-sites plugin, a slider, Jetpack, WooCommerce and its payments, buy-now-pay-later and PayPal plugins, an email-marketing sync, PDF invoices, two product-label plugins and two view counters.
    Why it matters
    Every plugin is separate code that has to be updated, kept compatible with the others and trusted with the store. Duplicates double that cost for no benefit, and each update is a chance to break checkout.
    What to do
    Remove one of each duplicate pair and the starter-sites plugin straight away. For the rest, list what each does for the business; anything that can’t be explained is a candidate to remove.

    EffortSmall for the duplicates; ongoing for the rest

  4. Finding 4Medium

    The homepage is missing basic search signals

    What we found
    No H1 heading and no meta description, so Google has to guess the page’s main topic and writes its own snippet. The homepage HTML is also 259 KB before any of the files above load.
    Why it matters
    The homepage is usually the page that ranks for a business’s own name and its main product terms.
    What to do
    Add one H1 that says what the business sells and where, and a meta description written for searchers.

    EffortSmall

  5. Finding 5Medium

    Most homepage images have no text alternative

    What we found
    18 of the 29 images on the homepage have no alt text. The product page scored 75 for accessibility.
    Why it matters
    Screen-reader users hear nothing for those images, and Google Images has nothing to index them by. Product photos are where both matter most.
    What to do
    Describe what each product image shows. Mark purely decorative images as decorative so they’re skipped.

    EffortSmall

04 · Already working

What to keep

  • Product pages carried structured data, so Google could show price and stock in results.
  • The homepage didn't jump around as it loaded on a phone: no measurable layout shift.

05 · Roadmap

Fix now, fix soon, fine as is

Fix now

  • Full-page caching for logged-out visitors
  • Remove the duplicate and unused plugins
  • Homepage H1 and meta description

Fix soon

  • Profile the slowest plugins and queries
  • Load builder and slider code only where it's used
  • Alt text for product images

Fine as is

  • Product structured data
  • Stable homepage layout while loading

06 · Fix or rebuild

Our recommendation: rebuild

The quick fixes above are worth doing regardless: caching alone would take most of the waiting off cached pages. They don’t reach the cart, checkout or the admin, though, which can’t be cached, and they don’t touch what the team struggles with day to day: inventory managed through a rigid template, and database queries that time out.

Those come from the same place as the slow pages: a general-purpose stack carrying 15 plugins to do a specific business’s job. So the recommendation is a custom platform with only the code the store needs, an admin built around the team’s workflows, and payments and shipping connected directly instead of through plugins. For a store with standard needs, a hosted platform such as Shopify would have been the cheaper recommendation.

In this case the rebuild had already happened by the time of this audit, which is why the store can be shared: the next section shows how it measures now.

07 · The rebuild

The same store on its new platform

HomepageWooCommerce storeCustom platform
PageSpeed score (mobile)4198
Server response8.2 s0.2 s
Main content visible (mobile)20.7 s2.4 s
Page weight3.1 MB0.7 MB
Plugins150

The full story, method and every measurement are in the Great Lakes Additive case study.

08 · Method

How this was measured, and what's left out

  • Scores and timings in the findings come from Lighthouse 12.8 in headless Chrome with Google’s default mobile and desktop throttling, median of three runs per page. Server response was also measured directly, three times per page.
  • The scores in “The rebuild” come from Google’s PageSpeed Insights, which runs on Google’s machines and scored the same homepage 41 where our Lighthouse runs gave 54. Different machines give different numbers, so we always say which tool produced which figure.
  • Timings were measured on an archived copy of the store, running WordPress, WooCommerce and the same plugins.
  • Left out of this public version: the code, security and data-handling sections. In a client report those include specifics that should never be published, even for a retired system.

Next season starts here

Want this for your platform?

Tell us where your platform is today and where you want it to go. We will review your setup, show you what is holding it back, and outline a clear path forward.

  • Free, no-obligation consultation
  • Reply within one business day
  • Led by a principal architect