How Better Hosting Can Support More Complex Website Designs

Hosting for Complex Websites

On the slowest websites, the server’s first response takes almost as long as Google’s entire target for showing the main content. HTTP Archive data for 2024 found that sites with a poor Largest Contentful Paint spent 2.27 seconds waiting on Time to First Byte, against a threshold of 2.5 seconds for a good score. A complex design adds weight after that wait, and the hosting largely determines how long the wait lasts before any of the design can start to load.

Page Weight in a Modern Design

The median mobile home page in the 2024 Web Almanac loaded 558 KB of JavaScript, 900 KB of images and 111 KB of fonts, and the desktop figures were higher on each count. Sliders, video backgrounds, animation libraries and several font weights all add to those numbers, and each one is a separate request the browser has to make. The median page as a whole weighed 2,311 KB on mobile and 2,652 KB on desktop in October 2024, and the mobile median grew 6.4% in 12 months. JavaScript was the most requested file type, at 22 files per mobile page and 24 per desktop page.

Much of that code belongs to other companies. The Web Almanac found at least one third-party service on about 92% of pages, such as analytics tags and embedded video. Those files load from their providers’ servers, outside the site’s own hosting, so the design stage is the place to limit them.

On a dynamic site, every uncached page request runs code and database queries on the server before a single byte of HTML is sent. A page with 20 content sections and a product grid asks the server for far more work than a plain article page, and that work happens on every visit unless something stores the result. Database size adds to that work, since large product catalogs and saved revisions make each query slower as the tables grow, and a design that shows related products or live stock levels runs more queries on every page.

Design Tools and Generated Code

Visual editors let a person with no coding background build layered, animated layouts. A design assembled section by section in a website builder produces its code from the settings chosen in the editor, and every added effect generates more of it. The finished page can look simple and still contain several layers of nested containers behind each visible block.

That generated code has a cost on the server as well as in the browser, since the builder has to assemble the page from stored settings on each uncached request. In the Web Almanac’s 2024 figures, WordPress sites passed Core Web Vitals on mobile 40% of the time, up from 28% the year before, and their median mobile page weighed 2,047 KB.

Server Response Targets

Google’s guidance treats a Time to First Byte of 0.8 seconds or less as good and anything over 1.8 seconds as poor. The measure covers the full wait from the request to the first byte of the response, including the server’s processing time.

The 2024 Web Almanac found that only 42% of mobile sites had a good server response time, 40% needed improvement and 19% were poor, and its authors noted little change in that share compared with the gains in other measures. Sites with a good Largest Contentful Paint spent about 600 milliseconds on the same wait, which leaves most of the 2.5-second budget for the design itself.

PageSpeed Insights reports the Time to First Byte that real Chrome visitors received, for sites with enough traffic, and testing an uncached page separately shows how long the server takes when it has to build a page from nothing.

Resource Limits on Shared Plans

Entry-level shared plans place many sites on one machine and divide its processor time and memory between them. Each plan also limits how many requests it can process at the same moment. A heavy page that takes twice as long to build occupies one of those slots for twice as long, so a modest rise in visitors can leave requests waiting in a queue.

A simple site can stay fast on limited resources because each request finishes quickly. A design with dynamic product filters, search, logged-in areas or a busy checkout needs more processing per request and more requests at once, and a plan with dedicated processor cores and memory gives it that room without competing with neighboring sites. Moving to a larger plan usually needs no change to the design, since the same files and database are copied to the new server.

Caching and Content Delivery

A page cache stores the finished HTML of a page after the first request, so later visitors receive the stored copy without the server running any code, and the browser can keep its own copies of static files under the rules set by HTTP caching headers. An object cache keeps the results of frequent database queries in memory for the parts of a site that cannot be cached as whole pages, such as a shopping cart. Checkout and account pages change for each visitor and are left out of page caching, so their speed depends on processing power and the object cache, and those are the pages where a slow response costs a sale.

A content delivery network places copies of static files such as images and fonts on servers closer to each visitor. For a design heavy with media, that shortens the distance the largest files travel on every load. The same network answers most requests for those files during a traffic spike, so the site’s own server only has to process the requests that need it.

Protocol and Image Support on the Server

Newer server software supports HTTP/3, which runs over a different transport protocol and reduces the delay caused by lost packets on unreliable mobile connections. Support has to exist on the server side before any visitor’s browser can use it, and browsers that cannot use it fall back to HTTP/2 automatically, so enabling it has no downside for older browsers.

The server can also convert and resize images automatically, sending modern formats such as WebP and AVIF to browsers that accept them. For a design that relies on large photographs, that conversion reduces the heaviest category in the page weight figures without any change to the layout.

Measured Costs of a Slow Load

A Deloitte study of 30 million user sessions across retail, travel, luxury and lead generation brands found that a 0.1-second improvement in mobile site speed raised retail conversions by 8.4% and average order value by 9.2%. For lead generation sites in the same study, bounce rates on information pages improved by 8.3%. A complex design on a server that answers slowly loses those gains before the visitor has seen the first image, and the loss repeats on every page view until the hosting changes.

(Visited 97 times, 1 visits today)
↑
Close
0 Shares
Tweet
Share
Pin
Share