Reference
Small, fast, self-contained, how I kept it that way
Page speed is money, this page explains where My T Maker’s smallness comes from.
Page speed is money, slow product pages lose customers before they ever touch the designer. My T Maker is engineered to stay light, and this page explains where the smallness comes from.
The philosophy: one lean app, zero freeloaders
Most designer plugins arrive as a framework plus a dozen libraries plus a telemetry stack. My T Maker ships as one self-contained application:
- No trackers, no analytics beacons, no telemetry. No analytics beacon leaves your site, nothing profiles your visitors, and the designer adds no cookie-banner burden to your site. The stats dashboard is native WordPress data on your own server.
- No page-wide footprint. Everything the designer needs, app, config, fonts, libraries, loads only on the page with the shortcode. It doesn’t inject scripts across your whole site or slow down pages it isn’t on.
- A short dependency list, self-hosted. The canvas engine (Fabric.js) and the PDF export libraries ship inside the plugin and load from your own domain, so no outside CDN can slow the designer down or break it. The only external request left is the Google Fonts stylesheet for the display fonts. No font walls, no 3D engines, no tag managers.
- The heavy work happens in the browser. The background remover, the canvas, the mockup rendering, all client-side. Your server isn’t rendering images for every visitor, so the designer runs fine on ordinary shared hosting.
Weight is a feature I maintain
Every release gets weighed. Recent examples of the diet:
- A single optimization pass cut ~394 KB from first load by trimming and deferring what the first paint doesn’t need.
- The exclusive BEEFY display fonts (the biggest single assets in the app) now ship as WOFF2, the modern compressed font format, typically 50–70% smaller for the same glyphs. They also lazy-load: a face downloads only when a design actually uses it, instead of riding along on every page view.
- Options that genuinely cost memory (custom background images, art-library preloading, custom watermark files) say so right in the admin, and every one can be switched off, you choose where the bytes go.
What this means on real hosting
- Works on standard shared hosting, no VPS requirement, no Redis requirement, no build step.
- Plays well with caching plugins (one rule: exclude the designer page from JS minification, see troubleshooting).
- Phone-first weight budget: the designer is used from customer phones on cell connections, and it’s built like it knows that.
Why competitors’ approach costs you
A designer that loads a 3D engine, four font CDNs, and a telemetry stack doesn’t just load slow, it drags your Core Web Vitals, and those feed your search ranking. A lean designer isn’t a technical vanity metric; it’s your product page staying fast enough that Google and your customers both like it.
Numbers on this page are maintained per release. Currently measured on the live demo: the designer page document, with the entire app inlined, transfers about 179 KB compressed; the canvas engine adds about 90 KB compressed. A first visit to the designer costs roughly 270 KB in total. The plugin download itself is 9.5 MB, and most of that is the 1,000+ piece art library that ships inside it.
Need a hand?
Use the contact form, answered by a working print shop within 1–2 business days.
