diff --git a/docs/how_tos/integrating-external-services.rst b/docs/how_tos/integrating-external-services.rst
index f3c428a12..db36a47b8 100644
--- a/docs/how_tos/integrating-external-services.rst
+++ b/docs/how_tos/integrating-external-services.rst
@@ -97,3 +97,10 @@ By default, ``useComponentPropOverrides`` and ``withComponentPropOverrides`` sup
     });
     return <span {...propOverrides}>{children}</span>;
   });
+
+Performance considerations
+***********************
+
+Performance implications should be considered while integrating with other services.Any third-party, external vendor scripts (e.g., Segment, Google Analytics, Datadog, etc.) loaded via a service class (e.g., ``SegmentAnalyticsService``, ``externalScripts``) are injecting ``<script>`` tags into the HTML document *after* much of the MFE's application code has been downloaded/parsed. That is, all JS needed for frontend-platform's MFE initialization must be downloaded/evaluated first *before* downloading any external scripts.
+
+The default/base ``NewRelicLoggingService`` is currently an exception in that it injects the New Relic JS `<script>` tag during the Webpack build process via ``HtmlWebpackNewRelicPlugin``, whereby the New Relic `<script>` may be downloaded earlier in the initial page load, without being blocked on parsing frontend-platform's JS. In a similar vein, many MFEs integrate with Optimizely by hardcoding its associated ``<script>`` element in the ``public/index.html`` file for the MFE (not open-source friendly).