Responsiveness

Responsiveness (or responsive web design) is an approach to designing and coding websites that ensures a site displays optimally on every type of device, from desktop computers and laptops to tablets and smartphones. A responsive site automatically detects the screen size (browser width) and dynamically adapts the layout of elements, the size of text and images, and the navigation, so that the page stays readable and easy to use.

In the past, separate versions of sites were built for mobile devices (m.site.sk, for instance). Today responsiveness is the standard: there is only one version of the site and one URL, which uses CSS technology (media queries) to change its appearance.

The basic technical principles of responsiveness are:

  1. A fluid grid: elements are defined not in fixed pixels but in percentages.
  2. Flexible images: images are never displayed wider than the screen.
  3. Media queries: rules in the code saying “if the display is narrower than 600 pixels, hide the sidebar and turn the menu into a hamburger icon”.
  4. The mobile-first approach: a strategy in which the site is designed for the smallest screens first and features for larger displays are added afterwards.

Advantages

  • Better user experience (UX): visitors do not have to zoom in on text or scroll horizontally, which lowers the bounce rate.
  • Better SEO (Google Search): Google favours responsive sites (mobile-first indexing). If your site is not responsive, it will slide down the search results.
  • Easier administration: you update content once in one place and the change appears on every device at the same time.
  • Higher conversion rate: customers on mobile buy more often when the buttons are big enough and the forms are clear.
  • Future-proof: a responsive site is ready for new devices that have not yet reached the market (various sizes of smartwatch or foldable display).

Disadvantages

  • More demanding development and testing: the designer and developer have to check the site at dozens of different resolutions and on several operating systems.
  • Longer loading time (if the site is badly optimised): if a phone downloads the same huge images as a desktop, loading can slow down (solved with adaptive images).
  • Design compromises: with very complex tables or interactive maps it can be hard to devise a workable display on a small screen.
  • Higher initial cost: designing a responsive site takes more hours of designer and frontend developer time than a fixed-width one.

Practical example

Imagine you run a restaurant.

  • A non-responsive site: a customer in town looks up your menu on their phone. They have to pinch-zoom tiny letters, cannot tap the phone number and constantly slide the screen left and right. Frustrated, they go to a competitor.
  • A responsive site: the menu appears in one clear column, the food photos sit one beneath another and a large “Call” button glows at the bottom of the screen, ready for a thumb. The customer books a table immediately.