Website Architecture and Performance

Overview

There are no settings for you to toggle in this article. Its purpose is to give you a clear understanding of how the system works under the hood to deliver your Kanorio website to visitors and search engines quickly and completely.

Traditional website building (e.g., WordPress) often requires you to rent a server, configure caching, and install image compression plugins—where too many plugins can slow each other down. Other modern website builders may only deliver a blank shell, forcing the visitor's mobile device to run a heavy script before any text appears. Kanorio solves both of these issues from the ground up.

1. What Search Engines and Visitors Receive: Server-Side Rendering

When a visitor clicks a link, or when search and AI bots like Google, Bing, ChatGPT, or Perplexity connect to your URL, the Kanorio server responds with a fully rendered, formatted webpage:

• Headings and content are in the first response: The page's main heading (H1), subheadings (H2, H3), and all module content are present the moment the page arrives. There is no need to wait for the browser to execute JavaScript to assemble the page.
• Automatically aligned breadcrumbs and structured data: Visible path navigation (e.g., Home › Shop › Product Name or Home › Blog › Category › Article) and machine-readable Schema.org structured data (including business info, FAQs, product pricing, article, and breadcrumb markup) are all sent in the initial response.
• What is the benefit for you?
  1. No blank screens for visitors: Mobile users see the layout and text immediately upon clicking the link, without staring at a loading spinner.
  2. Search engines and AI bots understand instantly: Many crawlers do not wait for browser scripts to execute. Server-side rendering ensures that all search engines and AI tools read 100% of your content.

2. Where Your Website Lives: Cloudflare Global Edge Network and Intelligent Caching

Your public website is not hosted on a single remote server; it is deployed across the Cloudflare Global Edge Network:

• Direct response from the nearest node: Edge nodes are located worldwide, acting like local branches in different cities. Whether a visitor is in Taipei, Tokyo, or New York, the cached page is delivered from the node closest to them, eliminating the need to travel back to the main server for every request.
• Seamless updates without disrupting visitors:
  • When you click "Publish" or update SEO settings, the system immediately notifies edge nodes to swap in the new version.
  • Even during the few seconds it takes to prepare the page in the background, the system ensures visitors see the page without delay. The update happens in the background and switches seamlessly; visitors will never encounter a frozen screen or error page because you just hit publish.
• Independent updates for blog posts and products: When you publish a new blog post or update a product, the system precisely updates the cache for that specific item and its related lists, without affecting the cache efficiency of other pages.
• Instant access to the latest version for site owners: When you click "View Website" from the dashboard, the system automatically applies a preview pass, bypassing the cache to show the latest state so you can verify changes immediately.

3. Automatic Optimization for Images and Fonts

High-resolution images and web fonts are usually the two main culprits that slow down mobile websites. Kanorio has a fully automated acceleration pipeline for them:

Automatic image resizing (No need to manually crop multiple versions)

• Large images for desktops, small images for mobile: You only need to upload one clear original image. The system automatically converts it to a web-optimized format with optimal quality and tags it with a list of multiple sizes. When a visitor browses on a large desktop screen, they get the large image; on mobile, the browser automatically downloads only the small image that fits the screen width. You don't need to prepare multiple sizes yourself.
• Priority loading for above-the-fold images: The system marks the first module image on every page as the highest priority for download. Images further down the page won't compete for bandwidth with the main image during the first second of loading.
• Reserved image space to prevent layout shifts: All images have their aspect ratios reserved on the layout before they load. This prevents the common issue where text appears, and then a loading image suddenly pushes the text and buttons down, causing the visitor to click the wrong place.

Self-hosted fonts and on-demand loading (Saves bandwidth and protects privacy)

• Self-hosted on platform edge nodes: The website fonts you select in the editor are all provided directly by Kanorio's edge network. The visitor's browser does not need to connect to external servers like Google Fonts (this eliminates cross-domain connection latency and prevents sharing the visitor's IP with third parties).
• Loading only the language and character sets used: The system automatically analyzes the actual text on each page and loads only the font styles and character subsets required for that page, rather than sending the entire multi-language font library to the visitor's mobile device.

4. Why the Website Doesn't Slow Down as You Add More Features

• Built-in modules, zero plugin bloat: Traditional website building often requires installing a dozen third-party plugins to piece together forms, sliders, shops, and SEO features. The more plugins you have, the heavier the scripts, and the higher the risk of conflicts and security vulnerabilities. All of Kanorio's modules and icons are managed centrally and efficiently at the system level. Pages only load what they need, so adding more pages won't slow down your homepage.
• Instant dark/light mode: If your website is set to follow the system's dark/light mode, the page will render with the corresponding background color the instant it opens, avoiding the "flash of white" before the screen turns dark.
• Third-party tracking codes step aside: If you have Google Analytics (GA4), Google Tag Manager, or Meta Pixel installed, the system automatically waits for the above-the-fold content to render or for the visitor to start scrolling before loading the tracking scripts in the background. You don't have to sacrifice site speed for advertising and data analytics.

5. Kanorio Website Hosting Architecture (Technical Details)

If you are a technical professional, an enterprise security evaluator, or a developer planning to integrate with Headless APIs, here is the breakdown of the execution environment and front-end/back-end separation for Kanorio public websites:

Public Website Global Edge Execution Environment

Public websites created with Kanorio are served via the Cloudflare Global Edge Network, benefiting from HTTPS, CDN caching, DDoS protection, and a Web Application Firewall (WAF). Content for different brands is strictly isolated at the rendering and data-reading layers, while the execution environment and security updates are maintained centrally by the platform.

Separation of Public Rendering, Core Back-end, and Database

Public website rendering services are separated from Kanorio's core back-end and database:

• Public Website Edge Rendering Layer: Responsible only for routing, caching, and rendering public pages. It does not connect directly to the main database and does not hold administrative credentials.
• Core Back-end and Database: Data such as members, customer lists, orders, form submissions, and other information requiring authentication are handled by the Kanorio core back-end (hosted on cloud servers and databases in the Singapore region) with access control based on user identity and site permissions (for more on data isolation and infrastructure provider responsibilities, please see ).

Front-end Deployment Flexibility for Headless API Customers

Customers using the , , or can choose their own front-end deployment platform (e.g., Vercel, Netlify, Cloudflare Pages, or their own servers). You do not need to deploy your website on Cloudflare to use content and commerce features via Kanorio's APIs.

Related Documentation