This post is going to be unusually concrete, because we’re doing something most “custom vs WordPress” comparisons don’t: we’re comparing two real websites built for the same business.
Mary Angels Home Care is a Pittsburgh-based in-home care company. They have both a WordPress version of their site live at maryangelshomecare.com and a custom-built Next.js version at mahc-website.vercel.app. Same business, same brand, same services. Two completely different approaches to delivering the website.
That’s the rarest thing in the agency world: an honest, controlled comparison. So instead of writing the usual abstract “it depends, here are some pros and cons” piece, we’re going to look at exactly what each version weighs, what it ships to the browser, how it converts, and what it costs to own.
By the end you’ll have a real framework for which one is right for your business — and we’ll be honest about both winners.
The Two Builds at a Glance
The WordPress build runs on Elementor (the most popular WordPress page builder), with SiteGround hosting and the SiteGround Optimizer plugin doing the CSS/JS combining and caching. This is the standard small business WordPress stack in 2026.
The custom build runs on Next.js (a React framework) deployed on Vercel’s edge network. Code-split JavaScript, modern CSS, no jQuery, no Elementor, no plugin ecosystem. This is what most engineering-led teams reach for when they want full control over performance and architecture.
Both sites serve the same purpose: get a Pittsburgh family with an elderly loved one to call 412-900-9354 or fill out a form.
Performance: The Page-Weight Comparison
We pulled the actual home page of both sites and measured what gets shipped to the browser. The numbers are real, from curl and direct asset downloads.
Initial HTML
| Site | HTML payload |
|---|---|
| WordPress (Elementor) | 223 KB |
| Custom (Next.js) | 216 KB |
These are almost identical, which is interesting. Modern Next.js apps do server-side rendering, so the initial HTML is actually full of content for the browser — just like WordPress. The first paint isn’t slower on a custom site than it is on WordPress. This is a myth.
Stylesheets (CSS)
This is where the gap shows up.
| Site | CSS payload | Notes |
|---|---|---|
| WordPress | ~596 KB | 493 KB combined SiteGround stylesheet + 103 KB Font Awesome |
| Custom | 64 KB | One Next.js compiled stylesheet |
The WordPress site ships 9x more CSS than the custom one. That’s not a fluke — it’s structural. WordPress + Elementor needs to ship the CSS for every block, widget, animation, and breakpoint Elementor knows about, plus icon fonts, plus the theme, plus plugin styles. The custom site ships only the styles that the actual page uses.
For users on a slow connection — and “slow” in 2026 means anyone on rural broadband, transit Wi-Fi, or a 5-year-old phone — that’s the difference between a page that renders in 1 second and one that paints in 4.
JavaScript
| Site | JS situation |
|---|---|
| WordPress | 7 script tags on initial HTML. jQuery (87 KB) + gtranslate (13 KB) + SiteGround combined bundle (289 KB) + WP core bundles, all parsing immediately |
| Custom | 1 script tag on initial HTML. Next.js bundles (~421 KB) loaded on-demand as the user interacts |
The custom site has a clever trick: it can defer most of its JavaScript until after the page renders, because Next.js code-splits everything by route. The WordPress site doesn’t — every plugin, jQuery, and Elementor’s animation library all parse before the user can interact.
Time to First Byte (TTFB)
| Site | Average TTFB |
|---|---|
| WordPress (SiteGround cached) | 247 ms |
| Custom (Vercel edge) | 290 ms |
This one surprised us — and it’s an honest win for WordPress. SiteGround’s full-page cache is genuinely fast for the first byte. Vercel is fast too, but the Next.js app does a tiny bit more work on the edge to compose the response.
The catch: TTFB is a small piece of perceived performance. By the time the browser actually paints the page, the WordPress site is still parsing 596 KB of CSS while the custom site has already finished rendering on 64 KB.
Performance verdict: Custom wins clearly on render performance, especially on mobile and slow connections. WordPress wins on raw server response time.
Conversion Architecture: Where the Real Money Is
Page weight matters, but the more interesting comparison is how each version is designed to convert visitors into phone calls and form submissions. This is where the gap gets bigger.
Phone Number Visibility
The WordPress site has the phone number +1 412-900-9354 in the header — but on a closer look, there’s a second number +412-318-4237 appearing elsewhere on the page. This is the kind of bug that happens when an Elementor site has been edited by multiple people over time without anyone catching the inconsistency. A visitor seeing two different numbers immediately wonders which one is correct.
The custom site shows 412-900-9354 once, consistently, in the header and as a sticky “Call” CTA in the hero.
Hero Headline
WordPress hero: “Pittsburgh’s Compassionate In-Home Care You Can Trust / Trusted Home Care in Pittsburgh, PA / Welcome to Mary Angels Home Care, your leading provider of personalized in-home care services.”
Custom hero: “In-Home Care in Pittsburgh / Care that feels like family / Trusted in-home care so your loved one can live safely and comfortably at home, across Pittsburgh and Allegheny County.”
The custom hero is shorter, more concrete (“feels like family”), and names the geographic service area (Allegheny County) which is great for SEO and for the buyer’s mental model. The WordPress version says “leading provider” — the kind of language families filter out as marketing fluff.
Forms
The WordPress site has a “Request Care Today” button that opens a contact form. Standard.
The custom site has a 3-step form visible in the hero (Full Name → Phone → Email, with a “1 of 3” progress indicator). Multi-step forms convert at 30-86% higher rates than single-page forms in study after study, because each step feels like a tiny commitment instead of a wall of fields.
Social Proof
WordPress: “Family-Owned · Licensed & Insured · Women-Owned” — three abstract trust badges.
Custom: “200+ Families served · 24/7 Care available · PA Licensed & insured · 5-Star On Google” — four specific, numerically-grounded trust signals.
Specific numbers convert. Abstract badges don’t.
FAQ Section
The custom site has a full FAQ accordion answering the questions families actually ask before they call: how quickly will someone call me, do you offer free assessments, can care start immediately, do you accept long-term care insurance, can I request a specific caregiver, what areas do you serve. Each answer is direct.
The WordPress site has no equivalent FAQ block on the homepage. Visitors with questions have to navigate to a separate page or call without their concerns addressed.
Bilingual Support
WordPress uses the gtranslate plugin — Google-translated, prone to mistranslating medical/care terminology. The custom site has a real en/es toggle built into the architecture, allowing professionally-translated copy. For a home care business serving Pittsburgh’s significant Spanish-speaking community, that’s a real conversion difference, not a cosmetic one.
Conversion verdict: Custom wins by a meaningful margin. The 3-step form alone is likely to deliver a 20-40% conversion lift, and the FAQ + specific trust signals stack on top of that.
SEO Comparison
Both sites have the basics right — title tag, meta description, schema markup. The WordPress title (“Home Care Pittsburgh PA | Mary Angels Home Care — Free Visit”) has the keyword phrase at the front, which is the textbook SEO move. The custom title (“Mary Angels Home Care | In-Home Care in Pittsburgh, PA”) has the brand first.
Google uses Core Web Vitals as a ranking signal. The custom site will reliably score higher on LCP (Largest Contentful Paint) because of the leaner CSS payload. On mobile, that 9x CSS gap could translate into a 1-2 point Core Web Vitals advantage — small but real.
SEO verdict: Roughly tied for ranking factors, custom slightly ahead on Core Web Vitals.
Ownership and Maintenance
This is the section most agency websites won’t write honestly. We’re going to.
WordPress
- You own the content in a database
- You don’t own the page builder — Elementor is a third-party product
- You’re dependent on plugins for almost every advanced feature
- Updates require regular maintenance — WP core, plugins, theme, PHP
- Edits are accessible to non-technical team members through Elementor’s visual editor
- Hosting: $20-50/month for managed host like SiteGround or WP Engine
Custom (Next.js)
- You own the code outright — every line of it
- No page builder dependency
- No plugin dependency
- Updates are deliberate — no surprise breaking changes
- Edits require a developer for design changes
- Hosting: $0-25/month on Vercel for typical small business traffic
When WordPress Is the Right Call
- You’re a non-technical owner who needs to update content weekly without calling a developer
- Budget is under $5,000 and timeline is under 30 days
- Your site is content-heavy (blog-first, lots of editorial updates)
- You want easy access to plugins for features like e-commerce or membership
When Custom Is the Right Call
- Conversion rate matters because you’re spending real money on traffic ($1,500+/month on ads)
- Performance matters because mobile users are 60%+ of your traffic
- You have a long-term technical partner who can maintain the codebase
- You want every detail of UX dialed in — multi-step forms, custom calculators, embedded apps
- You want the website to feel distinctly different from every WordPress competitor in your space
This is what we build at D1TechCreative for clients where the math works.
The Honest Recommendation for Mary Angels
For a Pittsburgh home care business that is family-owned (no in-house dev team), has staff who update copy occasionally, likely runs paid ads to the homepage, serves a high-intent emotional buyer (family member of an elder), and needs Spanish-language support:
The right answer is: the custom site as the customer-facing front, with a headless CMS so staff can edit copy without a developer. The conversion lift from the multi-step form, the FAQ, the cleaner architecture, and the bilingual support is going to deliver more booked free visits per month than the WordPress version.
The 5-Question Test for Your Business
- Are you spending more than $1,500/month on paid traffic to your site?
- Is your average customer value more than $1,000?
- Do you (or your team) need to edit copy weekly?
- Do you have a developer relationship?
- Do you want the site to feel distinctly different from competitors?
Three or more yeses on 1, 2, and 5 → custom is the right call. Two or more yeses on 3 and 4 → WordPress is the right call. Both → custom with a CMS layer.
FAQ
Can a custom website be edited by non-developers? Yes — when you build it with a headless CMS layer. Staff can edit copy, swap images, and update pages without touching code.
Is WordPress slower than a custom site by default? Usually, yes — but not always. A well-built WordPress site with proper caching can score 90+ on Lighthouse. The default Elementor + standard hosting stack ships much more CSS and JS than necessary.
Will my SEO suffer if I switch from WordPress to custom? Only if you don’t plan the migration. With 301 redirects, schema markup ported, and the sitemap updated, SEO recovers fully within 30-60 days and often improves due to better Core Web Vitals.
Can I use both — custom homepage + WordPress for blog? Yes, and this is a smart pattern. High-traffic, conversion-critical pages live in the custom build. The blog stays in WordPress where editorial workflow is easier.
Is hosting more expensive for custom sites? Usually less expensive. Vercel and Netlify have generous free tiers and cap at $20-25/month for typical small business traffic.
Want an Honest Recommendation for Your Business?
We build both WordPress and custom websites for service businesses. We’ll look at your traffic, your team, your conversion goals, and your budget, and tell you honestly which one is right. No upsell to custom if WordPress is the better call.
Book your free strategy call →
Or call us directly: (888) 330-1434.
D1TechCreative builds custom websites, WordPress sites, headless CMS architectures, AI voice agents, CRMs, and lead generation systems for service businesses across the United States. Based in Fort Lauderdale, FL.