Technology
This page is for readers interested in the technology: what goes into every site and how it is measured.
What goes into every site
Speed
The site is hand-written HTML (the page structure) and CSS (the look), with none of the extra code a page builder adds. A client site's home page is typically about 15 kB (kilobytes). Server response time, meaning the time the server takes to return the page, is typically 0.2 to 0.6 s and is recorded at launch.
Structured business data
Every page gets schema.org markup (a machine-readable description of the business and its services) in JSON-LD format, as its own block in the page code. Also included are a sitemap (sitemap.xml, a list of page addresses), robots.txt (rules for search engines) and a canonical address for each page (a tag that states the page's main address). Google's Rich Results Test tool checks the markup for errors.
Accessibility
The site works with a keyboard, and the spot you are on is clearly visible. Contrast between text and background is at least 4.5:1, which is the AA level requirement of WCAG (Web Content Accessibility Guidelines, the international accessibility guidelines). Form fields have labels, and motion is reduced if the browser asks for it.
Security
The connection is encrypted with HTTPS, where an SSL certificate protects traffic between browser and server. The site is static, meaning ready-made files, with no plugins that go out of date. The form has a hidden field against spam bots.
Measurement
Before launch the site is tested on a phone and a computer, and speed is recorded at launch. The measurement methods are explained below.
How we measure
PageSpeed Insights
Google's free tool that tests page speed on a phone. Among other things it reports LCP (Largest Contentful Paint, the time it takes for the largest content on the page to appear). We run it at launch and record the result.
Search Console
Google's free tool that shows how Google reads the site. It shows which pages are found, which searches bring people there and whether there are errors. We use it for monitoring in the Growth plan.
AI visibility
We measure our own AI visibility once a month: 10 questions on four AI platforms, for example ChatGPT and Gemini. We publish the results together with the method.
What we don't do, and why
No promised ranking in AI answers
The same question gives a different answer practically every time. So a ranking cannot be guaranteed or reliably measured. What we can do is build the site so that machines can read it.
We don't sell llms.txt as visibility
llms.txt is a small text file that describes a site to AI bots. According to Google's own guidance, Google does not use it for search visibility. This site has one, but no promise is made about it.
No FAQ markup for search results
Many add FAQ markup (FAQPage, questions and answers in machine-readable form) to a page hoping for an expanded search result, a rich result. In 2023 Google limited these to government and health sites and has since stopped showing them, so we don't use the markup.
No near-identical city pages
Dozens of near-identical pages where only the city changes do not help the customer. Google's spam policies forbid this kind of mass production, so every page has its own content.
We don't invent reviews
The site shows only real Google reviews, no invented quotes or numbers. Review requests follow Google's rules with no filtering, and reviews are never bought.
Technical details in depth
Open whatever interests you.
Show technical details: structured business data
schema.org types used on this site (schema.org is the vocabulary used to write machine-readable markup):
- Home page: LocalBusiness and Organization (business, service area and price range), WebSite (the site) and WebPage (the page).
- Service pages: Service (the service and its price) and BreadcrumbList (the page path, for example Home / Pricing).
- Pricing, FAQ and Technology: only WebPage and BreadcrumbList.
- Who builds it: Person (person: Henry Tuomisto, employer Luellux).
- No FAQPage markup and no review markup (AggregateRating, the average of reviews; Review, a single review).
The markup always matches the visible text of the page. The sitemap contains only the Finnish pages and the modification date (lastmod). Multilingual sites get hreflang tags, which tell search engines which language version is meant for whom.
Show technical details: hosting
Sites are published on Cloudflare Pages (Cloudflare's service for publishing static sites).
- Files are served from Cloudflare's CDN (Content Delivery Network, servers in different countries), so the page loads from close to the visitor.
- The HTTPS certificate comes with the hosting.
- The form is sent by a small Cloudflare server function (Pages Functions), which forwards the message to email.
- The domain is registered in your name, and the login details are handed over to you.
Show technical details: no plugins
- No page builder and no WordPress plugins (add-ons that go out of date and need updating).
- The site is hand-written HTML and CSS, plus one small JavaScript file (code that runs in the browser) for the menu and forms.
- No third-party scripts and no Google Fonts: fonts are loaded from our own server.
- Images are at most 200 kB and are served in AVIF and WebP formats (lighter than the common JPG format), with JPG as a fallback.
Three ways to start
-
Free website review
Tell me your website address. Within 2 working days you get a report on what is worth fixing.
Request a review -
15-min call
Book a time straight from the calendar. Google Meet, no sales pitch.
Book a time -
Start a project
Two fields, a reply the same working day.
Start