Prisjakt's HTML5 guideline caps average CPU usage at 30% and peak usage at 60%. That page sets a 15-request ceiling, a 30-second animation limit, and a black 1px border. Its test rig is fixed at a 1.5GHz processor, 920MB of RAM, and the latest Google Chrome.

Constraint falls on the creative producer, not on the shopper. The document proves only that a creative will be rejected if it exceeds those thresholds on the simulated rig; it does not prove that any submitted banner will pass. For the buyer, the useful number is the 1.5GHz/920MB rig, because it defines the approval environment before the ad reaches a real device.

No measured creative value appears in the document, so no measurement sits inside the limit. It names the continuous CPU and RAM measurement process, but it gives no average, peak, request count, or animation duration for a specific ad. Until a producer submits a file and Prisjakt returns a test result, the standing note can only hold the limit, not a pass or fail; the missing figure is not a defect in the page, but the normal state of a pre-approval spec.

The document does not give a measured CPU, RAM, request, or animation value for any specific creative.

Producers must fit the creative under 15 requests, 30% average CPU, 60% peak CPU, and 30 seconds of animation on a 1.5GHz/920MB Chrome rig. The spec defines the approval boundary, but it does not provide a measured pass for any specific creative.