How building a website or app affects SEO, speed and conversions: a guide for business owners

Developing a website or an app is much more than a nice design. It's the technical foundation that determines whether your business shows up on Google, whether visitors stay and whether they end up leaving their contact details. A well-built website is an asset that generates inquiries around the clock, and a badly built one is a silent budget leak. This guide explains how development decisions affect SEO, speed and conversions, in plain business terms. It's for anyone considering a business website or app development who wants to understand what they're really paying for.

What website and app development is, and why it's not just design

Development is the process of planning, writing and building digital products: brochure sites, online stores, management systems, web apps and mobile apps. Unlike graphic design, development deals with what happens under the hood: the structure of the code, loading speed, security, accessibility and the ability of search engines to read and understand every page. Every technical decision at this stage affects business results for years to come.

In plain English: a good website isn't just about "how it looks," but about how fast it loads, how easy it is for Google to understand and how many visitors end up becoming customers.

Three ways code affects your Google rankings

Google doesn't rank pretty websites. It ranks pages that answer the search, and it understands them through the code it receives. When the code is bloated, the images are heavy and the structure is messy, the search engine struggles to understand the site and the user experience suffers, even if the content is excellent. There are three main mechanisms:

• Speed and Core Web Vitals: Google measures the loading experience of real visitors and uses it as one of its ranking signals.
• Readable code and crawling: semantic HTML, an orderly heading hierarchy, internal links and a valid sitemap help Google discover and understand every page.
• Mobile: Google crawls and ranks based on the mobile version of the site, so a website that isn't built properly for mobile loses out even if it is perfect on a desktop.

How Google reads a website built with JavaScript

Most modern websites are built with JavaScript libraries such as React. That makes fast, smooth interfaces possible, but it raises an important question: what does a crawler get when it lands on the page? The answer depends on the rendering method, meaning where and when the page's HTML is built.

Client-side rendering (CSR) is the default for a simple React app: the server sends an almost empty page and a JavaScript bundle, and the content is built only in the browser. Google can run JavaScript, but that's an extra step in its process, as described in Google's guide to SEO for JavaScript sites. More importantly, some crawlers don't run JavaScript at all, including many of the crawlers behind answer engines such as ChatGPT and Perplexity. To them, a page built only in the browser is an empty page.

The solution is to send the crawler full HTML on the very first request. There are several methods for this, and Next.js, for example, supports all of them:

Static site generation (SSG)

The pages are built once, at build time, and every visitor gets a ready-made HTML file immediately. This is the fastest method, and it suits service pages, landing pages and the blog, in other words, most of the pages on a business website.

Server-side rendering (SSR)

The page is built on the server for every request. This method suits information that changes all the time or differs from visitor to visitor, such as real-time inventory, search results or a personal account area. The trade-off is server load and a slightly longer response time than a static page.

Incremental static regeneration (ISR)

A combination of the two: the pages are static, but the server rebuilds certain pages in the background, at a set interval or when the content changes. That gives you the speed of a static page with up-to-date content, for example in a large product catalog.

Prerendering an existing site

Even an existing React app can generate a full HTML file in advance for every URL at build time. That is how the VeloLinx website is built too: React, with full HTML for every page from the very first load.

The differences between the methods are explained in depth in web.dev's article on rendering methods. In a good project you choose a method for each type of page, not one method for the whole site.

Core Web Vitals and site speed: the numbers Google counts

Core Web Vitals are three metrics Google uses to quantify the user experience of loading, responsiveness and stability. Each metric has a clear threshold for "good," "needs improvement" and "poor," and Google looks at the experience of 75 percent of your real visitors, not a single lab test. The full definitions are in the official explanation on web.dev:

• LCP (Largest Contentful Paint, loading of the main content): how long it takes for the largest element on the page to appear. The target: 2.5 seconds or less. More than 4 seconds is considered poor.
• INP (Interaction to Next Paint, response to interaction): how quickly the site responds to a click or a keystroke. The target: 200 milliseconds or less. INP replaced the old FID metric, and it measures every interaction on the page, not just the first one.
• CLS (Cumulative Layout Shift, visual stability): how much elements jump around while the page loads. The target: 0.1 or less. A stable site doesn't move a button out from under your finger or cause accidental taps.

A concrete example: an uncompressed 2 MB background image can, on its own, stretch LCP past 4 seconds on a cellular network, even if the rest of the page is excellent. A banner that loads late and pushes the content down can send CLS far past the threshold. These are exactly the problems that proper development prevents at the coding stage:

• Images: dimensions set in advance for every image, so the browser reserves space for it and doesn't make the page jump; newer formats such as WebP and AVIF; different sizes for mobile and desktop; and lazy loading only for the images below the fold. The Next.js image component, for example, handles most of this automatically.
• JavaScript: splitting the code so that each page loads only what it needs, and deferring external scripts that aren't needed for the first load.
• Fonts: a limited number of weights, preloading the main font, and showing text while the font is still loading.

