• Resolved michaelgimm

    (@michaelgimm)


    Hi there
    I have used Autoptimize for some time and I am very fond of it. However I just changed my hosting company and now run on Kinsta.

    Somehow there is an issue when running my site in Chrome browser. When loading, it starts by showing big blue letters before changing to what should actually be there from the start.

    I tried disabling Autoptimize, clearing Kinsta cache and then it works like a charm.
    Is there a setting I could remove in Autoptimize or exclude something in order to make this anoying blue “thing” go away?

    See this little video about the bug: https://www.useloom.com/share/b167226389804c88826f01d9c84cf7ed

    Cheers
    Michael

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    sorry for the delayed response, only just now saw this topic @michaelgimm.

    I had a look at your page but can’t see what was visible in the video, does that mean you were able to fix yourself? 🙂

    frank

    Thread Starter michaelgimm

    (@michaelgimm)

    Hi Frank, not not really.
    If you look at product pages (pick any product) you will see that the problem is still there…

    Tried a lot of different things but was not able to find the problem :-/

    Cheers
    Michael

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    very weird;
    * I can reproduce in FF on product pages
    * I can’t reproduce in webpagetest.org (see filmstrip-view at https://www.webpagetest.org/video/compare.php?tests=190403_T4_792c9a4d49cd8f1f69499457327fc803-r:1-c:0)
    * It looks as though the autoptimized CSS is applied too late, which would happen if you had “inline & defer” on, which you don’t
    * The homepage indeed does not have that problem, but I don’t see relevant differences there that could explain what the HP works and a product page does not
    * I can however also reproduce when AO is disabled by adding ?ao_noptimize=1 to the URL (e.g. /product/oekologiske-hel-oelandshvede-fra-aurion/?ao_noptimize=1)
    * But I don’t see how page caching (Kinsta vs other) could impact CSS being applied

    So that leaves us with somewhat of a mystery I’m afraid.

    2 things you could try;
    1. disable cloudflare rocketloader (and any other optimization option you might have active at cloudflare’s)?
    2. you could try the “inline & defer” option in AO (see AO FAQ for info on how to), which adds the CSS to render the “above the fold” page inline, so it _should_ be applied immediately.

    frank

    Thread Starter michaelgimm

    (@michaelgimm)

    Hi Frank, thank you for getting back to me.
    I found there was maybe two errors causing this.

    In my site theme I have the ability to use a setting called “Use internal fonts” and for that I installed the main font I use “Montserrat Alternates”. Since I used internal fonts, I also used the “Remove Google fonts” setting in AO.
    I found that this setting will cause the big/blue font issue on entire site, so I disabled it, and was left with big/blue fonts only on product pages.

    The I went to Cloudflare and created a page rule for Rocket loader not to load on http://www.weensu.dk/product/* and that seems to do the job.

    It works now but maybe there is also a conflict between theme and AO “Remove Google fonts”?

    Thanks

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    interesting. question; if you leave “remove google fonts” on but disable rocket loader entirely, does that also fix the problem?

    Thread Starter michaelgimm

    (@michaelgimm)

    Yes that works, but it also significantly slows my site. See this comparison: https://www.dropbox.com/s/pe10wyctp5lk6ka/speedtest.png?dl=0

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    Bizar Michael … Somewhat at a loss here I’m afraid, but given my earlier feedback

    I can however also reproduce when AO is disabled by adding ?ao_noptimize=1 to the URL (e.g. /product/oekologiske-hel-oelandshvede-fra-aurion/?ao_noptimize=1)

    this rather (or “also”?) looks like some kind of conflict between theme & cloudflare?

    frank

    Thread Starter michaelgimm

    (@michaelgimm)

    Ok Frank
    Thanks for taking your time to answer. I will just disable that part of Autoptimize then.

    Michael

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Conflict with Kinsta cache plugin’ is closed to new replies.