The number of file requests made to download assets during the initial load phase directly impacts ad performance, page load speed, and user experience. Reducing initial file requests can improve viewability and enhance overall performance.
Understanding Initial load and Remote load:
-
Hosted ads: Ads that are primarily hosted, with only essential files (e.g., tags or small scripts) served from the server. Any additional assets loaded externally will appear under "Remote Assets."
-
Fully remote ads: Ads where all assets are served remotely, and only the tag is hosted.
-
Mixed-load ads: Ads that combine hosted and remote elements, like an HTML index file with additional assets loaded from external sources.
In order to minimise the number of Initial file requests, it is recommended to consolidate assets where possible and excluding redundant requests.
Initial file requests setting in Advalidation
When enabled, this test counts all hosted and remote file requests initiated during the initial load, with options to exclude certain items (e.g., cached JavaScript files) to refine the count.
You can set the Max requests number to match your specs and ensure good user experience.
Please note: You cannot set the Max request to 0. It must be set to a minimum of 1.
Advalidation's recommendation
We recommend using this setting in order to monitor and minimise the number of initial file requests, which will result in improved ad load speed and a better user experience.
You may also be interested in...
Display QA | Remote load - total load vs polite load
Comments
0 comments
Please sign in to leave a comment.