Validate and Test creative zip files for HTML5 display Ads

Validates that a valid entry HTML file exists

Verifies the creative has a primary HTML file that serves as the entry point. Ad servers need to know which HTML file to load first. The system looks for 'index.html' first, then falls back to a single .html file, or the first alphabetically.

Detects creative dimensions from HTML markup

Attempts to detect the creative's width and height by scanning HTML attributes (width="300"), inline styles (style="width: 300px"), CSS rules, aspect-ratio properties, and JavaScript object literals. Knowing the dimensions helps with trafficking and ensures proper rendering.

Validates that the total ZIP file size is within acceptable limits

Validates the total uncompressed size of all files in the creative. Large file sizes can impact load times and may exceed ad platform serving limits. Most platforms recommend keeping creatives under 5-10 MB.

Validates that the ZIP contains a reasonable number of files

Checks the number of files in the creative package. An excessive number of files can slow down processing, increase load times, and may indicate poor organization or unnecessary assets.

Validates that individual files are not excessively large

Validates that no single file is excessively large. Large individual files (especially images or videos) can cause significant performance issues and may fail to load on slower connections. Consider optimizing or compressing large assets.

Validates compression ratio to detect potential zip bombs

Detects potential zip bombs by analyzing the compression ratio. A zip bomb is a malicious archive that expands to an enormous size when decompressed, potentially exhausting system resources. Normal compression ratios are typically under 10:1.

Validates that all files have allowed extensions

Checks that all files use standard web-safe file extensions. Ad platforms typically only support common web formats (HTML, CSS, JS, images, fonts, video). Unsupported file types may be rejected or fail to load properly.

Validates that directory structure is not excessively nested

Validates directory structure complexity. Deeply nested folders can cause path length issues on some platforms, complicate maintenance, and indicate poor organization. Keep your creative structure simple and flat when possible.

Validates file naming conventions (no spaces, special characters)

Ensures file names use only web-safe characters (alphanumeric, hyphens, underscores). Spaces and special characters in file names can cause issues with URL encoding, server configurations, and cross-platform compatibility.

Validates image asset usage and sizing

Provides an inventory of image assets and their total size. Images are often the largest assets in display ads. Consider using modern formats (WebP), appropriate compression, and serving different sizes for different screens to optimize performance.

Validates JavaScript asset inventory

Catalogs JavaScript files and their combined size. JavaScript is executed by the browser and can impact ad performance. Large or numerous script files may slow down ad rendering and user interaction.

Validates stylesheet asset inventory

Lists CSS files and their total size. Stylesheets control the visual presentation of your ad. Multiple or large CSS files can delay rendering as browsers must download and parse them before displaying content.

Validates video asset sizing

Checks video file sizes. Video ads are typically the largest assets and require careful optimization. Large video files consume significant bandwidth and may not load on slower connections. Consider using streaming or external hosting for large videos.

Validates basic HTML structure and syntax

Performs basic HTML validation checks including proper tag structure, required elements (html, head, body), and common syntax errors. Valid HTML ensures consistent rendering across different browsers and ad platforms.

Validates presence of important meta tags

Checks for essential meta tags like charset (UTF-8) and viewport settings. These tags ensure proper character encoding and responsive behavior across different devices and screen sizes.

Validates inline script size limits

Checks the total size of inline JavaScript code embedded directly in HTML. Large inline scripts can slow down page parsing and should generally be moved to external files for better caching and performance.

Inventories external resource dependencies

Identifies all external resources (URLs) referenced in the creative. External dependencies create additional network requests and potential points of failure. Each external resource should be evaluated for necessity and performance impact.

Checks if JavaScript files appear to be minified

Detects whether JavaScript files are minified by analyzing line length patterns. Minification removes whitespace, comments, and shortens variable names, significantly reducing file size. Unminified code wastes bandwidth and exposes your implementation details.

Detects console.log and debug statements

Scans for console.log, console.debug, and similar debugging statements. These should be removed from production code as they can leak information, impact performance, and create unnecessary browser console noise. Use a build process to strip debug code.

Checks if JavaScript uses strict mode

Checks for 'use strict' directive in JavaScript files. Strict mode catches common coding errors, prevents unsafe actions, and disables confusing features. It's a best practice that helps avoid bugs and makes code more maintainable.

Checks for error handling patterns

Looks for try-catch error handling blocks in JavaScript. Proper error handling prevents your ad from breaking when unexpected conditions occur, provides graceful degradation, and helps with debugging issues in production.

Validates clickTag implementation for ad serving

Validates presence of clickTag implementation. ClickTags allow ad servers to dynamically insert destination URLs without modifying the creative file. This is essential for trafficking the same creative to multiple destinations and is required by most ad platforms.

Validates OMID (Open Measurement) implementation

Checks for Open Measurement SDK (OMID/OMSDK) implementation. OMID is an IAB standard that enables consistent viewability and verification measurement across different vendors. Many premium publishers and DSPs require or prefer OMID-compliant creatives.

Validates restricted vendor compliance

Validates compliance with vendor restrictions. Some platforms and publishers block specific third-party vendors due to privacy policies, competitive restrictions, or performance concerns. Using restricted vendors will cause your ad to be rejected.

Validates third-party script usage

Catalogs external JavaScript resources loaded from third-party domains. Each external script adds a network request and potential point of failure. Excessive third-party scripts can slow down your ad, create security risks, and may be restricted by ad platforms.