cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Ruxitagent content download on mobile devices

felicianoangelo
Visitor

Hi Community,

I wanted to ask about the data shown in the screenshot below. As you can see, the loading time for the Ruxitagent is 2.9 seconds. I’m not sure if this is typical when running the application on mobile devices. Could you help identify what might be causing this issue? Additionally, could you clarify whether this is related to Dynatrace or if it could be a server-side problem?

Thank you!

felicianoangelo_1-1733384518184.png

 

3 REPLIES 3

Peter_Youssef
Leader

Hi @felicianoangelo 

Concerning the Largest Contentful Paint (LCP) kindly find the below comment:

  • It's a key performance metric that measures the time it takes for the largest visible content element (e.g., image, text block) on a webpage to load.
  • A long LCP can significantly impact user experience, and Dynatrace (via the Ruxit agent) can help identify and diagnose issues related to it.
  • If you're experiencing issues with LCP through Dynatrace Ruxit agent, here are the steps to help address and fix the problem:
  1. Identify LCP Element Using Dynatrace

Dynatrace's Ruxit agent tracks performance data, including LCP.

For LCP issues diagnosis :

  • Access Real User Monitoring (RUM) in Dynatrace: RUM provides detailed data about your website’s performance from actual user sessions.
  • Locate LCP Data: Look for LCP information within the RUM dashboard. You can find the "Largest Contentful Paint" metric under the page performance section or the “Web” performance monitoring data.
  • Analyze the Problematic Pages: Identify which specific page or element is responsible for the slow LCP.

LCP Element Optimization:

Once you identify the element that contributes to the LCP issue, the next step is to optimize it. Common elements that contribute to LCP issues include images, videos, or large text blocks.

For Images:

  • Image Optimization: Ensure that images are properly optimized in terms of size and format (e.g., using WebP or responsive images).
  • Lazy Loading: Implement lazy loading for images that are not immediately visible on the page.
  • Serve Images in Proper Dimensions: Ensure images are not unnecessarily large for the viewport size.

For Fonts:

  • Font Loading: Avoid render-blocking fonts. Use font-display: swap to ensure text remains visible while fonts are loading.

For CSS/JS:

  • Critical CSS: Minimize the critical CSS and load non-essential styles asynchronously.
  • JavaScript Optimizations: Avoid long-running scripts that block the main thread during page load. Defer or async non-critical scripts.
  1. Check for Server or Network Issues
  • Server Response Time: A slow server response time can increase the time it takes to load the page. Dynatrace can help identify backend performance issues (e.g., database queries, API calls).
  • CDN Optimization: If using a CDN, make sure it's properly configured to deliver content efficiently, especially for large files like images.
  1. Use Performance Budgets

Set performance budgets within Dynatrace for LCP to monitor and alert if the threshold is breached. This allows proactive management of LCP performance over time.

  1. Review the Loading Sequence

Dynatrace provides insights into how elements load on the page. Make sure that LCP elements are prioritized and loaded earlier. Avoid blocking resources like large images, fonts, or JavaScript that delay the display of the LCP element.

  1. Monitor After Implementing Changes

After applying optimizations, use Dynatrace to monitor the improvements in LCP. This can be done by tracking the performance in RUM and the LCP score over time to ensure the optimizations were effective.

  1. Common Causes of Poor LCP
  • Slow server response times
  • Large or unoptimized images
  • Render-blocking JavaScript or CSS
  • Slow font loading
  • Third-party scripts or heavy ads affecting load time

By identifying the LCP element and addressing its loading bottlenecks, you can improve both your user experience and your LCP score.

Conclusion:

  • The issue is a reason of any of the highlighted factors or combined which require optimization from development team, therefore it's not a Dynatrace agent.
  • Performing waterfall analysis and looking into the stack traces will help you pinpoint the Root Cause and proceed with the applicable remediation.

Hoping it helps.

KR,

Peter

Hi Peter,

Thank you for your input. However, my question specifically concerns the Dynatrace agent itself and why it takes a long time to load. We've observed that it takes approximately 2.97 seconds to load the ruxitagentjs on mobile browsers.

Our leading theory is that we’re using the "Latest IE7-10" version for the RUM JavaScript rather than the "Latest Stable" version. Could you please share your thoughts on what might be causing this delay?

Thank you for your time and insights.

Hi @felicianoangelo 

Appreciate your feedback, Regarding the highlighted point feel free to review the release notes, it might have a reason or resolution if such scenario is stated.

Peter_Youssef_0-1734674127439.png

Dynatrace Managed doc:

Mobile App ref:

If the highlighted error related to a hybrid app, the attached Ref hopefully will add value.

Tip:

Hoping it helps.

BR,

peter

 

 

Featured Posts