← Blog
PerformanceJan. 2026· 13 min read

Website loading speed: beat your Geneva competitors

A slow website loses clients and rankings. Loading speed of Geneva SME sites (lawyers, architects, restaurants, fiduciaries) and its impact on conversion.

There is one statistic every Geneva-based SME should know before launching or redesigning its website: according to Google, when loading time goes from 1 to 3 seconds, the probability of a mobile visitor leaving the page increases by 32%. From 1 to 5 seconds, it increases by 90%. These figures come from Think with Google's study "The Need for Mobile Speed", not from an agency selling performance work.

In Geneva, where many 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 commercial cost.

Recurring problems, sector by sector

To see where your own site stands, 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. Here are the problems that come up most often in four sectors: lawyers, architects, restaurants and fiduciaries.

The metrics to check 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.

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

The consequence: a prospect urgently looking for a lawyer (breach of contract, a dispute, child custody) leaves a slow site and goes to a competitor. The reputation the firm has 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. Yet that weight comes mostly from poor practices, far more than from any real technical constraint.

The WebP format, natively supported by all modern browsers, reduces image weight by 25 to 34% compared with JPEG at comparable visual quality, according to Google's official WebP documentation. 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) makes the first load of a portfolio page much lighter. An architect's website with 30 projects only loads the images visible on screen at first, with no loss of visual quality.

Restaurants: when hunger cannot wait

Restaurants show very clearly what slowness costs in hard cash. A prospect looking for a restaurant for tonight has an immediate purchase intent. Their tolerance for waiting is very low.

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 tries to tap a dish and hits something else. They get annoyed and leave.

PDF menus are another specific problem: they are poorly 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.

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 dated website says exactly the opposite.

Fiduciary websites are often less visually heavy, but still fall well short of the standards. A missing or expired HTTPS certificate is a real problem: Chrome displays a "Not secure" warning that drives prospects away.

The measurable impact on conversion and revenue

These problems have a cost. 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 fictional example: 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 enquiries per month. With 40% of enquiries becoming clients, that makes 9.6 new clients per month, i.e. CHF 33,600 in annual revenue brought in by the clients signed each month (9.6 × 3,500).

After optimisation (LCP: 1.4 seconds): the example assumes +30% conversion rate, i.e. 3.9%. 800 × 3.9% = 31.2 enquiries, and 12.5 new clients per month, i.e. CHF 43,680.

The difference is about 2.9 more clients each month, i.e. CHF 10,080 in additional annual revenue for each month of enquiries. Better speed also improves Google ranking, which generates more organic traffic and amplifies the effect.

Published case studies

These projections point in the same direction as published cases:

  • AutoAnything: load time cut in half → +13% sales
  • Walmart: every second of loading time saved → +2% conversions
  • Deloitte ("Milliseconds Make Millions" study, 2020): 0.1-second improvement on the mobile site → +8% conversions in retail

For B2B services (lawyers, fiduciaries, architects), the effect is probably less direct than in e-commerce, but it is real: buying decisions take longer, and the first impression builds or destroys trust.

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

What separates these two sites is architecture, not the price of hosting or the power of the servers.

Building the page on every visit, or in advance

A WordPress site rebuilds each page on the server, in PHP, on every visit: it queries the database, assembles the theme and plugins, then sends the result. Without well-tuned caching, this step slows down display, and the scripts added by the theme and plugins then weigh on the browser.

A Next.js site can prepare its pages in advance, when it goes live (static generation), and serve them from servers close to the visitor. The browser receives a complete page, ready to display, with no wait while it is assembled.

Image optimisation: the first job

Images are often the heaviest resource on a web page. 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 a WordPress site generally detects a large amount of unused JavaScript (code downloaded but not executed on the page). In Next.js, tree-shaking (automatic removal of unused code) and code splitting (loading only the code needed for the page being displayed) clearly reduce the JavaScript sent to the browser.

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 global network of points of presence. A visitor in Geneva receives static resources from a nearby server, rather than from a shared server somewhere in Germany serving dozens of 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, this tiebreaker often comes into play.

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

If your site is in the "Poor" zone for mobile LCP, moving into the "Good" zone makes it more comfortable for visitors and also earns you Google's positive signal, where slower competitors get 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 relies on the same metrics Google uses for ranking, so 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 not disastrous, but not competitive. Above 90, you are in 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, a client value of CHF 2,000, and bounce rates of 55% (slow site) and 32% (fast site), both assumptions for this example:

  • With LCP > 5s: 500 × (1 - 0.55 bounce) × 2% = 4.5 enquiries/month
  • With LCP < 2s: 500 × (1 - 0.32 bounce) × 2% = 6.8 enquiries/month
  • Difference: 2.3 more enquiries per month. If one in three becomes a client (assumption), that is about 0.8 more clients per month, i.e. about CHF 1,500 in revenue per month and CHF 18,400 per year.

The ROI of a fast, bespoke website

A bespoke website developed in Next.js with an architecture designed for performance costs more than a quickly built WordPress site. It should still be seen as a commercial asset that works around the clock. Over 3 years, the ROI gap between a site that converts properly and one that lets a large share of its visitors walk away speaks for itself.

The Geneva-based SMEs that have invested in a fast website stand out in their sectors: they appear higher in search results, their visitors see the content immediately, and they lose fewer prospects along the way.

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

Look mainly at the last column: most high-impact optimisations are native in Next.js and hard to achieve reliably on a CMS. The advantage comes from the architecture itself, not from a list of add-on features.

What INFUSE does differently

On every INFUSE website, performance is a requirement set from day one. In practice:

Target: PageSpeed score > 95/100 on mobile and desktop across all main pages. This is our 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 reserved for large companies. Any Geneva-based SME can turn it into a commercial advantage by choosing the right technology from the outset.

Frequently asked questions

What loading time should I aim for?

Google's "Good" threshold for LCP is under 2.5 seconds, with INP under 200 ms and CLS under 0.1. An LCP over 4 seconds is rated "Poor".

How do I measure my website's speed?

Start with Google PageSpeed Insights (pagespeed.web.dev), which is free and instant. The Core Web Vitals report in Google Search Console then shows real data from your visitors, and WebPageTest or GTmetrix allow a more detailed analysis.

Why are WordPress sites often slow?

The same causes keep coming up: unoptimised images, many active plugins, render-blocking fonts and a lot of unused JavaScript.

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.

One point of contact, from design to code.

Request a quote