{"id":1807,"date":"2026-10-29T13:14:31","date_gmt":"2026-10-29T12:14:31","guid":{"rendered":"https:\/\/cms.fauves.agency\/?p=1807"},"modified":"2026-10-29T14:08:39","modified_gmt":"2026-10-29T13:08:39","slug":"less-javascript-websites","status":"publish","type":"post","link":"https:\/\/cms.fauves.agency\/en\/index.php\/2026\/10\/29\/less-javascript-websites\/","title":{"rendered":"Why we use less JavaScript when building websites"},"content":{"rendered":"<p>To use less JavaScript on your website often means delivering a simpler, more robust experience.<\/p>\n<p>Not every website interaction needs JavaScript. That may sound obvious, but many websites still load scripts, libraries and components by default before asking whether they are actually needed.<\/p>\n<p>Our starting point is simpler: use semantic HTML for structure, CSS for presentation and interaction where CSS is the right tool, then add JavaScript only when it creates a real benefit.<\/p>\n<p>This is not nostalgia for older ways of building websites. Modern CSS can handle far more than it could a few years ago. Transitions, responsive layouts, filters, disclosure patterns and many interface states can now be built cleanly without turning every detail into a client-side application.<\/p>\n<h2>Less JavaScript is a design decision<\/h2>\n<p>Reducing JavaScript is not only about performance. It is about deciding what the website needs to do before deciding which technology to add.<\/p>\n<p>A simple interaction that works with semantic HTML and CSS is often easier to maintain, easier to test and less likely to fail on a slower connection or an older device. It can also keep the experience more predictable for visitors who use a keyboard, a screen reader or reduced-motion settings.<\/p>\n<p>JavaScript still has an important place. Some features genuinely need it: complex filters, maps, client portals, live data, enhanced forms or interactions that cannot be expressed properly through native browser behaviour. The point is not to avoid it. The point is to make it earn its place.<\/p>\n<h2>Start with the page the visitor receives<\/h2>\n<p>When we build a <a href=\"\/en\/blog\/static-vs-dynamic-websites\/\">static-first frontend<\/a>, the first version of the page is already useful HTML. The structure, headings, content and links are available before extra client-side behaviour is added.<\/p>\n<p>This gives us a clearer base for accessibility and SEO. It also makes it easier to see what every page is actually sending to the browser. <a href=\"\/en\/blog\/when-wordpress-becomes-a-bottleneck\/\">A page should not carry a large interface framework, animation library or tracking stack simply because one small part of it is interactive.<\/a><\/p>\n<h2>Performance is more than a score<\/h2>\n<p>Performance tools are useful because they reveal problems: heavy images, unnecessary scripts, blocking resources or unstable page layout. But a score is not the objective by itself.<\/p>\n<p>The objective is a website that feels direct and dependable. Images and videos should be delivered at an appropriate size. Non-essential scripts should not block the first page view. Interactions should feel intentional rather than decorative. The page should remain understandable before everything has loaded.<\/p>\n<h2>Accessibility and consent belong in the build<\/h2>\n<p>Accessibility is not something added after the interface is finished. It starts with meaningful HTML, logical headings, keyboard behaviour, clear labels, sufficient contrast and a design that does not depend on one specific way of using a device.<\/p>\n<p>The same applies to consent and tracking. A cookie banner is not a decorative legal layer. It needs to control when non-essential tracking technologies are activated. The implementation should make that behaviour visible and testable.<\/p>\n<p>A lean frontend does not guarantee accessibility or compliance. It makes the system easier to inspect, test and improve because fewer hidden layers are working against the page.<\/p>\n<h2>Technical quality is built through choices<\/h2>\n<p>We use tools to test accessibility, performance, SEO and page quality. Those checks are useful, but they do not replace judgement. A high score does not automatically make a website clear, accessible or effective.<\/p>\n<p>What matters is the discipline behind the result: choosing the smallest useful solution, handling media carefully, respecting browser standards, adding code for a reason and testing the delivered website rather than trusting the source alone.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>We start with semantic HTML and CSS, then add JavaScript only when it creates a real benefit for the visitor or the organisation.<\/p>\n","protected":false},"author":1,"featured_media":1833,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[105],"tags":[],"class_list":["post-1807","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-digital-experience"],"acf":{"related_posts":null,"selected_cta_key":""},"rank_math_meta":{"rank_math_seo_score":"62","rank_math_title":"Why use less JavaScript on your website","rank_math_description":"Why use less JavaScript: semantic HTML, modern CSS and useful interactions for lighter websites.","rank_math_focus_keyword":"use less JavaScript"},"selected_cta":[],"wpml_current_locale":"en_US","wpml_translations":{"fr_FR":{"locale":"fr_FR","id":1818,"slug":"pourquoi-nous-utilisons-moins-de-javascript-pour-creer-des-sites-web","post_title":"Pourquoi nous utilisons moins de JavaScript pour cr\u00e9er des sites web","href":"https:\/\/cms.fauves.agency\/index.php\/2026\/10\/29\/pourquoi-nous-utilisons-moins-de-javascript-pour-creer-des-sites-web\/"}},"_links":{"self":[{"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/posts\/1807?lang=en"}],"collection":[{"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/posts?lang=en"}],"about":[{"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/types\/post?lang=en"}],"author":[{"embeddable":true,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/users\/1?lang=en"}],"replies":[{"embeddable":true,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/comments?lang=en&post=1807"}],"version-history":[{"count":3,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/posts\/1807\/revisions?lang=en"}],"predecessor-version":[{"id":1931,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/posts\/1807\/revisions\/1931?lang=en"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/media\/1833?lang=en"}],"wp:attachment":[{"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/media?lang=en&parent=1807"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/categories?lang=en&post=1807"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/tags?lang=en&post=1807"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}