Source library
Customers can browse curated designs and customize from there. This is especially helpful for customers who used stock images on the previous site and want a familiar starting point.
2.0 performance notes
A faster ordering site, measured in the places customers actually use.
Apparel Decorating Network 2.0 is not just a fresh coat of paint. We rebuilt the customer ordering path, production handoff, file handling, and reliability checks so the site feels quicker and gives us better visibility when something slows down.
Overall page speed
3.4x
Average slower-end improvement across common public pages.
Home page
7.8x
607ms on the previous site, 78ms on 2.0.
Cart page
2.1x
178ms on the previous site, 86ms on 2.0.
The measured page comparison
This first comparison used 20 safe page checks against the previous live site and Apparel Decorating Network 2.0. The numbers below use the slower end of normal responses, so they are more useful than cherry-picking the single fastest load.
| Page | Previous site | 2.0 | Improvement |
|---|---|---|---|
| HomeThe first page many customers see. | 607ms | 78ms | 7.8x faster |
| LoginThe gateway into account orders and invoices. | 110ms | 78ms | 1.4x faster |
| CartThe place customers upload, size, price, and order. | 178ms | 86ms | 2.1x faster |
| Health checkThe basic uptime and readiness check. | 184ms | 75ms | 2.5x faster |
Plain English version: the pages customers hit most often are responding faster, and 2.0 gives us better tools to see exactly where a slowdown happens if one appears.
Customer ordering workflow
The most important customer path is simple: open the order page, upload art, set size and quantity, confirm pricing, and get the order into production. The rebuild makes that path easier to measure and easier to support.
| Action | Previous site | 2.0 | What we can prove now |
|---|---|---|---|
| Open cart | Loaded the ordering page in about 178ms on the slower end of the benchmark. | Loaded the cart page in about 86ms on the same benchmark. | 2.1x fasterMeasured May 21, 2026 |
| Change quantity | Harder to isolate from the larger page flow. | Tracked separately as its own cart action, so pricing and quantity changes can be timed directly. | Instrumented in 2.0 |
| Upload artwork | Uploads worked, but timing and preview failures were harder to diagnose from the outside. | Uploads, previews, cart items, and cleanup are measured as separate steps during guarded workflow checks. | Tracked step by step |
| Order confirmation | Immediate-pay and weekly-billing paths existed, but the operational proof depended more on logs and manual review. | Checkout, payment reconciliation, order records, confirmation email handling, and production sync have dedicated tests and smoke checks. | More observable |
Artwork tools and Source
Artwork is where a lot of customer time is spent. 2.0 brings stock images, uploaded files, background removal, resizing, and order previewing into one connected flow instead of scattering those steps across disconnected tools.
Upload previews
Fresh uploads now render as visible previews in the studio, the gallery, the cart, and admin order review, giving customers and operators a shared visual reference.
Background and resize tools
Background cleanup and artwork sizing are part of the same ordering workspace, so customers can prepare art and price it without bouncing between screens.
Performance watchlist
AI and artwork actions can depend on outside providers, so 2.0 tracks those paths separately. If the slowdown is the site, storage, or an AI provider, we have a cleaner way to tell.
Admin production workflow
The customer-facing speed matters, but production speed matters too. The new admin tooling is being measured around the places operators spend their day: new orders, production queues, artwork previews, invoices, payments, companies, and users.
| Admin action | 2.0 proof point | Why it matters |
|---|---|---|
| Open new orders | Recent admin profiling checks the orders list, production tab, search, filters, sorting, and pagination. | Operators can find the next order to produce without guessing whether a page is slow because of search, filters, images, or database queries. |
| Review artwork | Order items show artwork previews, physical dimensions, quantity, pricing, and full-view access in the same order review flow. | Production should not have to hunt through separate pages just to understand what needs printed. |
| Move production forward | Production status controls are visible in the admin order flow and covered by targeted tests. | Status changes need to be clear, reversible where appropriate, and reflected in the right places during the cutover period. |
| Manage invoices and payments | Invoices, payments, manual payments, traded status, refunds, and weekly billing have dedicated code paths and tests. | Money workflows need ledger entries and auditability, not just a visual paid/unpaid label. |
The previous admin experience did the job, but it gave us fewer built-in signals. In 2.0, performance reports can include page timing, query counts, slow-query signals, queue depth, failed jobs, and workflow-specific timing.
How we are measuring it
The first published numbers above are one-to-one public page checks. For deeper operational work, 2.0 can combine route timing, workflow benchmarks, admin page profiles, queue health, database slow-query signals, and failed-job counts. That is the real difference: when something feels slow, we can measure the exact path and fix that path instead of guessing.
What we will keep measuring
A rebuild is not a one-time victory lap. The goal is to keep a scoreboard around the work customers and operators actually do.
Upload to checkout
How long it takes a customer to upload artwork, see the preview, adjust quantity, and reach checkout.
AI Studio readiness
How quickly the studio, gallery, Source library, and provider-backed actions become usable.
Admin production handling
How quickly an operator can find a new order, inspect art, confirm details, and take the next production action.
Billing reliability
Whether invoices, payments, refunds, manual settlement, and weekly billing stay reconciled as more customers move over.