Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

Launch testing · 21 Nov 2026 · 6 min read

Cross browser testing: what to check before your site goes live

A site that looks right on the developer's laptop can break on a customer's phone. Cross browser testing finds the gaps before launch.

The short answer

Cross browser testing means checking your website in the browsers and devices your visitors actually use, beyond the one it was built on. Test the current versions of the main desktop and mobile browsers, a small phone and a tablet, and check layout, forms, menus and checkout. Use your analytics to choose, and real devices where you can.

What cross browser testing is for

Cross browser testing is the check that a website works for the range of browsers, screens and devices its visitors use. Browsers read the same code slightly differently. Screens differ in size, shape and resolution. A few details that look fine in one place can break in another: a button that will not tap, a menu that opens off screen, a font that falls back to something plain, a form that does not submit.

It is also known as device testing for websites, and it is a normal stage of any careful build. It does not mean the site must look pixel for pixel identical everywhere. The standard is that every visitor can read the content, use the navigation and complete the actions that matter, on whichever browser they happen to have. Small differences in spacing or font smoothing are normal.

Testing is cheaper before launch than after. Once a site is live, a broken checkout on one browser means lost orders you will not hear about. Include it in your pre-launch routine, alongside the items in our website launch checklist.

Which browsers and devices should I test?

Test what your visitors use, not what is fashionable. If you already have a site, your analytics will show the browsers, operating systems and screen types your visitors arrive on. For a new site, assume a mix and cover the main families of each kind.

GroupWhat to includeWhy
Desktop browsersThe current versions of the main browsers on Windows and on MacMost office visitors and many buyers use a desktop
Phone browsersThe default browser on an iPhone and the default browser on an Android phoneMost visits to many sites come from phones
Screen sizesA small phone, a large phone, a tablet in both orientations, a laptop and a wide monitorLayouts change at different widths
Older versionsOnly if your analytics show real visitors on themAvoid wasting time on browsers nobody uses
Input and settingsKeyboard only, larger text, and dark mode if the site supports itAccess needs and preferences vary

There is no fixed list that suits everyone, so agree one with your developer and write it down. A list kept in the project documents means later changes can be tested against the same set. Our guide to what a mobile-friendly website means and how to check it goes deeper on the phone side.

How do I test without owning every device?

You do not need a drawer full of phones. A layered approach covers most of what matters at modest effort.

  1. Start with your own devices. Whatever people in the business already carry is a real test bed, and they will catch things a developer would not.
  2. Use the responsive mode built into desktop browsers. It resizes the page to imitate phone and tablet widths. It is quick and useful, but it does not reproduce how a real phone handles touch, fonts or the on-screen keyboard.
  3. Ask friends, family and colleagues to open the site on their own devices and send a screenshot of anything odd. Give them a short list of pages and tasks.
  4. Use a cloud testing service that provides real devices and browsers over the internet. Many offer a free trial or a free tier with limits, so check the current documentation and plans before you rely on one.
  5. Borrow a device for the final check. One older phone and one tablet often show problems the newer ones hide.

Whichever method you choose, test real tasks, not just pages. Add something to the basket and pay. Submit the contact form. Open the menu and close it. Scroll to the footer. A page that looks perfect but cannot complete its job is not tested.

Keep a simple log with the device, browser, page, what you saw and who is fixing it. A spreadsheet is enough. It turns vague worries into a list a developer can work through, and it forms part of the handover record described in our guide to website documentation to ask a developer to hand over.

What breaks most often?

The same few problems turn up repeatedly, so check them first.

  • Navigation menus that do not open, or open and cannot be closed, on a touch screen.
  • Forms that submit on one browser and fail silently on another, or whose fields are hidden behind the on-screen keyboard.
  • Text that overflows a button or a card on a narrow screen, particularly with longer translations or larger text settings.
  • Images that are stretched, cropped badly or far too large for a phone connection.
  • Fixed headers and banners that cover content, or cookie notices that cover buttons.
  • Fonts that fail to load and fall back to a different face, changing the layout.
  • Embedded maps, videos and booking widgets that do not resize.
  • Anything that relies on hovering, which touch devices cannot do.
  • Pop-ups that cannot be dismissed on a small screen.

Checkout and payment steps deserve special attention because the cost of failure is direct. Test them on at least one phone browser and one desktop browser every time they change. Third-party tools such as payment forms and chat widgets are common sources of surprises, since their behaviour is outside your site's own code and can change without notice.

Also look at speed on a phone. A page that is quick on a fast office connection can feel slow on mobile data. Speed tools can help, and checking the site on a real phone over a mobile connection tells you more than any score.

When to test, and how to fix what you find

Test at three points: during the build, once the design is complete and again just before launch. Testing only at the end leaves no time to fix real problems. Testing during the build lets you catch a design choice that fails on small screens while it is still cheap to change.

When you find a problem, report it in a form that a developer can act on. State the page address, the device and browser, the steps that led to the problem and a screenshot. Say what you expected to happen. Vague reports such as it looks wrong on my phone cost time on both sides.

Decide in advance what counts as a blocker. A checkout that fails on a main browser stops a launch. A two-pixel difference in spacing does not. Agreeing the line early prevents long discussions late in the project. Some fixes may carry a risk of breaking something else, so retest the areas around any change.

After launch, keep an eye on real use. Your analytics can show errors and drop-offs by browser, and customers will tell you what is wrong if you make it easy to do so. If you want a team to run through testing as part of a build, the website development service at Liftup Technologies includes it in the process, and it pays to ask any supplier what they test and how.

Testing and the rest of your launch

Browser testing sits alongside other launch tasks, not above them. Names, claims and wording on the page also need checking before launch, and for a new brand that includes whether the name is free to use, as covered in our guide to trademark basics for new brands. For legal questions, ask a qualified lawyer, because rules differ by country.

Once the site is live, set up something to tell you if it stops answering. Our guide to setting up uptime monitoring alerts explains what to check and who should be told. Testing finds problems before launch, and monitoring finds the ones that appear afterwards.

Related guides

Questions and answers

Which browsers should I test my website on?

Test the current versions of the main desktop browsers, the default browsers on iPhone and Android and a few screen sizes from small phone to wide monitor. If you have analytics, use them to choose, and add older versions only where real visitors use them.

How do I test my website without owning every device?

Combine the devices people in your business already own, the responsive mode in desktop browsers, a few friends or colleagues with different phones and, if needed, a cloud testing service. Real devices give the most reliable results for touch and mobile behaviour.

What breaks most often across browsers?

Mobile menus, forms, text that overflows on narrow screens, badly sized images, fixed banners that cover content, fonts that fail to load, embedded widgets and anything that depends on hovering. Checkout and payment steps need extra care because failures cost sales.

Is the browser responsive mode good enough?

It is a useful first check for layout at different widths, but it does not reproduce real touch, fonts or keyboards. Treat it as a quick screen, then confirm on at least one real phone and one tablet.

Do I need to support old browsers?

Only if your visitors use them. Check your analytics, or ask your developer to agree a support list based on the audience you expect. Supporting very old versions can add cost and limit what the site can do.

When should cross browser testing happen?

During the build, when the design is complete and again before launch. Early testing catches design choices that fail on small screens while they are cheap to change, and final testing confirms nothing broke in between.

Tell us what you are building.

A short call, a written plan and a fixed quote. No obligation.

Get a free quote