Websites that load fast, read clearly and get found.

Key terms, in plain words

Core Web Vitals

Three Google measures of real user experience: Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS). Good scores are LCP within 2.5 seconds, INP within 200 milliseconds and CLS of 0.1 or less.

Field data and lab data

Field data comes from real Chrome users over the past 28 days. Lab data comes from one simulated test. Google uses field data, so a perfect lab score can still hide slow real visits.

Content management system (CMS)

The software your team uses to edit pages without code. WordPress is one. A headless CMS stores content separately and sends it to a custom front end.

Template

A reusable page layout, such as a service page or a blog post. Good templates keep pages consistent and make new pages quick to add.

WCAG 2.2

The Web Content Accessibility Guidelines published by the W3C. Level AA is the usual target for business sites and covers contrast, keyboard use, labels and more.

Staging site

A private copy of the website used for testing. Updates and new features are checked there before visitors see them.

301 redirect

A permanent redirect from an old URL to a new one. It sends visitors and search engines to the right page after an address changes.

Responsive images

Images served in several sizes so each device downloads only what it needs. Modern formats such as WebP and AVIF cut file size further.

What actually makes a site fast

Speed problems usually come from a few heavy things, not many small ones. The biggest are oversized images, too much JavaScript, slow server response and third-party scripts such as chat widgets, ad tags and video embeds.

LCP is often decided by one element: the hero image or the main heading. Making that element light, loading it first and serving it from a nearby server does more than a dozen minor tweaks. INP suffers when scripts keep the browser busy, so cutting and delaying JavaScript matters most there.

CLS comes from things that load late and push content down. Setting width and height on images, reserving space for embeds and loading fonts carefully keeps the page still. Each new plugin or tag should earn its place, because speed is usually lost one addition at a time.

Common mistakes we see

• Designing before writing. Layouts get approved with placeholder text, then the real content does not fit. Draft the key pages first and design around them.
• Approving designs on a large monitor. Visitors use phones, but reviews happen on desktops. Review every design at phone width first.
• Treating accessibility as a final check. Fixing contrast, focus order and labels after the build costs far more than designing them in. Include accessibility in every design review.
• Launching without testing forms. A form that looks fine but never delivers its email loses leads quietly. Send test entries through every form and confirm where each one lands.
• Accounts owned by someone else. The domain, hosting or theme licence sits in a freelancer's or agency's account. Keep every account in your company's name, with admin access for your team.
• Leaving staging open to search engines. A test site gets indexed and competes with the real one. Protect staging with a password, not only a noindex tag.

A quick self-check

What changes the price

• Number of unique templates. Twenty pages that share three layouts cost less than ten pages that each need their own design. Templates, more than page count, drive design and build time.
• Who writes the content. Writing and editing copy can take as long as design. Supplying finished content lowers the cost. Having us write it adds time.
• Languages and right-to-left support. Each language adds translation review, metadata and testing. Arabic needs mirrored layouts and checks on every template.
• Integrations. Connections to a CRM, booking tool, payment system or inventory feed each need setup, testing and error handling.
• Content and URLs to migrate. Moving hundreds of posts, products or files takes mapping, clean-up and redirect testing.

What we measure

• Core Web Vitals in the field. LCP, INP and CLS for real visitors. They come from the Chrome UX Report, shown in PageSpeed Insights and Search Console.
• Form and call conversions. Leads per page and per traffic source. They come from GA4 events and your CRM.
• Indexed pages. How many pages Google has indexed compared with how many you want indexed. It comes from the page indexing report in Search Console.
• Accessibility issues. Automated scan results plus manual keyboard and screen reader checks. Automated tools catch only part of the problems, so both matter.
• Page weight. The total size of a page and everything it loads. Heavy pages are slow on mobile networks. It is measured with browser developer tools.
• Uptime and errors. How often the site is down and how many visits hit errors such as 404 or 500. It comes from uptime monitoring and server logs.

How to choose a partner

• Can we see live sites you built? Live URLs you can open on your own phone, not only screenshots. Run them through PageSpeed Insights yourself.
• Who owns the code, design files and accounts? You do, and the contract says so. Accounts are set up in your name from day one.
• How do you test accessibility? Automated scans plus manual checks with a keyboard and a screen reader. A good answer names the WCAG level they test against.
• What happens after launch? A set period for post-launch fixes, and an optional care plan with clear response times.
• How will our team update the site? A demo of the editing screens during design, and training before handover. If every change needs their help, ask why.