<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Web applications: &amp;quot;Visually complete&amp;quot; and &amp;quot;Speed index&amp;quot; metrics are not shown in Troubleshooting</title>
    <link>https://community.dynatrace.com/t5/Troubleshooting/Web-applications-quot-Visually-complete-quot-and-quot-Speed/ta-p/235261</link>
    <description>&lt;P&gt;When the &lt;A href="https://docs.dynatrace.com/docs/shortlink/visually-complete-speed-index-calculations" target="_self"&gt;"Visually complete" and "Speed index"&lt;/A&gt; metrics are not shown for your web application, check the following.&lt;/P&gt;
&lt;UL class="sc-jEACwC hZeaxZ"&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;
&lt;P class="sc-gEvEer lcacrh" data-testid="text"&gt;Ensure that Visually complete is the key performance metric used for XHR and load actions.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;Confirm support for your browser. Speed index and Visually complete metrics are only available on browsers that support&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="sc-gsFSXq dMCrLH sc-2d500c67-0 sc-68987768-1 gPHVzu bsktS" href="https://developers.google.com/web/updates/2012/02/Detect-DOM-changes-with-Mutation-Observers" target="_blank" rel="noopener noreferrer" data-testid="external-link"&gt;mutation observers&lt;/A&gt;. The following browsers are supported:
&lt;DIV class="sc-6646062a-0 ivCgmd"&gt;
&lt;UL class="sc-jEACwC hZeaxZ"&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;
&lt;P class="sc-gEvEer lcacrh" data-testid="text"&gt;Microsoft Internet Explorer 11&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;
&lt;P class="sc-gEvEer lcacrh" data-testid="text"&gt;Microsoft Edge 15 or later&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;
&lt;P class="sc-gEvEer lcacrh" data-testid="text"&gt;Firefox 57 or later&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;
&lt;P class="sc-gEvEer lcacrh" data-testid="text"&gt;Google Chrome 61 or later&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;
&lt;P class="sc-gEvEer lcacrh" data-testid="text"&gt;Safari is not supported because it does not support resource timings.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;Check the JavaScript injection point. Visually complete and Speed index metrics can't be calculated if the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="sc-iGgWBj bKeKTL sc-68987768-0 eSCioX" title="Learn the monitoring capabilities of OneAgent." href="https://docs.dynatrace.com/docs/shortlink/oneagent" target="_self" data-testid="link"&gt;RUM JavaScript&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;isn't inserted at a location within the HTML of your application pages where it can reliably get the mutation observer listeners in place. The RUM JavaScript execution occurring too late to get mutation observer listeners in place happens mainly when using Tag Manager. Known triggers that will stop Dynatrace RUM from capturing Visually complete timing measurements:&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Interrupted by user&lt;/STRONG&gt;: When your user interacted with your page during the initial Visually complete timing calculation and by that interrupted it.&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Forced by user before load&lt;/STRONG&gt;: When your user left the side before the browser fired the onload event.&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Forced by user after load&lt;/STRONG&gt;: When your user left your page after the browser fired the onload event but the Visually complete calculation has not yet started.&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Hard timeout met&lt;/STRONG&gt;: When the Visually complete timing calculation exceeded the hard timeout of 3 minutes.&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Thu, 22 Feb 2024 10:34:03 GMT</pubDate>
    <dc:creator>maliborskaya</dc:creator>
    <dc:date>2024-02-22T10:34:03Z</dc:date>
    <item>
      <title>Web applications: "Visually complete" and "Speed index" metrics are not shown</title>
      <link>https://community.dynatrace.com/t5/Troubleshooting/Web-applications-quot-Visually-complete-quot-and-quot-Speed/ta-p/235261</link>
      <description>&lt;P&gt;When the &lt;A href="https://docs.dynatrace.com/docs/shortlink/visually-complete-speed-index-calculations" target="_self"&gt;"Visually complete" and "Speed index"&lt;/A&gt; metrics are not shown for your web application, check the following.&lt;/P&gt;
&lt;UL class="sc-jEACwC hZeaxZ"&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;
&lt;P class="sc-gEvEer lcacrh" data-testid="text"&gt;Ensure that Visually complete is the key performance metric used for XHR and load actions.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;Confirm support for your browser. Speed index and Visually complete metrics are only available on browsers that support&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="sc-gsFSXq dMCrLH sc-2d500c67-0 sc-68987768-1 gPHVzu bsktS" href="https://developers.google.com/web/updates/2012/02/Detect-DOM-changes-with-Mutation-Observers" target="_blank" rel="noopener noreferrer" data-testid="external-link"&gt;mutation observers&lt;/A&gt;. The following browsers are supported:
&lt;DIV class="sc-6646062a-0 ivCgmd"&gt;
&lt;UL class="sc-jEACwC hZeaxZ"&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;
&lt;P class="sc-gEvEer lcacrh" data-testid="text"&gt;Microsoft Internet Explorer 11&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;
&lt;P class="sc-gEvEer lcacrh" data-testid="text"&gt;Microsoft Edge 15 or later&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;
&lt;P class="sc-gEvEer lcacrh" data-testid="text"&gt;Firefox 57 or later&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;
&lt;P class="sc-gEvEer lcacrh" data-testid="text"&gt;Google Chrome 61 or later&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;
&lt;P class="sc-gEvEer lcacrh" data-testid="text"&gt;Safari is not supported because it does not support resource timings.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;Check the JavaScript injection point. Visually complete and Speed index metrics can't be calculated if the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="sc-iGgWBj bKeKTL sc-68987768-0 eSCioX" title="Learn the monitoring capabilities of OneAgent." href="https://docs.dynatrace.com/docs/shortlink/oneagent" target="_self" data-testid="link"&gt;RUM JavaScript&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;isn't inserted at a location within the HTML of your application pages where it can reliably get the mutation observer listeners in place. The RUM JavaScript execution occurring too late to get mutation observer listeners in place happens mainly when using Tag Manager. Known triggers that will stop Dynatrace RUM from capturing Visually complete timing measurements:&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Interrupted by user&lt;/STRONG&gt;: When your user interacted with your page during the initial Visually complete timing calculation and by that interrupted it.&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Forced by user before load&lt;/STRONG&gt;: When your user left the side before the browser fired the onload event.&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Forced by user after load&lt;/STRONG&gt;: When your user left your page after the browser fired the onload event but the Visually complete calculation has not yet started.&lt;/LI&gt;
&lt;LI class="sc-cPiKLX cTTNHO"&gt;&lt;STRONG class="sc-bf977b27-0 hNpJEd"&gt;Hard timeout met&lt;/STRONG&gt;: When the Visually complete timing calculation exceeded the hard timeout of 3 minutes.&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Thu, 22 Feb 2024 10:34:03 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Troubleshooting/Web-applications-quot-Visually-complete-quot-and-quot-Speed/ta-p/235261</guid>
      <dc:creator>maliborskaya</dc:creator>
      <dc:date>2024-02-22T10:34:03Z</dc:date>
    </item>
  </channel>
</rss>

