The frontend is everything a visitor sees and touches on your website: the page layout, fonts, images, menus, forms and the way buttons respond when clicked. It is the code that is downloaded to and runs inside the visitor's browser, as opposed to the backend, which runs on a server they never see.
The three building blocks
- HTML describes the content and structure: this is a heading, this is a paragraph, this is a form with three fields.
- CSS controls appearance: colours, spacing, fonts and how the layout changes on a phone.
- JavaScript adds behaviour: opening a menu, validating a form before sending it, updating a cart total without reloading the page.
On modern projects these are rarely written by hand from scratch. Developers use frameworks such as React, Vue or Svelte to build pages from reusable components, styling tools like Tailwind CSS, and build tools like Vite that bundle everything into small files for the browser.
How the frontend talks to the server
When someone submits your contact form, the frontend checks that the email field looks valid, then sends the data over the internet to the backend, usually through an API. The backend saves it or emails you, and replies; the frontend then shows "Thanks, we'll be in touch". The visitor only experiences the frontend half of that conversation.
A slow menu page is a frontend problem
A restaurant's menu page loads slowly on phones and the "Book a table" button is hidden below a huge photo. Neither problem involves the server: the image is oversized and the layout is poorly arranged for small screens. Both are frontend fixes, compressing the image and moving the button up, and both directly affect whether someone books.
Why the frontend matters to you
For most small-business sites, the frontend is where results are won or lost: speed, mobile layout, readable text, clear calls to action and accessibility are all frontend concerns. Google's Core Web Vitals (LCP, INP and CLS) measure mostly frontend behaviour. Sites generated by We.Inc use a React, Vite, TypeScript and Tailwind CSS frontend.
Frontend mistakes that cost visitors
- Designing only on a desktop monitor. Many small-business visitors arrive on phones; test there first.
- Uncompressed images. A 5 MB hero photo can make a page feel broken on mobile data.
- Relying on frontend checks for security. Anything in the browser can be bypassed; the backend must validate too.
- Piling on scripts. Every chat widget and tracking tag adds JavaScript the browser must download and run.
Related terms
- Backend: the server side the frontend depends on.
- Full stack: working across both frontend and backend.
- React: a popular library for building frontends.
- CSS: the styling language of every frontend.