The impact is twofold: a positive ranking signal and, above all, fewer visitors leaving and more inquiries. For a detailed explanation of measuring and improving them, see our guide to Core Web Vitals. Want to know where your website stands today? You can check your Core Web Vitals in PageSpeed Insights. A free SEO audit adds the server response time, the weight of the page's code and 14 more technical checks to the picture.

Custom code, WordPress or Wix: the decision in brief

This is the most significant decision in any website project. WordPress themes and website builders like Wix are cheap and quick to set up, but they come with extra weight: plugins, generic code and platform dependence. Custom code requires a higher investment up front and delivers a lean, fast website tailored precisely to your needs.

• Wix: suits a small business that needs a basic presence fast and on a low budget, and is willing to work within the limits of the platform.
• WordPress: suits a content site that's updated often and standard needs that an existing plugin already covers, as long as someone maintains it.
• Custom code: fits when the website is your main sales channel, when the competition on Google is real or when you need unique functionality.

We laid out all the considerations, including a comparison table, the cost over time and switching platforms without losing rankings, in our comparison of a custom-coded website, WordPress and Wix.

Architecture that grows with your business

A brochure site and a web-based system look similar from the outside, but inside they are different worlds. When the project includes a personal account area, orders, payments or an admin interface, the quality of the architecture determines how easy it will be to add things two years from now, and whether the system will hold up on the busiest day of the year.

• Separating the interface from the data: the presentation layer (the frontend, for example in React) talks to the data layer (the backend, for example in Node.js) through a defined API. That way you can change the design without touching the logic, and later connect a mobile app to the same data source.
• Modular code: each component is built as an independent unit with a single job. A new feature is added as a new component, without breaking what already works.
• Handling heavy load: static pages served from a content delivery network (CDN) withstand a spike in traffic, for example after a successful campaign, without straining the server. The dynamic parts are designed so they can grow when demand rises.
• Simple outside, complex inside: the user should see a clear, minimal interface. The complexity, such as calculations, permissions and connections to other systems, stays behind the scenes.
• Real ownership: when a system is developed for you, the code should be yours. Make sure the contract says so, that you have access to the code repository, and that the hosting and domain accounts are registered to the business.

Mobile-first and responsive: most of your visitors are on mobile

In most industries, most visitors reach your website on their phones. Responsive means the website adapts to every screen size, from a phone to a wide monitor, and Google crawls and ranks based on the mobile version. A website that isn't built properly for mobile loses out on both rankings and conversions.

Real mobile-first development includes buttons and tap targets of at least 48 by 48 pixels, text that is readable without zooming, images that load fast even on a cellular network, and short forms that are easy to fill out on a small screen, with the right keyboard for each field: a number pad for the phone number and an email keyboard for the address. All of these directly affect how many people leave their contact details.

Security and stability

Professional development also takes care of what you can't see. Good security protects customer data and prevents breaches that can take the site down and damage your reputation. In practice that means an SSL certificate and encrypted communication (HTTPS), regular security updates for libraries, automatic backups that allow fast recovery, and protection of forms and APIs against spam, hacking attempts and request floods.

A theme-based website with dozens of plugins that aren't updated is an easy target for attackers. A website built on lean code, and especially one served as static HTML with no exposed admin panel, greatly reduces the attack surface. It needs maintenance too, but on a much smaller scale.

A website, a web app or a mobile app

Not every business needs an app, but there are situations where it goes from an asset to a necessity. A website is excellent for presence, brand image, inquiries and sales, and it is what brings in new customers from Google. An app fits when you need deep interaction and repeat use:

• Daily, repeat use: when customers come back again and again, an icon on the home screen and notifications strengthen the relationship.
• Complex functionality: booking systems, user management, payments or rich business logic.
• Device capabilities: the camera, location, push notifications and working even without an internet connection.
• A premium experience: when the speed and smoothness of an app are part of the brand.

In between there is the web app: a system that runs in the browser with no app store, such as a customer area, a dashboard or a booking system. Add home screen installation and notifications, and it becomes a PWA. For the full comparison, see web apps and PWAs vs. mobile apps, and for the question of whether your business needs an app at all, see the seven questions that will help you decide.

In many cases the right solution is a combination: a strong website that brings in customers from Google, alongside an app or a web-based system for managing the ongoing relationship, with both running on the same backend.

How much does a website or an app cost to build?

There is no single price, just as there is no single price for a car. But you can understand what determines it, so you know what you are paying for:

• The number of pages and screens: a five-page brochure site is fundamentally different from a system with dozens of screens and user management.
• A theme vs. custom code: a theme is cheap at first and more expensive to maintain. Custom code requires a higher initial investment and pays it back in speed, security and flexibility.
• Special functionality: payments, a personal account area, bookings or connections to external systems add development hours.
• Unique design: custom branding and design cost more than a theme, and they are what set you apart from your competitors.
• SEO foundation and content: a website built ready for SEO saves you from doing the work twice and from expensive fixes later on.

