Make the specialist work visible.
Cleanroom, laboratory and workplace cleaning lead the story. Nine service routes, seven industry routes and four regional routes help a buyer enter through the work, building or location that matters.
Add Life Facilities Services / Case studyThe website
The website
is a site walk.
Cleanroom, laboratory and workplace services, made easier to understand. A clearer identity, a room-by-room story and a useful next step for facilities buyers.
- Work
- Cleanroom + facility services
- Place
- Santa Clara, California
Brandcore brought Add Life’s supplied identity, specialist service story and inquiry path together around the site walk. The candidate shows how each room’s requirements become a written scope, then gives the visitor a direct way to start that conversation.
October 24, 2026 capture. The new site is a launch candidate at addlife.bcio.net; production activation and client approval remain separate, unconfirmed milestones.
01 / The visible work
Move the line.
See the change.
Compare the actual websites. Choose a recorded phase, switch to the phone view, or open either capture at its original size.
Drag anywhere across the image or use the slider. With the slider focused, use arrow keys, Home or End. Phone captures retain vertical page scrolling.
Before cutover · October 24, 2026 · Preserved live website
The maintained one-page WordPress homepage, captured at https://www.addlifeserve.com/ before cutover. The page’s experience wording refers to the team’s combined experience; the company founding year is not established.
Open earlier capture ↗Next.js preview · October 24, 2026 · The site-walk candidate
The Next.js launch candidate at https://addlife.bcio.net/, captured with the same desktop and phone basis. The facility cutaway and generated service scenes are illustrations, not photographs of named customer work.
Open later capture ↗The identity / Actual artwork
Recognisable.
Carried forward.
Actual retained artwork makes the progression visible. The current WordPress mark is preserved beside the supplied AL identity used throughout the new candidate. Neither is a generated approximation.
Preserved WordPress identity
Exact 425 × 100 PNG recovered from the current WordPress upload URL. Its 2021 upload path is an asset clue, not a verified website launch date.
Supplied AL identity
Actual project-export SVG lockup. The candidate uses its source geometry and complete company name across the page system and motion.
The record / Observed website eras
Keep the
source trail.
The public comparison shows the preserved live WordPress site and the captured Next.js candidate. Retained source exports and intermediate implementation drafts remain cataloged in the private review.
A verified November 2021 HTML record extends the source history. Its original assets are not recovered, so the public visual comparison remains the preserved October 2026 WordPress site and the captured launch candidate. Superseded draft pages stay private; source dates are not launch or founding dates.
- November 27, 2021 · observed source
A verified earlier WordPress record.
Common Crawl preserved Add Life homepage HTML at 10:53:16 UTC. Its WARC payload digest is verified. This is a dated source observation, not a launch or founding date. The original 2021 assets are not recovered or presumed unchanged, so no faithful 2021 design replay is claimed.
Open dated archive source ↗ - June 2026 source record
The retained starting material.
Project records identify a June 2, 2026 export of the owner’s WordPress content. This supports content provenance, not a verified original launch date.
- October 23, 2026
A recorded preview release.
The current project receipt identifies a deployed preview with the owner profile, customer copy, metadata and native forms. Production activation remains conditional.
- October 24, 2026
A dated before-and-after record.
The live response and candidate were captured at matched desktop and phone sizes, then measured under one clean Lighthouse method before any verified cutover.
02 / What we built
The system
behind the screen.
Let the process explain the promise.
The illustrative facility walk connects room-by-room notes to a written scope, onboarding, the first shift and review. Informative motion shows how the service plan takes shape.
Keep the company recognizable.
The supplied AL identity, full company name, navy and green palette and real owner profile carry across the system. Personal portraits retain their supplied appearance; generated scenes are identified as illustrations.
Give interest a concrete next step.
The repeated request is a site walk. Four required proposal fields lead into structured capture and a signed CRM handoff capability. Notification rollout and production routing remain separately verified.
03 / Retained speed evidence
The main content arrives sooner.
Median mobile main-content paint fell from 21.06 seconds on the preserved live site to 1.44 seconds on the launch candidate in the matched lab set. The mobile performance score changed from 62 to 100; desktop changed from 71 to 100.
October 24, 2026 · 16:54–16:57 UTC · Homepage Lighthouse performance scores / 100
| Tested version | Mobile | Desktop | Mobile main-content paint (LCP) |
|---|---|---|---|
| Preserved live WordPress homepage | 62 | 71 | 21.06 s |
| Next.js launch candidate | 100 | 100 | 1.44 s |
| Device / version | LCP | FCP | TBT | CLS | Transfer |
|---|---|---|---|---|---|
| Mobile · Preserved live WordPressPerformance 61–62; LCP 20.990–21.235 s; transfer 4,514,543–6,028,577 bytes; n=3 | 21.057 s | 5.266 s | 26.5 ms | 0.000 | 4,528,122 bytes |
| Mobile · Next.js launch candidatePerformance 100–100; LCP 1.434–1.439 s; transfer 395,047–395,070 bytes; n=3 | 1.437 s | 1.119 s | 5.5 ms | 0.000 | 395,070 bytes |
| Desktop · Preserved live WordPressPerformance 70–71; LCP 4.169–4.600 s; transfer 4,689,453–4,710,065 bytes; n=3 | 4.585 s | 1.453 s | 0.0 ms | 0.000 | 4,703,936 bytes |
| Desktop · Next.js launch candidatePerformance 100–100; LCP 0.368–0.375 s; transfer 442,532–442,555 bytes; n=3 | 0.375 s | 0.306 s | 0.0 ms | 0.000 | 442,555 bytes |
Read the test method and its limits
Lighthouse 13.5.0, Chrome 156.0.8078.47 and Node 24.21.0 on the same clean Linux rig. Three interleaved homepage runs per version and device, fresh isolated Chrome profiles, standard simulated mobile/desktop presets and sequential low-priority collection. Values are medians; source HTML and redirects were recorded before and after every run.
- The candidate remains prelaunch and deliberately noindex. Its SEO score of 69 reflects that staging control; accessibility and best practices scored 100 in all six candidate runs.
- Lab results describe the measured URLs and time, not field Core Web Vitals, historical provider performance or guaranteed production results.
- Earlier local diagnostic samples included injected system scripts and are excluded from these medians. Raw reports, unsuccessful diagnostics and method details remain in private review.
- The scoped analytics check does not establish historical traffic or ranking growth. No increase in qualified leads, contracts or revenue is claimed.
04 / Explore the captured sites
Open a page.
Follow the details.
Browse the locally preserved website versions. Each demo identifies its capture or reconstruction. Forms, ordering and account actions are disabled; these captures document a website state.
05 / The source trail
Real sites. Retained evidence.
The visual comparison and selected lab record document the work at the stated dates. The complete original report and supporting files remain available through detailed review access.
Your next chapter
Make the work
speak for itself.
A stronger identity, a faster website and a useful path from interest to conversation. Built as one system.