Viewing 13 replies - 1 through 13 (of 13 total)
  • Moderator t-p

    (@t-p)

    It’s something on the fyver.io end. I ran three speed tests and they all had 24+ second wait times.

    Thread Starter pandawang16

    (@pandawang16)

    Thanks. But I have already installed many of the cache plugins. I have W3 Super Cache, EWWW Image Optimize, Autoptimize, and deleted many of my plugins. I only have well-known reputable plugins. All my images are smushed.

    Any other recommendations? What do you think is the root cause of the long wait time?

    Thread Starter pandawang16

    (@pandawang16)

    @bdbrown Yes I have also tested it that way and see the same results. Could it be a problem with the theme? The theme I am using is theFox theme which is a quite popular premium theme.

    It doesn’t have anything to do with your site; it’s the fyver.io server that’s the problem. Clear your browser cache and go to the fyver site directly in your browser; you’ll get the same slow results.

    Thread Starter pandawang16

    (@pandawang16)

    @bdbrown Oh so its a problem with the server (like my hosting company) what should I change over on that side?

    For some reason speed is much faster once I switch to 2016 theme no plugin differences.

    • This reply was modified 9 years, 5 months ago by pandawang16.

    OK, maybe I misunderstood what you were describing. Is fyver.io your site?

    You have:

    +45 js files
    +25 css files
    +15 font files

    These take time to download / process / parse.

    Consider reducing and combining as much as possible.

    the time till first byte (the wait for the initial HTML) is too long and you indeed have a lot of JS, CSS & Fonts. based on the HTML & HTTP response headers neither W3TC (which should fix the TTFB-issue) nor Autoptimize (which should cut down on number of CSS/ JS files) are active at the moment?

    frank

    Thread Starter pandawang16

    (@pandawang16)

    Funny that you mention autopmtimize, since I deactivated it and now the website loads much faster. I think if I split the files it should be fine.

    well, as you’re using a page cache (w3tc), any impact of AO should only be on first load (after which it should fly really). using AO without a page cache is frowned upon πŸ˜‰

    concerning the impact of AO on your first load; that depends on context (CSS/ JS injected by theme + plugins) and configuration. if would ever want to optimize CSS/JS (I know I would), you should have a look at the AO FAQ.

    frank (ao’s developer πŸ™‚ )

    Thread Starter pandawang16

    (@pandawang16)

    My theme support said

    For Autopmize, you will have a problem with our theme if you put all the files in one file, if you split in two or three it should works fine.

    How do I split the said files?

    putting all in one file should not necessarily be a problem, but you could always exclude one or more of the bigger files from optimization.

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

The topic ‘HTML Wait Time Very Long’ is closed to new replies.