With Script Management enabled and your Ion property delivering your site or app to end-users, mPulse will have had some time to gather real-user monitoring data regarding script usage. Use Script Management tools to review this data.

The Script Management API

Review "insight" information on how Script Management is handling the scripts used on your site or app.

Get insights

Open Recipe

You want to identify scripts that are negatively impacting your site. In the production array results, locate script entries with an analysis value of HIGH, review the analysisReason, and store these values:

script. This is the URL for the offending script. You'll use it to build a policy to manage the script to either block or defer it.
testingSuggestions. These are the pages where this script is currently in use. After you build your policy, you'll access these pages to test.

Here's an example of the response:

{
  "staging": [ ],
  "production": [
    {
      "category": "Miscellaneous",
      "group": "docsassociates.com",
      "script": "https://docsassociates.com/edge-demo/block.php.js",
      "party": "THIRD_PARTY",
      "spof": false,
      "recentPopularityPercentage": 1,
      "minPopularityPercentage": 1,
      "avgPopularityPercentage": 1,
      "maxPopularityPercentage": 2,
      "recentTransferSizeBytes": 487,
      "minTransferSizeBytes": 461,
      "avgTransferSizeBytes": 476,
      "maxTransferSizeBytes": 514,
      "recentTransferTimeMs": 10285,
      "minTransferTimeMs": 9654,
      "avgTransferTimeMs": 10336,
      "maxTransferTimeMs": 10914,
      "analysis": "HIGH",
      "action": "",
      "analysisReason": "Slow transfer time (>1000 ms)",
      "testingSuggestions": [
        "https://docsassociates.com/projects.html"
      ]
    }
  ]
}

👍
Consider repeating this process for the MEDIUM entries, too. You should at least review the analysisReason to see how they might be impacting your site.

The Script Management dashboard

Here's how to use the Script Management dashboard to review this data to determine which scripts may be problematic on your site or app.

In Control Center, go to ☰ > CDN > Script Management.
Set the following:
- Group. Select the Group ID you used to create your Ion property.
- Property. Select your Ion property name.
- Hostname. Select the appropriate Property Hostname. This is the unique name you used for the association between the domain clients use to request your site or app, and the edge hostname Akamai created, that redirects those requests to the edge network.

Review the information shown on the Script Management Dashboard.

When reviewing the Dashboard, consider these key options and points of information:

Option	Details
Analysis	The mPulse beacon data is analyzed and the overall number of scripts used is categorized based on the level of impact they're having on your site. If you have any "High" entries, you'll want to make note of these scripts to create a policy to defer or block them. 🚧 Know what your scripts do Script Management's analysis only accounts for performance, not functionality. If a script runs critical functionality on your site, you probably don't want to block or defer it, even if the analysis indicates that it substantially slows page loading.
View	Select how you want scripts displayed in the table: Scripts. This lists scripts independently. This view offers detailed metrics and other information for each script by clicking the information button. Groups. You can use this to group your third-party scripts based on common functionality. You'll need to manually define a group for one script and then include similar scripts in that same group.
Filters	Select one or more ways to filter the scripts displayed in the table: First party. This refers to a script that's accessed via the same domain as your website or app. (This would be the domain you used in your Property Hostname to generate its edge hostname.) Third party. This refers to a script that's accessed from a domain outside of your website or app.

Option

Details

Analysis

The mPulse beacon data is analyzed and the overall number of scripts used is categorized based on the level of impact they're having on your site. If you have any "High" entries, you'll want to make note of these scripts to create a policy to defer or block them.

🚧
Know what your scripts do
Script Management's analysis only accounts for performance, not functionality. If a script runs critical functionality on your site, you probably don't want to block or defer it, even if the analysis indicates that it substantially slows page loading.

View

Select how you want scripts displayed in the table:

Scripts. This lists scripts independently. This view offers detailed metrics and other information for each script by clicking the information button.
Groups. You can use this to group your third-party scripts based on common functionality. You'll need to manually define a group for one script and then include similar scripts in that same group.

Filters

Select one or more ways to filter the scripts displayed in the table:

First party. This refers to a script that's accessed via the same domain as your website or app. (This would be the domain you used in your Property Hostname to generate its edge hostname.)
Third party. This refers to a script that's accessed from a domain outside of your website or app.

👍
For additional details on the options and information in the Script Management Dashboard, have a look at the Dashboard metrics reference.

The Script Management API

👍

The Script Management dashboard

🚧Know what your scripts do

👍

🚧
Know what your scripts do