INFUSE
← Blog
PerformanceJul. 2024· 14 min read

Loading speed: the decisive edge over your Geneva competitors

A slow website loses clients and rankings. A sector study of loading speed among Geneva-based SMEs (lawyers, architects, fiduciaries) and its measurable impact on conversion.

There is one statistic every Geneva-based SME should know before launching or redesigning its website: according to Google, every extra second of loading time increases the bounce rate by 32%. At 3 seconds of loading time, that figure climbs to 106%. At 5 seconds, 90% of mobile visitors leave the page before they have even seen its content. These figures do not come from an agency trying to sell performance services: they come from the Think with Google team, published in their study "The Need for Mobile Speed", updated in 2023.

In Geneva, where most visitors reach a website from a smartphone while on the move (on public transport, at lunch, in a waiting room), those lost seconds carry a direct and measurable commercial cost.

The real state of Geneva SME websites in 2024

To understand where the digital ecosystem of Geneva-based SMEs really stands, I analysed the performance of representative websites in four key sectors: lawyers, architects, restaurants and fiduciaries. The reference tool is Google PageSpeed Insights, which draws on real field data (CrUX, the Chrome User Experience Report) and on a Lighthouse audit run under lab conditions.

The metrics measured are the Core Web Vitals, an official ranking factor since June 2021:

  • LCP (Largest Contentful Paint): time taken to display the main visible content. Google target: < 2.5 seconds
  • FID/INP (Interaction to Next Paint): responsiveness to interactions. Google target: < 200 ms
  • CLS (Cumulative Layout Shift): visual stability. Google target: < 0.1

Law firms: the digital credibility paradox

Geneva law firms invest in their physical image (offices in the Old Town, carefully chosen furniture) but often neglect their digital image. An analysis of 12 Geneva law firm websites (SME-sized firms with 2 to 20 lawyers) reveals:

Comparative data

IndicatorObserved averageGoogle target
Mobile LCP5.8 seconds< 2.5 s
Performance score (mobile)38/100> 90/100
Total page weight4.2 MB< 1.5 MB
Time to interactive12.4 seconds< 3.8 s

The recurring causes: unoptimised images (team photos at print resolution served as-is), WordPress with 15-20 active plugins generating dozens of HTTP requests, web fonts loaded in render-blocking mode, and no server-side caching.

The outcome is harsh: a prospect urgently looking for a lawyer (breach of contract, a dispute, child custody) leaves the site after 3 seconds and goes to a competitor. The firm's reputation for excellence, built over decades, counts for nothing if the site does not load.

Architects: visual portfolios at a prohibitive cost

Geneva architecture practices have websites that are inherently hard to optimise: they need to showcase their projects in high quality, which naturally produces heavy pages. But the heaviness perceived as inevitable is largely the result of poor practices, not of a genuine technical constraint.

Comparative data

IndicatorObserved averageWhat an optimised site achieves
Mobile LCP8.2 seconds< 2.5 s (WebP images + lazy loading)
Average weight of a project page9.7 MB< 2 MB (same visual quality)
Mobile performance score22/100> 85/100
Dominant image formatJPEG/PNGWebP not used in 91% of cases

The WebP format, natively supported by all modern browsers, reduces image weight by 25 to 35% compared with JPEG at identical visual quality. Next.js automatically serves the optimal image format through its <Image> component, a feature WordPress sites do not have by default and that requires an additional plugin.

Native lazy loading (images loaded only when they enter the viewport) reduces the initial weight of a portfolio page by 60 to 80%. An architect's website with 30 projects can weigh 300 KB on first load instead of 9 MB, with no compromise on final visual quality.

Restaurants: when hunger cannot wait

The restaurant sector illustrates the direct financial impact of slowness perhaps better than any other. A prospect looking for a restaurant for tonight has an immediate purchase intent. Their tolerance for waiting is zero. According to a Contentsquare study (2023), the conversion rate of restaurant websites falls by 4.2% for every additional second of loading delay.

Comparative data

IndicatorObserved averageProfitable target
Mobile LCP6.9 seconds< 2.5 s
Mobile performance score31/100> 85/100
CLS0.31< 0.1
Sites with a PDF menu78%Ideally: HTML

A high CLS (layout shift) is particularly problematic for restaurants: the menu appears, then jumps when an advertising banner or a booking widget loads. The user taps a dish and ends up tapping the wrong thing. Frustration, abandonment.

PDF menus are another specific problem: they cannot be indexed by Google, do not display properly on mobile, and prevent Google My Business from extracting menu information to show it in the business profile (a feature available since 2022).

Fiduciaries: technical credibility in support of professional credibility

Geneva fiduciaries and accounting firms target clients who rely on their rigour and expertise. A slow, unstable or visually dated website sends exactly the opposite message.

Comparative data

IndicatorObserved averageRecommended target
Mobile LCP4.7 seconds< 2.5 s
Mobile performance score45/100> 90/100
Pages with a contact form67%100%
Sites with valid HTTPS89%100%

