Bulma drops to second last place

by Andy Prevost

Saturday December 6 2025

Bulma is a CSS framework that I have used in the past. I was engaged in the framework and developed quite a few websites with the code base, starting with v0.9.4. I did have some concerns ... Bulma is a huge size. 

I need to make it clear: I do not use any CSS pre-processor. I use the CDN as offered by the development team. That is usually the full package and is already processed and pure CSS.

Bulma, in the version I started with, was already more than three times the recommended size of data to transfer from a web server to a user's browser. My servers are already optimized to use every possible optimized compression technique to serve data quickly. There is only so much you can do, though. I was not alone in expecting Bulma to reduce the overall size.

Not to be ... the developer(s) of Bulma have increased the size in every version since then. And its popularity was wained too. It has dropped in market share from second place to second-last place. W3C tracks a dozen frameworks. As of December 7 2025, Bulma has tumbled to second last place, just slightly ahead of Spectre. Right ... I haven't got a clue what Spectre is, and Bulma is now in that same crowd.

Bootstrap remains the leader in market share – although it has dropped slightly in percentages. Tailwind continues its ascent nearly doubling in market share over the past year. 

And, by the way, I no longer recommend Tailwind CSS. It also has become quite bloated and more difficult to use.

I do recommend that you develop your own. Quite frankly, it is not that difficult. Unlike Bulma's reset, I started with "modern-normalize" ... a full reset is a dumb idea. The entire concept of "normalize" is to have all browsers display a web page the same way. You don't need to re-create every HTML css to accomplish that.

I must admit that I researched quite a few classless and class-light packages. There are quite a few good packages. But again, I don't recommend any (if you search my articles, there are previous recommendations). Many are trying to fill the void somewhere between class-light and "kitchen-sink".

The other point to make in developing your own framework: before you get too far into CSS code, settle on a grid strategy. That can be half the size of your CSS framework if you try to mimic the 12-column standard created by packages like Bootstrap. A 12-column grid is absolutely not necessary these days. My grid CSS is a total of about one dozen lines and less than 1 Kb. And it is fully responsive. It is a lot easier to create a special grid, if needed, in your style.css file unique to one website.

If you read my recent articles, my framework is now classless. Entirely classless. That includes a responsive horizontal megamenu. Not only classless, but also not one single line of javascript. Pure CSS. Also need to point out that it is impossible to have a complete framework without some classes. Buttons in particular. That being said, every time I think of a component that I would like to see in my framework, I have found a way to make it classless. The most challenging so far has been the megamenu. 

For those that want to see my code: sorry, I am no longer interested in tutoring or teaching. I encourage you, though, to start and give it a try. 

 

◀ Previous Next ▶

Post a Comment