The common mistake is to look only at the starting price. A cheap website that has to be rebuilt in a year, or that brings no inquiries, is the truly expensive one. The right way to think is cost versus return: how many inquiries the website is expected to bring and what a new customer is worth. For price ranges and the questions worth asking a provider, see our guide to website and app development pricing and our guide to app development costs.

The stages of developing a website or an app

A well-organized project goes through five clear stages:

1. Scoping: understanding the business, the audience, the competitors and the goals, choosing the right technology and defining how success will be measured. For apps, a well-organized specification document saves many hours of development.
2. Design: structure, user experience and visual design aimed at conversions, not just aesthetics.
3. Development: modular, documented code, with the right rendering method for each type of page, an SEO foundation and full mobile support.
4. Launch: quality, speed and security testing, an accessibility check against the requirements of the law in Israel and setting up measurement tools, and only then going live.
5. Maintenance: updates, performance monitoring and ongoing improvements that keep the website fast and secure.

Common development mistakes that cost you money

The same mistakes come up again and again, and they usually cost the business far more than it saved at the start:

• Choosing a provider on price alone: a cheap, badly built website turns out to be the most expensive one, because it has to be rebuilt or it simply doesn't bring in customers.
• Neglecting speed: heavy images that weren't compressed, unnecessary fonts and plugins that slow everything down. All of these hurt Core Web Vitals and drive up bounce rates.
• Building without thinking about SEO: a website that went live without the right structure, without orderly headings and without a sitemap starts its SEO life at a disadvantage, and sometimes it has to be rebuilt.
• Building a React site that renders only in the browser: without server-side rendering or prerendering, many crawlers see an empty page, and all your content work goes unread.
• Ignoring mobile: a website that looks perfect on a desktop but is broken on a phone loses most of its visitors.
• Forgetting a clear call to action: a beautiful website with no prominent contact button and no conversion path is a brochure, not a lead machine.
• Not securing ownership: code, hosting and a domain registered in the provider's name turn every switch to a new provider into a negotiation.
• Skipping maintenance: a website is not a project that ends at launch. Without updates, monitoring and backups it becomes outdated, exposed to vulnerabilities and gradually loses rankings.

Every one of these mistakes can be prevented in advance, if you build properly from the start, with a provider who thinks about marketing too, not just about code.

How we build websites and apps at VeloLinx

VeloWeb, VeloLinx's development team, builds websites, web and mobile apps and management systems in custom code, mainly in React, Next.js and Node.js. Every website comes with full HTML for crawlers, Schema markup, a planned heading and URL structure and a content management system for day-to-day editing.

The advantage is that the same team that builds also does the SEO. The structure of the pages and the internal links is planned for SEO in advance, and once the foundation is ready, organic SEO packages and buying backlinks plug straight into it, with nothing to fix after the fact.

Frequently asked questions

How long does it take to build a professional website?

A custom-coded brochure site usually takes anywhere from a few weeks to two months, depending on the complexity, the number of pages and the scope of functionality. A complex system or app takes longer. The stage that most affects the timeline is scoping: the more precise it is, the faster and smoother the development.

How much does it cost to build a website?

There is no single price, because the cost depends on the number of pages, the functionality required, the choice between a theme and custom code and the level of design and content. The right way to estimate cost is by return: how many inquiries the website is expected to bring and what a customer is worth. A detailed quote that shows exactly what is included lets you compare providers on a real basis.

Does a React website hurt SEO?

No, provided it serves full HTML to crawlers. A React site that builds its content only in the browser relies on Google running the JavaScript, and the crawlers of many answer engines don't do that at all. With static generation, server-side rendering or prerendering, a React site reads like any HTML site and even tends to be faster.

Custom code or WordPress: which is better for my business?

It depends on the website's role. A business whose website is its main sales channel, that competes for competitive keywords or that needs unique functionality will benefit from custom code, thanks to the speed, the security and full control. A content site with a team that updates it in house, or a small business with basic needs, can do perfectly well with a well-maintained WordPress site.

Does site speed really affect Google rankings?

Yes, but it isn't the only factor. Core Web Vitals are part of the page experience signals Google uses, and relevant content still carries more weight. The big impact of speed is on behavior: fewer visitors leave before the page loads, and more of them leave their contact details.

Do I need an app, or is a website enough?

For most businesses, a fast website that is ready for SEO is the first and most important step, because it brings in new customers from Google. An app becomes relevant when there is repeat, daily use, complex functionality or a need for device capabilities such as notifications and location. In many cases a web app or a PWA delivers most of the benefits at a lower cost.

Who owns the code for a website or app built for me?

It depends on the contract, so it's important to check it before you start. In a custom project, the code should be the property of the business, with full access to the code repository and with hosting and domain accounts registered in your name. That way you can keep developing with any provider and not depend on one.

What to do next

Before you ask for quotes, define what the website or app needs to achieve: how many inquiries, from which channels, and which actions users need to take. With those answers it's easy to compare providers and choose a technology. For details on how we work, see our pages on business websites and app development, or message us on WhatsApp: 050-741-8449.