Excluding Third Party Resources in Transaction and Full Page Load Monitoring


Many web pages contain references to elements that are not actually hosted on that server. Each external request requires a number of extra elements to be loaded through your server and your browser, which can add significantly to your page load time. This requires a call to the host for that script whenever your page loads.

Even worse, what happens if a host is slow at some point or even unavailable then the browser will wait for an extended period of time to try to include that script. The end result is that your web page is extremely slow, and some page elements may not load properly. The more elements you have like this – images, PHP, Twitter feeds – the more your page slows down. The main problems that users address related to this kind of code are:

  • Slow page load times and timeouts
  • Unexpected javascript errors of various kinds
  • Failure to load some of your website content
  • False positives

To control the impact of third-party scripts, in Monitis Transaction and Full Page Load monitoring you can provide a list of URLs/domains to be excluded.


Creating the Third Party Resource Exception List

You can create the third party resource exclusion list from your Transaction or Full Page Load monitor’s settings.

C:\Users\veghiaza\Desktop\zara final.png

Go to the Excluded Resources tab and add the URL patterns you want.

URL pattern can be any string.

If you enter duplicate URLs, you will see the “You have already entered this URL pattern” error message.

You can use wildcard when specifying the URL pattern. By using the asterisk * character dynamic patterns are created and URLs/domains matching them will be excluded as well. The * character is interpreted as the .* regular expression meaning zero or more occurrences of any symbol.

By default, the plain text that you enter is treated as a regular expression, meaning that the matching patterns include also the entered pattern preceded or followed by any text.

For example, if you enter example.com then the below listed will also match the pattern:

  • one.example.com
  • example.com/one
Note that HTTPS resources also can be excluded.