ContextHub flickering the screen | Community
Skip to main content
Level 2
Feb 14, 2019 5:33 PM UTC
Solved

ContextHub flickering the screen

Hi, we are trying to use ContextHub to implement personalisation (segmentation) on our website.

We were able to implement it correctly. Everything is OK, but in some computers, we don't know why, the screen flickers before displaying the final content.

In some computers:

a) First, it displays the Default content (without segmentation applied).

b) Then, after 1 second, the screen changes completely to match the segmentation.

Anyones knows why this is happening? We want to see the final content with segmentation applied without the page flickering.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Gaurav-Behl
Gaurav-BehlAccepted solution
Level 10
Feb 14, 2019 7:11 PM UTC

Not sure but that could be because of network/machine related issues that the libraries take time to load & process. For the m/c where you notice the error, do they have local AEM or they use the same remote/cloud AEM server?

Couple of pointers to debug:

  • Check the page load time in network tab of developer toolbar or even in 'Developer' mode or use a plugin
  • Look for any errors/warnings in the console tab of developer toolbar or server logs
  • Try to find a pattern based on OS/Browser/network/memory/cpu combination

3 replies

Gaurav-Behl
Level 10
Feb 14, 2019 7:54 PM UTC

very likely but proxy would have same impact on all m/c, its sort of a combination of multiple reasons..

Translate
Level 2
Feb 14, 2019 7:37 PM UTC

I am really working in a very restricted network environment, where we have a strong proxy with lots of blocked websites and strict monitoring of information.

It may be that our proxy is slowing down the loading of some scripts. But I am not sure yet what is the root of the problem.

Translate
Gaurav-Behl
Gaurav-BehlAccepted solution
Level 10
Feb 14, 2019 7:11 PM UTC

Not sure but that could be because of network/machine related issues that the libraries take time to load & process. For the m/c where you notice the error, do they have local AEM or they use the same remote/cloud AEM server?

Couple of pointers to debug:

  • Check the page load time in network tab of developer toolbar or even in 'Developer' mode or use a plugin
  • Look for any errors/warnings in the console tab of developer toolbar or server logs
  • Try to find a pattern based on OS/Browser/network/memory/cpu combination
Translate