• Hi,

    I am using twenty-sixteen. Everything works good except when making comments.

    It’s takes forever to load the post after submit? Like 8 – 15 sec before it completed load?

    Is any functions, etc ways to load instantly or at least quicker?

    Please advise help,
    Thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator bcworkz

    (@bcworkz)

    Do you have any anti-spammer plugins filtering comments? It can take a while to decide a comment is not from a spammer, especially if the plugin is using an external resource to do the checking.

    What you can do, if anything, depends on where the bottle neck is. Use your browser’s network developer tool to determine which part of a page load is taking a long time. Focus your efforts on making that part faster if possible. There may be a choice between strong spammer security and speed.

    Thread Starter DamnDramaQueen

    (@damndramaqueen)

    Hi bcworkz,

    I am using Anti-Spam by CleanTalk plugin many months now.

    I am also buddypress, and the activity stream load either instant and/or within 1 sec. However if CleanTalk somehow is not affecting activity Post Update?

    CleanTalk blocked spams like a charm! But, any other anti-spam plugin you can recommend? Perhaps other way to fix the load time?

    However, for the 2nd part (browser’s network developer tool), I have no idea to go by that! Any help?

    Please advise help,
    Thanks

    Moderator bcworkz

    (@bcworkz)

    I don’t have any specific recommendations. Every site’s anti-spam needs are different, what works for me may be unusable for you. There are all sorts of plugins available that are free or at least free to try. Evaluate a few for a while. Weigh speed against the mis-identification rate on your site. I think it’s worth tolerating a little bit of spam in order to gain speed.

    On further thought, the Network Developer tool I mentioned probably does not have enough granularity to identify a specific plugin as the bottleneck. All the same, it’s a useful tool for identifying other page speed issues. It’s thus worth learning about even if it does not help in this instance.

    Rather OT at this point, but FYI:
    All major browsers have a set of developer tools, some of which are useful to non-developers. Ctrl-shift-I will typically open the UI. Otherwise look for something in the browser menu regarding tools. The resulting UI will have several different tools listed across the top. Go to the Network tool. Reload the page, submit a form, or navigate to start logging HTTP requests.

    It’ll be readily apparent which requests take a relatively long time. You can click any particular request to see more information like headers sent and received and any data sent.

    While you have the developer tools open, check out the Elements tool, where you can evaluate and alter/test the applied CSS for any page element. It has a mobile device emulator that is very useful in responsive theme development. The Console tool is mainly a JavaScript error log, something to check if a page is behaving strangely. The other tools have their uses, but are of lesser interest to most users. Don’t be afraid to experiment with these tools, you cannot break anything that a reload does not fix.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Post Time’ is closed to new replies.