Update, October 2026: Web Gerek is now a QR menu platform only; the website builder this post originally described is no longer offered. I've updated the features and pricing below to match the product today. The infrastructure hasn't changed.
When a customer scans a QR code at a restaurant table, they expect the menu to appear instantly. When someone finds your cafe on Google and taps through to the menu, they won't wait three seconds for the page to load. Speed isn't a technical luxury — it's the difference between a customer staying or leaving.
That's why I built Web Gerek on top of Cloudflare's infrastructure from day one. Not because it sounded impressive on a features page, but because I saw firsthand — through years of freelance web development in Istanbul — how much a slow page costs a small business. This post is about the technical decisions behind Web Gerek's speed, what your guests actually experience compared to a menu on a Wix or WordPress site, and what the platform handles automatically so you never have to think about it.
Why I Chose Cloudflare as the Foundation
When I started building Web Gerek, I had a clear requirement: pages created on the platform had to load fast in Turkey. Not "fast enough" — genuinely fast. A restaurant menu in Antalya, a cafe in Ankara, a bar in Istanbul — they all had to feel instant regardless of where the visitor was.
Most website builders host your site on a single server somewhere in the US or Europe. When a visitor in Turkey requests that page, the data has to travel thousands of kilometers, bounce through multiple network hops, and arrive with noticeable delay. That's the fundamental problem with centralized hosting.
Cloudflare operates a global edge network with data centers in over 300 cities, including Istanbul and Ankara. When someone opens a Web Gerek menu, it's served from the nearest Cloudflare data center — not from a server on the other side of the world. This is the single biggest reason Web Gerek menus load faster than pages on Wix or WordPress for visitors in Turkey.
Here's how I use different parts of Cloudflare's infrastructure:
Cloudflare R2 stores all static assets — dish photos, images and menu design assets. R2 serves these files from the edge, meaning a restaurant's food photos load from a server physically close to the customer scanning the QR code. There's no round-trip to a US-based S3 bucket.
Cloudflare Workers handle edge computing tasks. Routing logic and certain API operations run at the edge instead of on a central server. This shaves off latency that users on other platforms never even realize they're experiencing.
Cloudflare for SaaS powered custom domains back when Web Gerek was a website builder, including one-click DNS setup through the Domain Connect protocol; we were accepted into the official Domain Connect repository for it. Custom domains aren't offered on new plans: every menu now publishes on a webgerek.com subdomain with SSL handled automatically.
Edge caching ensures that repeat visitors and subsequent page loads are nearly instantaneous. Once a page is cached at the edge, it's served without touching the origin server at all.
The result: Web Gerek menus consistently load in under a second for visitors in Turkey. That's not a marketing claim — it's a direct consequence of the architecture.
The Wix and WordPress Speed Problem
I don't want to turn this into an attack on Wix or WordPress. They're massive platforms that serve millions of users. But when it comes to speed — especially for small business pages in Turkey — they have structural problems that aren't going away.
Wix generates heavy JavaScript bundles. Every Wix site ships with a large runtime that powers their drag-and-drop editor capabilities, animations, and platform features. Even if all you need is a one-page menu, the browser still downloads and processes all that JavaScript. The result is a first contentful paint that's often 2-4 seconds on mobile. For a guest holding their phone over a QR code, that's an eternity.
Wix also controls your hosting entirely. You can't choose where your site is served from, you can't optimize caching rules, and you can't strip out the JavaScript you don't need. You're locked into their infrastructure decisions.
WordPress has a different problem. The platform itself is lightweight, but nobody runs vanilla WordPress. A typical small business WordPress site has 10-20 plugins: SEO plugin, caching plugin, security plugin, contact form plugin, gallery plugin, backup plugin. Each one adds database queries, CSS files, and JavaScript. A site that should load in 500 milliseconds ends up taking 3-5 seconds because the server is processing 20 plugins before it can even send the HTML.
Then there's hosting. Most small businesses put their WordPress site on cheap shared hosting — a $5/month plan where their site shares a server with hundreds of others. During peak hours, response times spike. And since most shared hosting providers have servers in the US or Western Europe, every request from Turkey adds 100-200ms of network latency on top of the slow server response.
WordPress also requires constant maintenance. Plugin updates, PHP version upgrades, security patches, database optimization — if you don't do these regularly, your site gets slower over time. A restaurant owner shouldn't need to worry about updating PHP to keep their menu page fast.
With Web Gerek, none of this exists. There are no plugins to manage, no hosting to choose, no JavaScript bundles to bloat your page. The platform generates clean, optimized HTML served from the edge. That's it.
What Web Gerek Handles Automatically
Here's something I'm particularly proud of as a developer: Web Gerek handles the technical SEO and web standards work that would normally require either a developer or multiple plugins. And it does it invisibly — the restaurant owner never sees any of it.
Structured data (Schema markup) is generated automatically for every menu. Each one is published with Restaurant and Menu schema, so Google can read your sections, dishes and prices directly. On WordPress, you'd need a dedicated plugin like Yoast or Rank Math to set this up manually. On Wix, the schema support is limited and often incomplete.
Sitemaps are generated automatically and updated every time you publish changes, and new menus are submitted through IndexNow so search engines pick them up quickly. You don't do anything.
AI search is covered too. Every menu ships with an llms.txt file, so AI assistants can read what you serve instead of guessing.
Multiple languages live on the same menu: up to 4, chosen from 14, with one-click AI translation on paid plans. A restaurant in Sultanahmet can serve Turkish, English, German and Russian from a single QR code.
SSL certificates are provisioned and renewed automatically through Cloudflare. Every Web Gerek menu runs on HTTPS with zero configuration. WordPress users on shared hosting often struggle with SSL setup, and expired certificates are a common problem.
Responsive design is built into every one of the 13 menu designs. They're designed mobile-first, which is the whole point: nobody scans a QR code with a laptop.
All of this happens in the background. A restaurant owner in Sultanahmet just types in their menu items and hits publish. They don't know what schema markup is, and they don't need to.
What Happens When a Guest Scans
When a guest scans your QR code, what actually happens behind the scenes is worth explaining.
The menu is rendered as server-side HTML — not a JavaScript application that needs to boot up in the browser. This means search engines see your full menu immediately, and guests see a complete page without waiting for scripts to execute. It's the same approach used by major news sites and high-performance web applications.
Compare this to Wix, where the page is essentially a JavaScript application. The browser downloads a large bundle, parses it, executes it, and then renders the content. On slow mobile connections — which are common in Turkey — this process can take several seconds.
This matters most for menus. When a customer scans a QR code, they're on their phone, probably on a cellular connection, and they want to see the menu right now. Web Gerek menus load from Cloudflare's edge with all images served from R2. The customer sees the menu in under a second. I've tested this extensively across different networks and devices in Istanbul — the experience is consistently fast.
The Features That Come With Speed
Speed is the foundation, but it's not the whole story. Web Gerek is built for restaurants, cafes and bars in Turkey, which means every feature is designed around the menu.
13 menu designs for different kinds of venues: neon for cocktail bars, İznik tiles for kebab houses and dessert shops, a coffee-cup design for cafes, classic and luxury for restaurants.
Instant updates. Change a price and it's live in 30 seconds — no reprinting, and the QR code on the table stays the same.
Calorie, ingredient and allergen fields, with 16 allergens per dish, included in the free plan. Turkey's Şeffaf Menü rules are phasing in ingredient, allergen and calorie information on restaurant and cafe menus from 1 July 2026.
Menu analytics on paid plans: total and daily scans, broken down by hour and by day of the week.
No per-table fees. Ten tables or sixty, you print the same QR code as many times as you like.
All of this at pricing that makes sense for the Turkish market. The free plan includes one published menu with no time limit. Pro is $6.99/month for 2 menus, Pro+ is $12.99/month for 10, and Agency is $39.99/month for 50. Compare that to reprinting a paper menu every time prices change, or to the combined cost of WordPress hosting, a domain and premium plugins just to keep a menu page online.
The Bottom Line
I built Web Gerek because I watched local businesses struggle with platforms that weren't designed for them. Wix is too heavy for a page that has to open in a second on a phone. WordPress requires too much technical knowledge and maintenance. Neither is optimized for speed in Turkey.
Web Gerek sits on Cloudflare's edge network, generates clean server-rendered HTML, handles the technical SEO automatically, and gives restaurant owners an editor that speaks their language — literally and figuratively. The menus are fast because the infrastructure is fast. The SEO works because it's built in, not bolted on. And the experience is simple because complexity is the developer's job, not the customer's.
If you run a restaurant, cafe or bar in Turkey, I'd encourage you to try Web Gerek with a free menu and see the speed difference for yourself. Your guests will notice it, even if they can't explain why.
