Technical tips, case studies, and thoughts on the modern web.
Technical
Why a static website is often the best option
No database, no CMS to maintain, no WordPress security vulnerabilities. A well-built static site is faster, safer, and cheaper to host.
4 min read
HTMLPerformance
When people think about websites, many automatically think of WordPress, Wix, or Squarespace. And yet, for the majority of showcase websites, a static site is the most relevant solution.
What is a static website?
A static website is a site made of HTML, CSS, and JavaScript files — that's it. No server generating pages on the fly, no database, no PHP. The browser receives the files directly and displays them.
The concrete advantages
Speed — no server requests, content displays almost instantly
Security — no CMS vulnerabilities, no vulnerable plugins, no SQL injection possible
Cost — hosting is minimal, sometimes free
Reliability — fewer moving parts = fewer things that break
SEO — Google loves fast websites with clean HTML
For whom?
If your site is a showcase site, a portfolio, an event page, or a presentation website — static is made for you. If you need a blog, there are static site generators that handle that very well.
What about maintenance?
This is where it gets interesting: a static website requires virtually no technical maintenance. No CMS updates, no plugins to monitor. The content is in the code, and the code doesn't age like a CMS.
At Les Techniciens du Net, all our sites are static. It's a deliberate choice: we prefer to deliver something solid, fast, and durable rather than a WordPress that needs indefinite maintenance.
SEO
Local SEO for craftspeople and merchants in Alsace
Ranking well on Google when someone searches for your trade in your town isn't complicated. But you need to know the basics.
6 min read
SEOLocal
When a potential customer types "plumber Thann" or "restaurant Husseren-Wesserling" on Google, does your business show up? If the answer is no, you're losing customers every day.
Google Business Profile: the foundation
The first thing to do is create and optimize your Google Business profile (formerly Google My Business). It's free, and it's what gets you showing up on Google Maps and in local results.
Local keywords
Your website should naturally contain the terms your customers use to find you:
Your trade + your town
Your trade + your region (Alsace, Thur Valley)
Terms your customers actually use (not technical jargon)
NAP consistency
NAP = Name, Address, Phone. This information must be identical everywhere: on your website, on Google Business, on directories, on your social media. Google checks for consistency.
Customer reviews
Google reviews are a major ranking factor in local SEO. Systematically ask your satisfied customers to leave a review. Reply to all reviews, both positive and negative.
A fast, mobile-friendly website
Over 60% of local searches are done on mobile. If your website is slow or poorly adapted to smartphones, Google penalizes you. It's as simple as that.
Local SEO isn't magic. It's common sense, discipline, and a bit of technical know-how. And the results are often quick to see.
Performance
Your website takes more than 3 seconds to load? You're losing customers.
53% of mobile visitors leave a site that takes more than 3 seconds to display. Here's how to diagnose and fix performance issues.
7 min read
Core Web VitalsOptimization
Google has been clear: loading speed is a ranking factor. And beyond SEO, it's also a matter of user experience. A slow website is a website nobody visits.
How to measure?
Two free tools are enough:
Google PageSpeed Insights — analyzes your site and gives a score out of 100
Lighthouse (built into Chrome) — full audit: performance, accessibility, SEO, best practices
The most common causes
Unoptimized images — a 5 MB photo where 200 KB would suffice
Too much JavaScript — plugins, trackers, widgets piling up
Slow hosting — an overloaded shared server
No caching — the browser re-downloads everything on each visit
Heavy web fonts — loading 8 variants of a Google Font
Quick fixes
Convert images to WebP or AVIF
Enable GZIP compression on the server
Configure cache headers
Remove unnecessary JavaScript
Defer loading of non-critical resources
A performance audit is often the first step towards a website that converts better. And that's exactly what we offer in our audit service.
Technical
Web technologies in 2026: what has changed
CSS Container Queries, View Transitions API, the AVIF format... The web evolves fast. Here are the innovations that truly make a difference.
8 min read
CSSJavaScript
The web in 2026 is an incredible playground for developers. Browsers finally support features we've been waiting for years. Here are the ones that truly matter.
CSS Container Queries
Gone are the days when you could only adapt a component based on the window size. With Container Queries, a component can adapt to the size of its container. It's a fundamental change for responsive design.
View Transitions API
Page transitions without complex JavaScript or frameworks. The browser natively handles transition animations. The result: websites that behave like apps, with a fraction of the complexity.
The AVIF format
AVIF offers 50% better compression than WebP, with equivalent quality. All modern browsers support it. It's the new standard for web images.
Native CSS Nesting
No more needing Sass just to nest selectors. Native CSS now supports nesting. A welcome simplification for projects that want to stay lightweight.
Popover API
Tooltips, modals, and context menus can now be handled natively by the browser, with a simple and accessible-by-default API. Less JavaScript, more reliability.
These developments reinforce our belief: you can build remarkable websites with native web technologies, without heavy frameworks or complex dependencies.
SEO
Schema.org: the secret to standing out on Google
Structured data helps Google better understand your website and display rich results. It's easy to implement and it changes everything.
5 min read
Schema.orgRich Snippets
Have you ever seen those Google results with stars, opening hours, prices, or FAQs right on the results page? Those are rich results, and they're generated thanks to Schema.org structured data.
How does it work?
You add a small JSON-LD code block to the HTML page. This code describes the page content in a format that Google understands: "this is a local business", "here are its hours", "here are its reviews".
The most useful types
LocalBusiness — for shops and craftspeople (address, hours, phone)
Article — for blog posts (author, date, description)
FAQ — for frequently asked questions pages
Product — for product pages (price, availability, reviews)
Event — for events (date, venue, price)
The impact on SEO
Structured data isn't a direct ranking factor. But it significantly increases click-through rates: a rich result catches the eye and inspires trust. More clicks = more traffic = better rankings over time.
On this very website, we use Schema.org LocalBusiness. It's a practice we systematically apply to all the websites we build.