Back to Guides
Development

Why Lebanese Business Websites Are Slow: The Real Cost of WordPress and Shopify Defaults

WordPress runs over 40% of the web and Shopify powers close to a third of online stores — but HTTP Archive's own 2025 data shows WordPress passing Core Web Vitals only 45% of the time. Here's what's actually true about speed and platform lock-in, and what still isn't.

Ibrahim Shanaa

Ibrahim Shanaa

Aug 8, 2026/9 min read

Web design and user interface illustration representing website structure and layout

This isn't really a "WordPress vs. custom" argument

WordPress runs an estimated 41.2% of all websites, and Shopify powers roughly a third of e-commerce sites specifically, according to W3Techs' live usage tracking. Those numbers alone should settle any claim that either platform is fundamentally broken — millions of businesses use both successfully. The more useful question isn't whether WordPress or Shopify are bad platforms. It's why so many real-world implementations of them, especially budget-constrained ones, end up slow and hard to change.

That distinction matters because most articles on this topic go one of two ways: agency blogs selling custom development that treat WordPress as uniformly terrible, or platform loyalists who dismiss every performance complaint as user error. Neither is fully honest. What follows is what the actual, dated data shows, including where that data runs out.

What HTTP Archive's own data actually shows

The strongest evidence here comes from HTTP Archive's Web Almanac, an independent, methodology-disclosed annual study of the real web, not a vendor's marketing claim. Its 2025 CMS chapter found WordPress sites pass Core Web Vitals, Google's real-user speed and stability benchmark, on mobile only 45% of the time: the lowest pass rate among the major named platforms it tracks. TYPO3 (79%) and Duda (85%) outperform it clearly, and even Wix, up sharply to 74% from 55% the year before, now beats it too.

Looking closer at the breakdown, WordPress's specific weak point is Largest Contentful Paint, the time it takes the main content to appear, where only 53% of WordPress sites score "good." Its layout stability (CLS) is actually reasonable at around 84%, comparable to Duda and Squarespace. In other words, WordPress sites generally aren't unstable or broken, they're specifically slow to show their main content, which is a symptom with identifiable causes rather than a platform-wide flaw.

Why WordPress sites specifically struggle

The Web Almanac's own researchers attribute the spread in WordPress performance to configuration choices layered on top of the software, not WordPress core itself: hosting quality, theme choice, plugins, and page builders. That distinction is worth taking seriously rather than dismissing as spin. Google's own guidance on fixing Largest Contentful Paint points to slow server response times, render-blocking scripts and styles, and unoptimized images as the usual causes, none of which are unique to WordPress, but all of which are unusually easy to accumulate on it.

The scale of that accumulation is measurable. Elementor, a drag-and-drop page builder, runs on 31.4% of all WordPress sites overall and 43% of the WordPress sites specifically measured in the Web Almanac's mobile dataset, more than double the share using WordPress's lighter, native block editor. WooCommerce, which adds a full e-commerce layer, runs on close to 20% of WordPress sites. Every plugin and builder layer adds code that has to load, and a site built cheaply on shared hosting with several of these stacked on top rarely has anyone checking what that's doing to load time.

The Shopify lock-in that's real, and what's actually changed

Shopify's checkout limitations are frequently described using outdated information, so it's worth being precise about what's current. Shopify fully retired its old, freely-editable checkout.liquid template in August 2025, replacing it with a more structured "Checkout Extensibility" system. Standard-tier stores that haven't migrated will be automatically upgraded, with legacy customizations stripped out, by August 26, 2026.

What that means practically: real checkout customization — custom fields, upsells, custom logic beyond basic branding — now requires Shopify Plus, a materially more expensive tier, and even then it only works through Shopify-defined extension points. If there's no extension point for what you want to build, it can't be built, regardless of budget. This is a genuine, current constraint, not stale complaint, and it's the clearest example of the trade brands make for Shopify's ease of setup: fast to launch, but the ceiling on what you can customize is real and enforced by the platform itself, not just a skills gap.

Why this matters more in Lebanon specifically

Slow-loading sites are a compounding problem in Lebanon, not just a general web performance issue. DataReportal's Digital 2026: Lebanon report puts the country's median fixed broadband speed at 16.13 Mbps and median mobile speed at 43.90 Mbps as of 2025, figures well below what's typical in markets with more built-out fixed infrastructure. A website that's already slow to load compounds that gap for real visitors rather than existing in isolation from it.

On CMS usage specifically, one industry tracker estimates WordPress accounts for a majority of tracked Lebanese websites, though that figure comes from a single source whose exact methodology for attributing sites to Lebanon couldn't be fully confirmed, so it's presented here as a directional estimate, not a firm number. What is firmly established is that no Lebanon-specific Core Web Vitals or hosting-quality study exists in any public, checkable source. Any article claiming an exact "X% of Lebanese websites fail Core Web Vitals" figure is citing a number that doesn't exist yet — this one included, which is exactly why we're not going to.

What's actually worth the tradeoff, and when

None of this means WordPress or Shopify are the wrong choice for every business. A brand testing an idea, running a simple brochure site, or launching a small store quickly has good reasons to start on a platform that's fast to set up and well understood. The tradeoff becomes worth solving once a site's traffic, sales, or customization needs start to matter, and once a slow load time or a blocked checkout feature is visibly costing leads or sales, not before.

The practical questions worth asking before committing to either path are the same three every time: how much does the platform's default performance ceiling matter for this specific business, how much genuine customization will actually be needed as it grows, and is there a real plan, and budget, for maintaining whichever platform is chosen. Custom development removes the platform's ceiling entirely, but it only pays off once a business is actually going to hit that ceiling.

Core Web Vitals pass rate by platform

% passing Core Web Vitals (mobile)

Share of sites on each platform passing Google's Core Web Vitals on mobile, most recent measured data.

Core Web Vitals pass rate by platform
CategoryValue (% passing Core Web Vitals (mobile))
Duda85%
TYPO379%
Shopify75%
Wix74%
Squarespace68%
Drupal59%
Weebly47%
WordPress45%

Duda, TYPO3, Wix, and Weebly figures are from HTTP Archive's Web Almanac 2025 CMS chapter (Tier 1). Shopify, Squarespace, and Drupal figures are from Search Engine Journal's independent analysis of the same June 2025 CrUX/HTTP Archive dataset (Tier 3), used because the Web Almanac's own fetched summary didn't break those three out separately; WordPress appears in both (45% Almanac, 43.44% SEJ) and is shown at the Almanac figure. No tier 1-3 source publishes a comparable figure for custom-built (no-CMS) sites — do not assume one.

Frequently asked questions

Want a site that doesn't inherit these limits?

Aranbis builds custom, performance-first websites and online stores for Lebanese businesses, grounded in what the Core Web Vitals data actually shows, not what's easiest to build with a page builder.

Talk to Aranbis

Strategy. Design. Technology.

One team. One process. Real results.

Looking for shorter, faster reads instead?

Browse Insights
We use cookies to ensure you get the best experience on our website. For more information on how we use cookies, please see our cookie policy.