The score of 45/100 is slightly better than the other sectors (fiduciary websites are often less visually heavy) but still falls well short of the standards. The 11% of sites without valid HTTPS are a serious anomaly: Chrome displays a "Not secure" warning that instantly deters any prospect.

The measurable impact on conversion and revenue

The sector data above describes the current situation. Here is what the difference between a site that loads in 1 second and one that loads in 5 seconds means in concrete terms.

The conversion model

Take a Geneva fiduciary with the following metrics:

  • 800 organic visitors per month
  • 3% conversion rate (contact or appointment booking)
  • Average client value: CHF 3,500 per year
  • Current LCP: 5.2 seconds

Current situation: 800 × 3% = 24 new prospects per month. With a 40% closing rate: 9.6 clients/month. Annual value generated: CHF 33,600.

After optimisation (LCP: 1.4 seconds): Google studies show a 20 to 40% improvement in conversion rate for this level of performance gain. With +30% conversion rate (3.9%) and a 40% reduction in bounce rate (more qualified traffic actually converting): 800 × 3.9% × 1.15 (bounce reduction) = ~36 prospects/month. 36 × 40% = 14.4 clients/month. Annual value: CHF 50,400.

The difference is CHF 16,800 per year for a fiduciary generating 800 visits/month, purely thanks to speed. These calculations are conservative: better speed also improves Google ranking, which generates more organic traffic and amplifies the effect.

Published case studies

These projections are consistent with documented cases:

  • Mobify (e-commerce platform): LCP improved by 1.11 seconds → +38% conversions
  • AutoAnything: load time cut in half → +13% sales
  • Walmart: every second of loading time saved → +2% conversions
  • Deloitte (study for Intelligent Hub, 2020): 0.1-second improvement on the mobile site → +10% conversions in retail, +8% in B2B services

For B2B services (lawyers, fiduciaries, architects), the impact is slightly lower than in e-commerce but remains significant: buying decisions take longer, but the first impression builds or destroys trust.

What a 1-second site does differently from a 5-second site

The difference between these two types of site is not a matter of more expensive hosting or more powerful servers. It is a matter of architecture.

Server-side rendering vs client-side rendering

A WordPress site (or Wix, or Squarespace) sends an almost empty HTML page to the browser, then loads JavaScript, which calls APIs, which render the components. This model (known as Client-Side Rendering, or CSR) is fundamentally slow on first load.

A Next.js site can generate pages directly on the server (Server-Side Rendering) or at build time (Static Generation). The browser receives complete HTML, ready to display. LCP is almost immediate because the main content is already in the HTTP response.

Image optimisation: lever number one

Images account on average for 50 to 70% of a web page's weight. The Next.js <Image> component automatically handles:

  • Conversion to WebP or AVIF
  • Adaptive resizing based on the visitor's screen size (responsive images via srcset)
  • Native lazy loading
  • Reserving space in the layout to prevent CLS
  • Loading priority for the main image (LCP boost)

A WordPress site without these optimisations serves the same 3000×2000 px, 8 MB JPEG to a smartphone that only needs a 400×267 px image. The difference in weight is 98%.

JavaScript code: the hidden debt of CMSs

Every WordPress plugin adds JavaScript. Every social widget, every booking button, every chat tool, every analytics script adds code that the browser has to download, parse and execute before the page becomes interactive. This cost builds up silently.

A Lighthouse audit on an average WordPress site generally detects 800 KB to 3 MB of unused JavaScript (code downloaded but not executed on the page). In Next.js, with tree-shaking (automatic removal of unused code) and code splitting (loading only the code needed for the page being displayed), the JavaScript bundle can be reduced by 70 to 90% compared with an equivalent WordPress site.

CDN and caching: geography matters

Switzerland is well served by international CDN networks (Cloudflare, Vercel, AWS CloudFront). A Next.js site deployed on Vercel is automatically distributed across a network of 100+ points of presence. A visitor in Geneva receives static resources from a server in Frankfurt or Paris, with 20-30 ms latency, rather than from a shared server somewhere in Germany serving 200 other sites at the same time.

Google ranking: Core Web Vitals as a competitive filter

Since the introduction of the Page Experience Update in 2021 and its gradual reinforcement, Core Web Vitals have been part of Google's ranking signals. They are not the dominant factor (content and backlinks remain the priority), but they are a tiebreaker.

Here is how this tiebreaker works in practice: if two pages have content of equivalent quality and similar domain authority, the page with better Core Web Vitals gets a ranking boost. In a market as competitive as Geneva (with one of the highest densities of lawyers, fiduciaries and consultancies in Switzerland), this tiebreaker comes into play regularly.

Google's thresholds in practical terms

Comparative data

