All Collections
CMS
Pinpoll vs. CLS
Pinpoll vs. CLS

We explain how Pinpoll deals with the much-noticed "Cumulative Layout Shift" (CLS).

Theresa Kirchner avatar
Written by Theresa Kirchner
Updated over a week ago

Customers ask us often, "Does Pinpoll cause a Cumulative Layout Shift?"

The short answer: Yes, just like any element that is loaded asynchronously by the browser.

This is even more the case with Pinpoll, as elements are only requested according to the "lazy loading" principle when the element actually appears in the viewing area of the website visitor - this increases performance and saves costs.

Nevertheless, there are ways to avoid a shift. We recommend these two options to our customers:

  1. Insert placeholder in height of 250 px

  2. Embed elements natively

Option 1: Insert placeholder in height of 250 px

The elements of the Pinpoll are on average approx. 200 px high. As is usual for advertising positions, a placeholder can be provided for Pinpoll, which is replaced as soon as the element is loaded. This avoids the shift completely for elements up to 250 px high.

Option 2: Embed elements natively

We have recently added the option to embed elements natively. This means that no iFrame is used and the height of the element is therefore already fixed at load time, which completely avoids a shift.

Native integration is also good for SEO and CI, as the CSS of the website is also applied to the Pinpoll-element.

However, we do not want to conceal one catch: Changes to the Pinpoll-elements always require an update of the embed code in the client's CMS. In addition, not all options are supported by the native embed.

Our technicians accompany all customers during the initial setup, which ensures ideal integration.

Any questions? Feel free to write us directly in the chat โ†˜๏ธ

Did this answer your question?