Skip to content

A calm site that is also light

We wanted this site to feel rich without feeling heavy. Here is how we kept the motion gentle and the pages light, and what a page checker said when we ran it on 28 October.

5 min read

A single dark glass tablet with a glowing gold icon floating calmly above an almost empty wooden desk in soft light.

5 min read

On 28 October 2026 we ran a free page checker over seventeen pages of this site, in English and in Hebrew, at phone size and at desktop size. Most scores were 100. A few were not, and we say which below.

A site with a big picture, soft glows and drifting sparks can easily become heavy. We had already seen what too much movement looks like in our first design, so this story is about how we kept the look and kept the weight down.

Key points

  • The motion is gentle, and it switches off for visitors whose devices ask for less motion.
  • Pictures use a smaller image format, fonts come from our own site, and pages are built ahead of time.
  • On 28 October 2026, accessibility, best practices and search visibility (SEO) scored 100 on all seventeen pages we checked.
  • Performance scored 100 at desktop size. On a simulated phone it first scored 91 to 99, and after we trimmed pictures and fonts, 94 to 100.

Movement that does not cost much

The motion on this site is small on purpose: things lift a little when you point at them, and a slow trail of sparks drifts by. It is all made with the page’s own style rules, with no animation program running in the background.

We also changed the glow around the cards so it only moves things that the computer’s graphics hardware can move with little effort. And when a visitor’s device says it prefers less motion, every one of these movements is switched off.

Pictures, fonts and pages

  • Pictures are saved in a newer format that makes the same picture smaller.
  • Fonts come from this site itself, so the page does not wait for another website.
  • Style rules (how things look) are placed inside each page, so the browser does not wait for a second file before it can draw the page.
  • Pages are built once, ahead of time. Opening one is just sending a file.
  • Files that never change are kept (cached) by the visitor’s browser for a year.
  • The accessibility menu and the cookie notice were first built as interactive pieces that need extra code to run. We rewrote them as plain HTML (the basic language of web pages) and a small script (a short piece of code), so they add almost nothing to the page.

What is a cache?

A cache is a place where a browser keeps a copy of a file it already downloaded, so the next visit does not fetch it again. It is like keeping a book at home instead of going to the library every time.

How we checked

We used Lighthouse (opens in a new tab), a free checker that scores a page for speed, accessibility, good practices and search visibility (SEO).

We did not run it against a plain test server. A plain server serves files differently from our real host, and that measures the test instead of the site.

What is a server?

A server is a computer, usually far away, that answers requests from your browser: it keeps web pages and files and sends them when asked. Our host is the service whose servers keep this site online. A test server is a simple stand-in on one computer, and measuring a stand-in measures the stand-in.

So our check runs a local copy that serves files the way the host does, compressed (made smaller to send) and with the same rules for what the browser may keep. We corrected the check script itself within an hour of adding it.

What it said

On 28 October 2026, across seventeen pages in both languages, including these stories:

  • accessibility, best practices and search visibility scored 100 on every page, at both sizes;
  • performance scored 100 at desktop size on every page;
  • performance on a simulated phone connection (the checker pretends to be a slow phone on a slow connection) was lower: between 91 and 99, over two runs.

On the simulated phone, the largest visible part of each page appeared after 2.0 to 3.2 seconds over the two runs. On desktop it was under a second. The simulated phone is deliberately slow, but a number below 100 is still a number below 100, and we would rather tell you than round it up.

Trimming after the first run

We did not leave it there. A simulated slow phone counts everything that downloads before the page first appears on screen, so weight is what sets the score. We trimmed three things:

  • pictures are saved at a lower quality, and the home picture went from 67 KB to 40 KB;
  • fonts for parts of the page nobody sees yet, the closed accessibility menu and on phones the footer, are no longer downloaded early;
  • two small font files no longer sit inside the styling of every page.

After that, phone-size performance over three runs on 28 October was between 94 and 100, and in our own run the largest visible part of each page appeared after 1.7 to 2.4 seconds. Not every page reached 100. What is left is mostly the fonts that give the site its look, and we chose to keep them.

What we take from it

The calm look and the light pages did not pull against each other. Every effect we kept costs very little, and where an effect cost more, such as the glow that travelled around the cards, we changed it.

Read next

Hebrew and English as equalsEvery page of this site exists in English and in Hebrew, read left to right and right to left. Here is what that meant for the fonts, the layout, the error page and the way we check our words.We fact-checked our own case studiesBefore our case studies went live, we checked every claim against the real code and the live sites. Some of our first wording was wrong. Here is what changed.

Got something to build? Let's talk.

No sales pitch. Tell us what your business needs and we'll tell you straight how we'd tackle it, or whether you need it at all.

6 stories about BotKB.com

All 6 stories

We were not happy with the first designThis site started with ideas from Gemini and Claude, and a lot of movement. We were not happy with it. Here is what we built first and what we threw away.One picture changed the whole siteWe brought one picture, and the colors, the mood and the words of every page followed it. A story about taste, and about letting an assistant do the matching.A calm site that is also lightYou are reading this story. We wanted this site to feel rich without feeling heavy. Here is how we kept the motion gentle and the pages light, and what a page checker said when we ran it on 28 October.Hebrew and English as equalsEvery page of this site exists in English and in Hebrew, read left to right and right to left. Here is what that meant for the fonts, the layout, the error page and the way we check our words.We fact-checked our own case studiesBefore our case studies went live, we checked every claim against the real code and the live sites. Some of our first wording was wrong. Here is what changed.What we did and what the assistant didA plain list of who did what in building this site: the taste, the pictures and the corrections on our side, the building, the matching and the checking on the assistant's.
Accessibility menu

Keyboard shortcuts

Open accessibility menuAlt+A
Accessibility statement

These settings are saved on your device only and are used to adjust the display. They do not change the site content and send no information to any server.