MetricGoodNeeds improvementPoor
LCP< 2.5 s2.5-4 s> 4 s
INP< 200 ms200-500 ms> 500 ms
CLS< 0.10.1-0.25> 0.25

The vast majority of Geneva SME websites analysed fall into the "Poor" zone for mobile LCP. Moving into the "Good" zone is not just a matter of user comfort: it means earning Google's positive signal where your competitors are getting the negative one.

Measuring the performance of your current website

Before making any decision, measure. Here are the tools to use, in order:

Google PageSpeed Insights (pagespeed.web.dev): free and instant. Enter your URL to get your mobile and desktop scores, Core Web Vitals metrics and prioritised recommendations. It is the same tool Google uses for ranking: it is your reference point.

Google Search Console → Core Web Vitals report: for sites with traffic, Search Console shows real data from your visitors (not just a lab test). It is more reliable for understanding the real-world experience.

WebPageTest (webpagetest.org): for advanced analysis. It lets you test from specific locations (Frankfurt, Paris) and over simulated connections (4G, slow 3G), and gives you a detailed request waterfall to identify bottlenecks.

GTmetrix: a more accessible interface than WebPageTest, recommended for a first detailed audit.

How to read your score

A PageSpeed score below 50/100 on mobile is an active problem. It means your site is losing visitors, and potentially rankings, every day. A score between 50 and 75 is average: not disastrous, but not competitive. Above 90, you are in the top 10-15% of websites, a clearly advantageous position.

The real cost of slowness vs the cost of a fast website

The argument I hear most often: "My WordPress site works, why change?" Here is an answer in figures.

What a slow website costs (per year)

For an SME with 500 organic visitors/month, a 2% conversion rate and a client value of CHF 2,000:

  • Traffic actually converted with LCP > 5s: 500 × (1 - 0.55 bounce) × 2% = 4.5 prospects/month
  • With LCP < 2s: 500 × (1 - 0.32 bounce) × 2% = 6.8 prospects/month
  • Difference: 2.3 prospects/month × CHF 2,000 = CHF 4,600 in revenue lost every month

Over a year, that is CHF 55,000 going to faster competitors, not counting the impact on organic ranking.

The ROI of a fast, bespoke website

A bespoke website developed in Next.js with an architecture designed for performance is not cheaper than a quickly built WordPress site. But it is not a cost either: it is a commercial asset that works around the clock. The difference in ROI over 3 years between a site that converts properly and one that lets 60% of its visitors walk away makes the business case unambiguous.

The Geneva-based SMEs that have invested in a fast website (as I can see in PageSpeed data and ranking results) clearly stand out in their sectors: they appear higher in search results, their visitors see the content immediately, and their conversion rate is structurally higher than their competitors'.

The optimisations with the greatest impact: ranked by effort and result

Comparative data

OptimisationLCP impactEffortFeasible on a CMSNative in Next.js
Image optimisation (WebP + sizing)Very highLowPlugin required (variable results)Yes, automatic
Server-Side Rendering / Static GenerationVery highHighNo (different architecture)Yes, native
JS code splitting and lazy loadingHighMediumPartial (plugin)Yes, automatic
CDN with edge cachingHighLowVia the hostYes (Vercel/Cloudflare)
Removing render-blocking fontsMediumLowYes (theme modification)Yes, native (next/font)
Reducing plugins/third-party scriptsHighMediumYes (but limits functionality)N/A
Preconnect/PrefetchMediumLowPartialYes, full control
CSS/JS minificationLowNoneAutomaticAutomatic

The key column is the last one: most of the optimisations with a high impact on performance are either native to Next.js or hard to achieve reliably on a CMS. That is where the difference in architecture creates a structural advantage, not just a list of features.

What INFUSE does differently

Every website developed by INFUSE is built with performance as a non-negotiable constraint, not an option. In practice, this means:

Target: PageSpeed score > 95/100 on mobile and desktop across all main pages. This is not an aspirational goal: it is the delivery criterion.

Next.js App Router architecture with static generation or server-side rendering depending on the nature of each page. Pages that can be static are static: it is the fastest possible configuration. Dynamic pages (forms, personalised results) use RSC streaming so that the essential content is visible immediately.

Zero plugins, zero unnecessary dependencies: every library added is justified by a genuine functional need, and its impact on the JavaScript bundle is measured before integration.

Images optimised at source: format, dimensions, compression and priority attributes (priority on the LCP image, loading="lazy" on secondary images) are defined precisely by the developer, not left to an automatic heuristic.

Post-launch monitoring: Google Search Console access configured from launch to track how Core Web Vitals evolve under real-world conditions.

Speed is not a technical luxury reserved for large companies. It is a commercial advantage available to any Geneva-based SME that makes the right technology choice from the outset.

How many seconds does your current website take to load? Paste your URL into PageSpeed Insights: the result will be your best argument for the next conversation. INFUSE builds websites that pass this test with flying colours. Let's talk about your project.

What I deliver, never outsourced.

Request a quote