alloy digital

Truckworx — Current Site vs. Concept Redesign

Prospect: Truckworx · Site: truckworx.com (WordPress) · Evidence: alloy-prospect-recon (2026-06-18) + CWV proof (PageSpeed Insights, 2026-06-19/22)

Honesty guardrail. Left = the measured problems behind each pin. Right = concept art (illustrative, not a live build). Real-user mobile LCP is 2.1 s ("Fast") — we do NOT claim the site is slow.

🔒 truckworx.com

Current state · measured

1 2 3 4 5

Live screenshot — Truckworx's current homepage, captured at desktop resolution (2880×2000px). Click each numbered pin for the measured finding.

Three eras of tech stitched together Measured

WordPress + an external Kenworth parts system + a live legacy parts.aspx (ASP.NET) page. Buyers bounce between environments.

Source: alloy-prospect-recon, 2026-06-18 (verified off live pages)

No structured data anywhere Measured

No LocalBusiness / AutoDealer / Vehicle schema on homepage, locations, or inventory.

Source: alloy-prospect-recon, 2026-06-18 (homepage, /locations/, /inventory/)

High-intent parts buyer leaves the site Measured

Parts ordering hands off to partscounter.kenworth.com — the dealer loses session + data.

Source: alloy-prospect-recon, 2026-06-18

Can't shop or rank by branch Measured

~16 branch URLs, but inventory isn't filterable by location and branch pages lack NAP / maps / per-branch schema.

Source: alloy-prospect-recon, 2026-06-18

Page bloat + desktop layout shift Measured

~2.9 MB page, ~1.4 s unused JS; real-user desktop CLS 0.34 ('Slow'). Mobile Lighthouse 50-56/100.

Source: PageSpeed Insights lab + CrUX field, 2026-06-19/22

🔒 truckworx.com

Concept art · illustrative

Concept direction

One unified site — built around how buyers actually shop.

An illustrative redesign that resolves each measured finding below. Concept art — not a live build or quoted scope.

Findings, before → after

Finding 01

Three eras of tech stitched together

NowWordPress + an external Kenworth parts system + a live legacy parts.aspx (ASP.NET) page. Buyers bounce between environments.

ConceptOne custom CMS where trucks, parts, and service live in a single flow.

Measured: alloy-prospect-recon, 2026-06-18 (verified off live pages)

Finding 02

No structured data anywhere

NowNo LocalBusiness / AutoDealer / Vehicle schema on homepage, locations, or inventory.

ConceptFull schema markup so Google generates 'near me' cards + per-branch knowledge panels.

Measured: alloy-prospect-recon, 2026-06-18 (homepage, /locations/, /inventory/)

Finding 03

High-intent parts buyer leaves the site

NowParts ordering hands off to partscounter.kenworth.com — the dealer loses session + data.

ConceptOn-site parts ordering integrated into the unified flow; no off-site hand-off.

Measured: alloy-prospect-recon, 2026-06-18

Finding 04

Can't shop or rank by branch

Now~16 branch URLs, but inventory isn't filterable by location and branch pages lack NAP / maps / per-branch schema.

Concept'In stock at your branch' filtering + full NAP + per-branch schema = local rankings in every city.

Measured: alloy-prospect-recon, 2026-06-18

Finding 05

Page bloat + desktop layout shift

Now~2.9 MB page, ~1.4 s unused JS; real-user desktop CLS 0.34 ('Slow'). Mobile Lighthouse 50-56/100.

ConceptLean bundle + reserved layout space -> CLS toward 0.0, lighter payload, faster paint.

Measured: PageSpeed Insights lab + CrUX field, 2026-06-19/22

Measured Core Web Vitals — the honest read

Pulled via Google PageSpeed Insights (psi_cwv.py). Field (CrUX) = real users; we lead with what actually fails, never "feels slow."

Metric	Mobile	Desktop	Field — real users (CrUX)	Verdict
Perf score	50-56	71-72	—	Mobile under bar
LCP	17.3 s (lab)	1.4-1.7 s	mobile 2.1 s (Fast)	Mobile real-user Fast
CLS	0	0.43-0.48	desktop 0.34	Slow — the real fail
Unused JS / weight	~1.4 s unused JS · ~2.9 MB		—	Bloat — lean upside