Source
Snippet performance & flicker — found from sitemap — Contentsquare
Checked for Contentsquare on 2 Nov 2026
- Page
- https://docs.contentsquare.com/en/web/impact-on-performance/
- Checked
- 2 Nov 2026, 04:37 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:e2e30d0e2415e146dba4012326a85c587637f68c0e95569cbf4d7cb148978065
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Tag compressed size Report an error
“The standard version of the Contentsquare tag is compressed to 3.2 KB, and transferred from the Contentsquare CDN to the browser, compressed by gzip.”
-
Tag structure Report an error
“The Contentsquare tag loads as two files: a small project-specific loader and a shared tag runtime.”
-
Loader cache duration Report an error
“The small project-specific loader is cached locally on a customer's browser for 15 minutes.”
-
Runtime caching Report an error
“The tag runtime is a static file that never changes once published. A new tag version is published at a new URL, so browsers can keep the runtime in cache much longer than a regular script, and a settings change in your project doesn't invalidate it.”
-
Recommended placement Report an error
“Our recommended approach is to put the tag in the <head> element of your HTML page, with a defer attribute; this will make the browser download the tag asynchronously while it continues to parse the HTML, and once the DOM is ready, it will run the tag.”
-
Paint metrics unaffected Report an error
“This also means the Contentsquare tag should never impact any "paint" metrics, such as Time to First Byte (TTFB), First Contentful Paint (FCP) or Largest Contentful Paint (LCP).”
-
Tbt impact examples Report an error
“Desktop device with good processing power, good broadband connection, modern browser - the tag would have an impact of between 0ms and 50ms. Mobile device with average processing power, 4G connection, modern browser - the tag would have an impact of between 25ms and 100ms.”
-
Core web vitals affected Report an error
“The only Core Web Vital that would be affected by the Contentsquare tag is First Input Delay.”
-
Metrics impact table Report an error
“Metric Name Impacted by CS Tag? Time to First Byte (TTFB) No First Meaningful Paint (FMP) No Largest Contentful Paint (LCP) No Speed Index No Cumulative Layout Shift (CLS) No Time to Interactive (TTI) Yes Total Blocking Time (TBT) Yes Interaction to Next Paint (INP) Yes”
-
Request behavior Report an error
“If Session Replay is live, then there will be several requests made as the customer navigates around the website. These are batched up and sent as small HTTP POST or GET requests.”
-
Error capture requests Report an error
“Additionally, if the tag is also enabled for capturing errors, then this will trigger a new request per error occurrence on the page.”
-
Request size Report an error
“The requests posted to Contentsquare's API vary depending on the information sent. However, the majority are tiny, typically under 500 bytes.”
-
Dom node threshold Report an error
“The Document Object Model (DOM) being large, over 2000 nodes”
Scores citing this record
- The CRO Consultant Snippet performance & flicker
- The CRO Consultant Snippet performance & flicker
- The CRO Consultant Snippet performance & flicker
- The Data Protection Officer Snippet performance & flicker
- The E-Commerce Manager Snippet performance & flicker
- The E-Commerce Manager Snippet performance & flicker
- The E-Commerce Manager Snippet performance & flicker
- The Growth Lead Snippet performance & flicker
- The Growth Lead Snippet performance & flicker
- The Growth Lead Snippet performance & flicker
- The Product Engineer Snippet performance & flicker
- The Product Engineer Snippet performance & flicker
- The Skeptic Snippet performance & flicker
- The Skeptic Snippet performance & flicker
- The Skeptic Snippet performance & flicker