Skip to main content

Fix issues due to high URL resolution time

Learn to fix issues in test performance due to high URL resolution time on BrowserStack.

Issue

When you run a test using BrowserStack Automate, the following warning might appear on the Issues Detected tab in the Automate dashboard.

URLs in the session took too long to resolve

Note: This page provides information to help you resolve high URL resolution time if it is a concern. Sometimes applications are designed such that high URL resolution time is an expected scenario. If you are aware of this issue and it is intentional, you can ignore the suggested resolutions.

Cause

At a given time, multiple tests are run on BrowserStack. Since we handle diverse test scenarios from various customers, it gives us a better understanding of how the optimum page load performance compares to other tests run on the platform. Based on this understanding, we generate the warning to alert you that the time taken for your page to load/URLs to resolve is higher than 75 percentile of all users that use BrowserStack.

Some of the causes for this warning are:

  • Page includes heavy UI compoenents, such as bloated scripts, unoptimized images, and so on.
  • Application server unable to handle resources in multi-threaded tests.

Why you must mitigate this issue

As an organization, optimizing your builds to run faster, is crucial. BrowserStack understands the need to identify issues that might not be evident, but have a large impact on the speed and stability of your test sessions.

Use the resolutions provided to mitigate these issues so as to:

  • Improve performance
  • Reduce test flakiness

Resolution/Workaround

Optimize page load time using SpeedLab reports

BrowserStack provides a website speed test tool, SpeedLab, that can help you calculate key metrics such as TTFB, Response time, Page load time, and so on. Using these metrics, you can identify performance bottlenecks and take corrective actions .

Check out SpeedLab to learn how your page performs on different device/OS-browser combinations.

Other resolutions

You can also try the following options to resolve this issue:

  • Check your page to identify heavy UI components and reconsider the design.
  • Invest in a resource-intensive application server that can handle multi-threaded tests better.

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback

Is this page helping you?

Yes
No

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback!

Talk to an Expert
Talk to an Expert