WordPress or Custom Code: What Is Right for a Small Business and Why It Matters on the Beach in Eilat
WordPress is right for a small business that needs a brochure site of a few pages and wants to edit text and photos on its own. A coded website is right for a business whose website is a working tool. A tourist coming in from a phone on the beach. Booking and payment. Several languages. A season when nobody is around to fix a broken plugin. Both paths are legitimate. The difference is not the technology. It is what the site needs to do and who maintains it.
What a coded website is, in plain words
A coded website is a site a developer writes from scratch in a programming language, instead of assembling it from a ready made template and plugins. WordPress is a content management system. You install it on a server. Pick a design template. Add plugins for forms, galleries and SEO. Then you log into an admin panel and write. This is the model almost every business owner has already met. It is cheap to set up and lets the owner edit alone, and that is a real advantage.
A coded website works differently. We write the pages and the components ourselves and build only what the site needs. Next.js is a framework for building websites in code that prepares the pages ahead of time, so the visitor gets a ready page instead of waiting for a server to assemble it on every visit. There is no public admin panel. No third party plugins. There is code that belongs to you and runs on simple hosting.
A coded website does not mean you cannot edit. When a price menu or blog posts need regular updates, we connect a headless CMS, a detached content management system, and define exactly which parts can be edited. The difference is that you decide up front what changes and what stays fixed, instead of every corner of the site being open. That is really the question of code versus template. Who decides what can be touched.
Comparing WordPress and a coded website
On every point in the table one side has a clear advantage and the other side pays a price. There is no overall winner here. There is a fit for the business. We build both ways, and our website building page details what each track includes.
Two points worth getting precise. The speed of a WordPress site does not come from WordPress itself but from what you dress it with. A heavy template, a page builder and a lot of plugins will slow any site down. And a coded site is not immune. Photos weighing several megabytes will slow it down too. The difference is that in code the default is fast, and in WordPress you have to work to get there.
With cost the picture is reversed. Setting up a coded site usually costs more because it is written specifically for you. In the years after, WordPress accumulates template and plugin licenses and hours of updates, while a coded site sits on cheap hosting with almost no routine care. We wrote about the numbers themselves and what each level includes in how much a website costs for a business in Eilat.
| WordPress | Coded website | |
|---|---|---|
| Speed | Depends on the template, the plugins and the hosting. A lean site can be fast. A site with a page builder and many plugins is heavy | Fast by default because the pages are prepared ahead of time and only what is on the page gets loaded. Heavy photos will slow it down too |
| Security | The most common system in the world, so the most common target for break in attempts. Most problems we have seen came from outdated plugins | Small attack surface. No public login screen and no third party plugins |
| Maintenance | Core, template and plugin updates every few weeks, plus someone checking nothing broke | Almost no routine maintenance. Version updates once in a while by whoever built it |
| Self editing | The big advantage. Text, photos, pages and posts on your own from the admin panel | Only what was defined up front as editable through a connected content system. The rest goes through a developer |
| Cost | Cheaper to set up. Over the years licenses, hosting and maintenance hours add up | More expensive to set up. Cheap hosting and no licenses. A big change needs a developer |
| When it fits | A brochure site, a blog and a content site the owner updates on their own | A site that is a working tool. Bookings, payment, languages and mobile speed |
What really decides speed for a tourist on 4G at the beach
The speed the tourist feels comes down to four things. The weight of the photos. The fonts. How much code loads before anything shows on screen. And the distance from the server. WordPress or code is only the question of who controls those four things.
Google measures this experience through Core Web Vitals, its browsing experience metrics. The main one is Largest Contentful Paint, the load time of the biggest element on the page, and by Google's definition it should stay under 2.5 seconds on mobile. There is also a metric for the page jumping around while it loads, called Cumulative Layout Shift. Google says these metrics count in ranking, but not ahead of content that answers the search.
Photos of blue sea are the most common problem we see on websites in Eilat. A photo comes out of the camera weighing several megabytes and gets pushed to the homepage with no compression. On a coded site the photos are converted automatically to a light format like WebP and load at the size that fits the screen they are viewed on. In WordPress you can reach the same result with a plugin and compressing up front. Someone just has to do it.
The fourth thing is the route the page travels. A page builder like Elementor adds a layer of its own styles and scripts on top of the template. Newer versions improved, but the layer is still there and every extra plugin adds more files. A coded site loads only what is on the page. Distance matters too. A server in Europe or the United States adds time to every request. Hosting nearby, or a CDN, a content delivery network with a point in Israel, shortens the trip. A fair measurement runs both sites under the same conditions and from the same device. You can run it yourself in Google's PageSpeed Insights on your site and on a competitor's site.
Hebrew fonts and RTL
A Hebrew font loaded from the network is one of the first things that slows a Hebrew site, and no English guide will tell you about it. Heebo. Assistant. Rubik. All good fonts, usually loaded from Google's servers. The browser requests the font, and until it arrives it either hides the text or shows a temporary font and swaps it later. Both states are bad. Hiding delays the load moment of the headline, which is usually the biggest element on the page. Swapping shifts the whole page and spikes the stability metric.
The fix is the same in both technologies. Host the font file on the site itself instead of pulling it from Google. Load only the weights actually in use. Trim the file down to the Hebrew and Latin characters only. And set a fallback font with a similar width so the swap does not move anything. In Next.js this is built in. In WordPress it is possible but takes manual work or a plugin, plus checking that the template does not keep loading the font from Google anyway.
Hebrew running right to left, RTL, is the second story. Most templates and plugins are written for English and then get direction fixes layered on top. The result is more style files. Icons pointing the wrong way. Lines of numbers and English breaking inside a Hebrew sentence. A site written in code for Hebrew from day one simply does not suffer from this. In WordPress you pick a template with real RTL support and check every component after every update.
When WordPress is right
WordPress is right when the content changes a lot and the person changing it is you. A restaurant that updates its menu every season. A therapist with a blog who writes a post a week. An office with twenty service pages that wants to add one more without waiting for anyone. In all these cases the ability to open an admin panel and change things is worth more than any speed gain.
There are more advantages that are hard to argue with. A lower setup budget. Freedom to move between providers, because almost everyone who builds websites knows the system. And a huge plugin library for almost any need. Forms. An appointment calendar. Translation. A small shop with WooCommerce. When the need is standard, the standard route is the cheapest and fastest to set up.
WordPress can also be fast. A lean template. Few plugins. Good hosting. A cache layer, meaning ready copies of pages kept in memory. And someone going over the updates once a month. We have built sites this way and we maintain WordPress sites to this day. The only condition is that someone maintains it. A WordPress site with no owner is the problem. Not WordPress.
When code is right
Code is right when the site needs to do something a template was not built to do, or when speed and reliability are part of the product itself. The clearest example from our own work is a water sports beach in Eilat we work with. There the website is not a business card. It takes bookings from the phone of a tourist standing on the sand. The front desk and the online bookings work off the same open spots. A cancellation because of wind has to move through the whole system at once. You do not build that from plugins.
The same logic works for a park that manages entries. For vacation villas that need a booking and cleaning system. For a restaurant that wants the menu and the table booking to work in Hebrew, English and Russian without a template breaking. And for any business that connects its website to payment processing, to WhatsApp and to its Google Business Profile. When systems connect to each other, it is better that the code is yours. Examples of systems like these that we built are in our portfolio.
And there is the season factor. In August it is hard to find anyone in Eilat free to deal with a plugin that stopped working. A well built coded site just sits quietly. Nothing to update every two weeks. No login screen someone is trying to guess. This is also the part we explain on our apps and systems development page.
What to do if you stay on WordPress
If you decided to stay on WordPress, here is a short list that separates a working site from a site that gets hacked in the middle of the season. Nothing here needs a developer. It needs someone to be responsible.
- Updates: core, template and plugins at least once a month, and a quick check of the main pages after every update
- Backup: an automatic daily backup to somewhere that is not the same server, and a check every so often that you can actually restore from it
- Plugins: delete every plugin not in use. A deactivated plugin is still code sitting on the server
- Login: two factor authentication for the admin panel and changing the login address from the default
- Speed: compress photos before uploading, a cache layer and a locally hosted font as we described above
- Monitoring: an automatic alert when the site goes down, so you do not find out from a customer
How to move from WordPress to code without losing your rankings
The move does not hurt your rankings if every old address keeps leading to the right place. Google ranks pages, not technologies. What matters to it is that the address it knows returns the same content or points with a permanent 301 redirect to the new address. Everything else is work order.
If the new site is faster and built right for Hebrew, the SEO gain comes after the move and is not hurt by it. What does sometimes happen is small fluctuations in the first weeks while Google recrawls. That is normal when the redirects are in place. How to continue from there to local SEO, we wrote in the promoting a business in Eilat guide.
- Map every existing address from the sitemap and from Search Console, including images and old pages you forgot about
- Keep the same addresses on the new site. Where you cannot, prepare a table of permanent redirects from every old address to the new one
- Move titles, descriptions and H1 headings as they are. Improve content only after the move has settled
- Keep the alt text on images and the LocalBusiness schema on the new site
- Submit a new sitemap in Search Console and watch the 404 errors and the coverage report for a few weeks
- Update the link in your Google Business Profile and in every local directory if the domain changed
- Do not go live during Passover week or in August. Pick a slow period, so if something moves it moves on little traffic
Sources and verification
Every figure in this article was checked against two independent sources before publication. The numbers are quoted as originally published and their date appears next to them. Anything we could not verify twice is not written here as fact.
- WordPress.org. Official documentation and security updates
- Next.js. Official documentation
- Google. web.dev and the Core Web Vitals metrics
This is exactly what we do at Website building. If you want us to go over it together for your business, write to us.
Frequently asked questions
To set up, usually yes, because it is written specifically for you. Over the years the picture evens out. No plugin licenses, no update hours, and the hosting is cheap. A business planning to keep the site for several years should compare total cost, not just the price of day one.
Yes, if you define it up front. We connect a content management system to the parts that change, like a price menu or blog posts, and leave the rest fixed. Anything not defined as editable goes through whoever built the site. So it is worth deciding at the start of the project what you actually want to touch.
If every old address is kept or points with a permanent redirect to the new one, the rankings move with you. Small fluctuations in the first weeks are normal. A faster site built right for Hebrew usually improves once the dust settles.
No. Neglected WordPress is dangerous. A site with an updated core and plugins, an external backup and two factor authentication at login is a fine site. The risk comes when nobody has logged into the admin panel for months and an old plugin stays open.
Wix is a reasonable option for a business that wants to go live alone and fast. The price is less control over speed, over hosting and over how Hebrew behaves. And you cannot take the site and move it to another provider. If the site is a business card, that is fine. If it is a working tool, you will feel the limit.
Elementor is a page builder for WordPress that lets you design by dragging. That convenience comes with an extra layer of code and styles on top of the template. Recent versions improved, and a tidy Elementor site can run reasonably. The problem starts when you stack more design plugins and heavy photos on top of it.
Want us to look at this for your business?
Just write to us on WhatsApp. The first conversation comes with no commitment. 050-294-0127
Write to us on WhatsApp