Every Portfolio Photo Labeled “Test Caption / Test Description Goes Like This”

The Situation

Chef Cindy Vescovi has spent years building a reputation for elegant corporate events, foundation galas, and wedding receptions. Her portfolio gallery shows all of that beautiful work — every photo labeled “Test Caption / Test Description goes like this.”

The Problem

Chef Cindy Vescovi runs a serious catering operation. Corporate award dinners. Foundation board galas. Wedding receptions at Evansville's premier venues. The food is elegant, the execution is professional, and the events Cindy has catered represent exactly the kind of high-stakes, high-detail work that builds lasting client relationships.

The portfolio on vescovicatering.com documents all of it. And every single photo in that gallery carries the same two labels:

Test Caption

Test Description goes like this

Not one photo. Every photo. The gallery was set up by a developer at some point — photos uploaded, lightbox configured, captions stubbed in as placeholders — and then the actual captions were never written. No event names. No menu descriptions. No venue callouts. Just “Test Caption / Test Description goes like this,” repeated next to every image of Cindy's work. This is the primary trust-building tool for a catering company that competes on elegance and detail. And it looks like no one ever finished setting it up.

What It Costs

The buyer for corporate catering is typically an executive assistant, an events manager, or a VP who has been tasked with finding someone credible. They look at the portfolio to answer one question: has this caterer done events like ours? The answer, based on what Vescovi's portfolio currently shows them, is: we don't know. There are photos, but no context. No event types. No scale. No venue partners. Just placeholder text where the substance should be.

A wedding couple browsing caterers goes to the portfolio for a different reason: they want to feel the experience. They want to see Cindy's work and imagine their reception. What they get is “Test Caption / Test Description goes like this” next to every image. The photos might be beautiful. The dummy text destroys the impression. For a catering company that depends heavily on word-of-mouth and referrals, a broken portfolio actively undermines every warm referral that lands on the site.

What a Redesign Would Unlock

A rebuilt portfolio for Vescovi Catering does what the current one cannot: it tells the story of each event. Every photo gets a real caption — the type of event, the venue, the food featured, the scale of the gathering.

What Pitchcraft Did

Pitchcraft built a full spec redesign concept for Vescovi Catering before any contact was made. The spec includes:

• →Rebuilt portfolio page — every photo captioned with real event type, venue descriptor, and menu highlights; gallery filterable by Corporate, Wedding, and Social/Private events
• →Separate buyer journey pages — dedicated Corporate Events page and Weddings & Celebrations page, each speaking to its specific audience
• →Chef Cindy Vescovi bio page — credentials, philosophy, and personal photo positioned as the primary trust signal
• →Homepage redesign — full-bleed event photography, “Request a Quote” above the fold, trust signals (years in business, event types served, Cindy's personal quote)
• →Quote request form — event date, type, guest count, venue, and contact info; positioned prominently on every page
• →Real testimonial section — replacing the absent social proof with real client quotes from corporate and wedding clients
• →SEO foundations — LocalBusiness schema, local keyword targeting for “catering Evansville IN,” “wedding catering Evansville,” “corporate catering Evansville,” and alt text on all portfolio images
• →Mobile optimization — full responsive redesign so corporate buyers and brides browsing on phones get the same quality experience

The spec was built to show Cindy exactly what Vescovi Catering could look like online — a portfolio that earns the trust the events deserve, not one that undermines it with developer placeholder text.