Weird problem

  • Resolved Seph

    (@seph)


    8 years, 8 months ago

    Hey there,

    I have a weird problem which I do not understand at all. I have to say that I had a developer configuring Autoptimize for me, so I don’t know much about it.

    I’m using a child theme setup. What I noticed:

    When autoptimize is active, I can override css settings of my theme just fine using my child theme css editor.

    When I deactivate autoptimize, that stops working. I can override some parts using !important or I can not override my settings at all.

    I’m using w3 in conjunction but deactivating both, w3 and autoptimize doesn’t change the issue at all. I’m not even sure that has something to do with autoptimize. I just have no idea at all why I have that issue. Maybe someone here as an idea.

    https://wordpress.org/plugins/autoptimize/

Viewing 9 replies - 16 through 24 (of 24 total)
1 2
  • Ramanan

    (@superpoincare)

    8 years, 8 months ago

    AJ,

    Why is warm cache needed? Doesn’t W3TC do a preload?

    AJ @ WpFASTER.org

    (@ajm_1976)

    8 years, 8 months ago

    …Quick note: images are automatically de-prioritized by modern browsers, so no; this is not the issue with Seph’s site. The issue(s) is/are revealed in the tests linked to.

    Why is warm cache needed? Doesn’t W3TC do a preload?

    It’s supposed to, yes. The problem is that anything relying on a WP cron is unreliable and/or less effective than available alternatives.

    The vast majority of sites are far better off not making use of this W3TC feature at all; and, instead, implementing the every-time hammer of direct cache warming. It is far more effective.

    AJ

    Thread Starter Seph

    (@seph)

    8 years, 8 months ago

    I activated the code snippet – it killed my section menu. 🙁

    Plugin Author Frank Goossens

    (@futtta)

    8 years, 8 months ago

    In that case I would remove (or comment out) that code snippet Matthias.

    frank

    Thread Starter Seph

    (@seph)

    8 years, 8 months ago

    Yeah, I killed it. Nevermind guys, thanks for your support. I really don’t know what do right now, but at least I know now that the page isn’t as slow as I thought it is. 😉

    Plugin Author Frank Goossens

    (@futtta)

    8 years, 8 months ago

    If I were you, I would try to (find someone -like AJ- to) look into what is causing the delay in start render time. This very important metric currently is around 1.65s, but it could be about a second faster really (after HTML & main CSS have been downloaded).

    (going to mark as resolved, as this is no Autoptimize-issue any more)

    frank

    Thread Starter Seph

    (@seph)

    8 years, 8 months ago

    So…you think start to render time is something to focus on? I checked the mobilegeeks site out of interest and I noticed that their start to render lag is even bigger than mine. Still, their page is insanely fast, one of the fastest I’ve ever used.

    http://www.webpagetest.org/result/150819_TY_DTJ/

    Plugin Author Frank Goossens

    (@futtta)

    8 years, 8 months ago

    well, mobilegeeks is slower then yours when looking at it here and tests seem to confirm that 🙂

    Ramanan

    (@superpoincare)

    8 years, 8 months ago

    Mobilegeeks is using Cloudfront as its CDN. So images will load faster.

    Its origin server is of course slower as compared to yours.

    You might try a CDN Matthias. These days they are usually cheap but if your site has a lot of traffic, you should try to estimate the costs and see if it is worth for the business from your site. It will be an economic decision.

Viewing 9 replies - 16 through 24 (of 24 total)
1 2
  • The topic ‘Weird problem’ is closed to new replies.