Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
  • #522003


    When my page loads initially, the search box pops up just for a second. Is there any way I can avoid this behaviour? It doesn’t really look professional, as it attracts the user’s attention and it’ll be the first thing they see. It seems more like a bug.

    The site:

    Thanks for great support


    Hey Emilvillumsen!

    are you using any cache plugin to the site?
    Any CDN service?

    Best regards,


    Yep, Supercache is installed and trying out W3 Cache at the moment. The behaviour appeared before W3 though.

    Also a CDN, yes; Amazon Web Services S3 and Cloudfront.



    Please try this in the Quick CSS field:

    .avia-search-tooltip {
        opacity: 0;

    Cool website. :)



    Nope, doesn’t work sadly. Still pops for half a second.

    This is the custom css (child theme) I have on the search field. But tried inserting it in Enfold custom CSS as well. Didn’t work.

    .avia-search-tooltip { /* wider search field */
        width: 400px;
        border-bottom: none;
        opacity: 0;
    #top #searchform>div {
        max-width: none;
    @media only screen and (max-width: 989px) { /* helps search icon appear on mobile in hamburger menu. Found it on kreisi support */
        #top #searchform>div {
            display: block !important;
            opacity: 1 !important;  
            padding: 0 1em;

    And thanks :)

    • This reply was modified 8 years, 7 months ago by Emilvillumsen.


    Not sure if I’ve missed something here but I can’t see that error on my end using latest version of Chrome, in what browser are you getting this error? Or maybe you got it fixed already?

    Best regards,


    Hi Rikard,

    No, I didn’t get it fixed, sadly. And I still experience it on several devices in latest Chrome, Safari and Firefox.


    Any suggestions?




    I can’t see any issue when loading your website. There is no search box or anything appearing for a second for me. Seems that you could remove it already and if you still see it on your end then I think you are seeing a cached version (caused by cache plugin or CDN). Please check on another device as well.


Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.