If you didn’t build your own site, you’re likely using a content management system (CMS) that your web builder chose. If he or she didn’t educate you on the pros and cons, you may be in for a big surprise in your webpages’ performance and search engine rankings.
The technical definition for a content management system (CMS) is “is a computer software program used to manage the creation and modification of digital content.”
In other words, it is a system that allows the content to be stored separately from the code that builds the page. The user enters the code through a program called an interface, e.g. WordPress, and the interface saves that as the page data. The browser takes the files from both locations and renders the page.
However, while simple and easy, it creates a problem. To make this easier to understand, I use a simple metaphor of an architect, contractor, and warehouse. The user is the architect, the contractor is the browser, and all the design code sits in the warehouse
In this metaphor, we are going to use a prefabricated home. There are a general set of blueprints, but lots of options for flooring, tiles, etc. Think of this as your theme.
The architect now selects specific options within a house, for example, flooring, tile, window type, etc. But, these specifications aren’t given to the contractor (browser) until he or she shows up to build the house.
The contractor knows he or she is building a home, but other than that, it’s left open. Therefore, they have to bring all the labor and materials they might use, even if they aren’t needed in this specific build.
Once at the site, the contract reads the blueprints and then has to sort through and organize their materials first before the job can start.
As you can see there is a lot of wasted time and materials that put a burden on the contractor. This is why a theme will never be as fast as a custom build.