Client-side testing
Client-side testing modifies the content visible to the user via scripts executed in the browser.
A method that dynamically modifies the content displayed to the user via JavaScript scripts executed directly in their browser. This approach is ideal for quick tests on visual or textual elements, thanks to its great flexibility and simplified implementation, without any server-side code modification.
However, it can degrade site performance (loading time, visual stability), with a measurable impact on indicators such as First Contentful Paint (FCP), Largest Contentful Paint (LCP), Time to Interactive (TTI), Cumulative Layout Shift (CLS), or Total Blocking Time (TBT).
It is therefore advisable to reserve this method for temporary experiments, and then integrate the validated changes directly into the source code or on the server side.
Autres termes : A/B testing
View the full glossary- A/B TestingA/B(n) testing is a method that compares two or more versions of a web page, an application, an algorithm, advertising banners, etc., to determine which performs best.A/B testing
- AA TestA type of test where two groups receive the same experience to ensure that the testing system is reliable and that observed differences are not due to chance.A/B testing
- DatalayerA data structure used to transmit information between a website and a tag management tool.A/B testing
- Feature FlaggingA technique for enabling or disabling features remotely without deploying new code.A/B testing
- Feature RolloutThe progressive rollout of a new feature to a subset of users before a full launch.A/B testing
- Test hypothesisA test hypothesis is a statement formulated to predict the outcome of a specific change on a website or application as part of an optimization process.A/B testing