DIGIBOY
In-house project

Case Study: Building digiboy.in as a Fast, Content-First Website

How we built our own site as static pages generated from plain content files, with one small script, one stylesheet and no third-party requests.

Updated · 5 min read · By the Digiboy team

Digiboy is a new studio. We publish a case study only for work that is live and that you can check for yourself. Client case studies will appear here as projects launch and clients agree to share them.

Client
Digiboy (our own website)
Work
Web design, development, content structure
Year
2026
Built with
Astro, Tailwind CSS, Markdown

The first website Digiboy built was its own. This case study is about a real, public project, and everything in it can be checked by opening the site and looking. The figures below were measured from the built site in November 2026.

The brief

We wanted the site to prove four things we say to clients:

  1. Fast on a phone. Most visitors in Kerala arrive on mobile data, so the site has to be light.
  2. Easy to grow. A studio that publishes guides every month cannot rebuild its site every month.
  3. Readable by machines. Search engines and AI assistants should understand every page.
  4. Owned outright. No rented platform, no plugin licences, no lock-in.

What we built

Pages made in advance

digiboy.in is a static website. Every page is generated once, when the site is published, and stored as a finished HTML file. When you open a page, a server near you sends that file. Nothing is assembled on the spot, and there is no database behind it.

That choice does most of the work for speed and security. There is no admin login on the public site to attack and no plugin to fall out of date.

Content as plain files

Every page starts as a plain text file. A service, a guide or a blog post is one Markdown file with a short block of fields at the top: title, description, date, key takeaways, questions and related pages. The file name becomes the page address.

From that one file the site produces the page itself, its entry in the menu and footer, its line in the sitemap, its structured data, its item in the RSS feed and its entries in the two editions for AI assistants. Nobody has to remember to update five places. This is how the site reached more than 80 pages without becoming hard to manage.

One route table, a handful of templates

All pages are drawn by a small set of templates: one for landing pages such as services and guides, one for blog posts, and one each for pages like About and Contact. A new section, such as these case studies, is a folder of files and one line of configuration.

Very little JavaScript

JavaScript is the code that runs in the visitor’s browser. It is also the most common reason sites feel slow on mid-range phones. On digiboy.in:

  • Icons are drawn when the site is built and shipped as part of the HTML, so no icon library loads in the browser.
  • The only script handles the gentle reveal of sections as you scroll.
  • If that script fails, or if the visitor has asked their device to reduce motion, the page simply shows everything at once.
  • With JavaScript switched off, every page is still fully readable.

Fonts and files from our own address

The two typefaces are served from digiboy.in itself, not from a third-party font service. No page calls another company’s server, so there is nothing external to wait for and no visitor data is passed on. If analytics is added, it will be the one exception, and the privacy policy will say so.

What we measured

Measure Result
Pages generated More than 80
Script files per page 1, about 26 KB compressed
Stylesheets per page 1, about 10 KB compressed
Home page HTML About 14 KB compressed
Requests to third-party servers None
Database queries per visit None
Readable with JavaScript off Yes

“Compressed” means the size that actually travels over the network. For comparison, a single uncompressed photo from a phone camera is often several thousand kilobytes.

What we have not measured yet

We have not published Core Web Vitals or other speed-test scores here. Those figures should come from the live site on real phones, and the hero artwork is still being finalised. Once the site has been live long enough to have field data, we will add the numbers to this page with the date they were taken. You do not have to take our word for it in the meantime: test any page at pagespeed.web.dev and read the mobile result.

Trade-offs, honestly

A static, hand-built site is not the right answer for everyone.

  • Editing is by file, not by dashboard. That suits us. A client who wants to edit pages from a browser needs a content editor added, or may be better served by WordPress. See WordPress vs custom website.
  • Interactive features need more. Bookings, logins, carts and payments need server-side code or a connected service.
  • It costs more to build than a template. The website cost guide explains the difference between a template site and a custom one.

What a business owner can take from this

  • Ask your developer how many scripts and third-party services each page loads, and why each one is there.
  • Keep content separate from design, so that changing one does not break the other.
  • Prefer fewer moving parts. Every plugin is something to update.
  • Test on a mid-range phone on mobile data, not on office Wi-Fi. The article on website speed in Kerala shows how.

Work with us

This is the standard of build behind Digiboy’s web development service. Tell us what you need on the project form and we will reply with next steps and a fixed quote.

FAQ

Questions people ask

What technology is digiboy.in built with?

digiboy.in is built with Astro, a framework that generates static HTML pages, and styled with Tailwind CSS. The content is written in Markdown and JSON files, and the site is served as static files from Cloudflare's network.

What is a static website?

A static website is one where every page is built in advance and stored as a finished file. When a visitor asks for a page, the server simply sends the file. There is no database to query, which makes static sites fast and gives attackers very little to target.

Is a static website right for every business?

No. A static website suits brochure sites, blogs and content-heavy sites. A business that needs customer logins, live stock, bookings or a checkout needs server-side features as well, either added to a static site or built as a web application.

How fast is digiboy.in?

Digiboy has not published speed-test scores for digiboy.in yet. What can be stated is the page weight, which is one script of about 26 KB and one stylesheet of about 10 KB when compressed, plus the HTML and images, with no third-party requests.

Have something to build?

Tell us the idea. We will tell you how to build it.

Start a project