Skip to content
6 min read

Cross-Browser Testing: How to Make Sure Your Site Works for Everyone

Cross browser testing is the process of checking that a site works the same way across browsers, devices and screen sizes. A site that looks perfect on the developer's MacBook can break on a budget Android phone with an outdated browser, or inside Telegram's in-app window. If your lead form fails for some visitors, you lose enquiries and never find out: the person simply closes the tab.

What cross browser testing is and why layouts break

Browsers are built on different engines: Chrome and Edge use Blink, Safari uses WebKit, Firefox uses Gecko. Each engine adopts new CSS and JavaScript features at its own pace and handles imprecise code in its own way. What one engine forgives, another renders wrong or not at all.

Safari on iPhone is a case of its own. On iPhone, browsers including Chrome run on the WebKit engine by default, so Safari quirks affect every iPhone owner. It behaves differently around viewport height, form fields, video and floating toolbars, and most 'everything has shifted' complaints come from there.

The second cause is hardware. Budget Android phones with little memory and a browser that was never updated struggle with animations, large images and heavy scripts. The site may not break, but it can load so slowly that the visitor leaves.

What to test in Uzbekistan

Start from data, not guesses. Open the technology report in Google Analytics or Yandex Metrica: browsers, operating systems, screen resolutions. You need to test what your visitors actually use, not a generic list from the internet.

A practical minimum for Uzbekistan: current Chrome on Android; Safari across several iPhone generations, including older models; Chrome plus one alternative browser (Edge, Firefox or Safari) on desktop; and Telegram's in-app browser. The last one matters a lot: many people arrive through links in chats and channels, and that window is not an ordinary tab. Cookies, third-party sign-in and file downloads may behave differently there.

On every device, check three screen sizes: a narrow phone (around 360 pixels wide), a large phone or tablet, and a laptop. Do not skip landscape orientation either.

A step-by-step test plan on a small budget

Step 1. The device mode in Chrome DevTools. It quickly reveals layout and responsiveness problems, but it does not reproduce engine differences, so treat it as the first level only. While you are there, throttle the network to Slow 4G and see how the site loads on a poor connection.

Step 2. Real phones. Gather five different devices in the office: two Android phones from different price classes, two iPhones from different years and one tablet. Ask colleagues to walk through real scenarios: find a product, submit a request, open the site from Telegram.

Step 3. Cloud services with real devices are useful when you must check a specific OS or browser version. As a rough guide, a subscription costs from 400,000 to 1,500,000 UZS per month, but for a single site a short paid period around the release is usually enough.

Step 4. Check caniuse.com. If you use a recent CSS or JavaScript feature, it shows which browser versions support it and whether you need a fallback.

What breaks most often: a checklist

Horizontal scrolling caused by an element wider than the screen: open the page on a narrow phone and try swiping sideways. If the page moves, somewhere there is a fixed-width block, a long unbroken word or an image with no size limit.

Form fields: on iPhone, focusing a field with a font size under 16 pixels zooms the page and shifts the layout. Also check the phone mask, the keyboard type for numbers and e-mail, and the submit button, which the on-screen keyboard must not cover.

Viewport height: a 100vh block in mobile Safari gets cut off by the address bar. Use dvh or svh units with a fallback value. The same list includes custom dropdowns, overlapping layers that make buttons unclickable, and fonts or icons that failed to load because an external resource was blocked.

Autoplaying video: policies differ, and where a background video plays on desktop, a phone may show a black rectangle. Add the muted and playsinline attributes and always set a poster frame as a fallback.

How long it takes and what it costs

An initial check of a small site (a landing page or a 5–10 page business site) takes roughly one to two working days if the scenarios are written down in advance. For an online store or a site with a personal account, plan three to five days: there are more scenarios and each one has to be run on several devices. This is a rough guide, not a guarantee.

If an outside specialist does the check, the market guide is from 500,000 to 3,000,000 UZS depending on the size of the site and the number of devices. This is an approximate range; the exact figure is given after the project is reviewed. The cheapest approach is to build testing into development rather than fix complaints after launch.

Make a table: scenarios in rows (home page, catalogue, form, payment), devices in columns. Record the result and the browser version. You will reuse this table every time the site is updated.

FAQ

Do I need to support very old browsers? Not always. Decide from analytics: if the share of an old version among your audience is small, it is enough that the site stays readable and the form works, even without animations.

Why does my site not work in Safari when Chrome is fine? Most often the cause is a newer CSS or JavaScript feature that Safari adopted later, viewport height, or video autoplay rules. Connect an iPhone to a Mac and inspect errors with Safari's web inspector.

Is Chrome's device mode enough? No. It imitates the screen size, but not the engine or the quirks of a real device. At a minimum, add a few real phones.

How often should I repeat testing? After every noticeable change: a new block, a form, a payment module update. Also once every few months, because browsers keep updating.

Next step

If you want a site that has been checked in the main browsers and in Telegram's in-app window before launch, 4 Digital builds turnkey websites starting from 1,399,000 UZS. Before launch we run the key scenarios on different devices. Get in touch and we will discuss the task and timing.

Need a website or ads? Let’s discuss your project.

Turnkey Website Development + CRM · от 2 399000 сум

We reply within 15 minutes during business hours. No spam.