1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Wordpress site loading super slowly after migration

Discussion in 'BlackHat Lounge' started by Floopa75, Dec 11, 2016.

  1. Floopa75

    Floopa75 Jr. VIP Jr. VIP

    Joined:
    Feb 6, 2014
    Messages:
    815
    Likes Received:
    713
    Gender:
    Male
    Recently had a bad plugin installed on a site I'm working on and it crashed the site. Had the site migrated to a different hosting account on the same host provider and ever since the site has been loading horribly. I had it loading in around 1.5 seconds before the crash + migration, consistently.

    Stuff I've already tried:

    - Fumbling with plugins, deactivating them 1 by 1
    - Tried different kinds of caching
    - Deleted post revisions, optimized databases
    - Added in a CDN
    - A bunch of other small stuff

    None of the above has produced a consistent result. If anyone has dealt with this please help me out. Gtmetrrix is telling me the site takes 60 seconds to load.

    One weird thing I want to mention is that when I run the site through Gtmetrix, the images on the home page take 60 seconds for Gtmetrix to load. But if I go directly to the image URL it loads almost instantly. So I'm thinking it has something to do with the how the site is being served to browsers.

    Any ideas I'm willing to try.
     
  2. staypositive

    staypositive Power Member

    Joined:
    Jul 28, 2015
    Messages:
    623
    Likes Received:
    66
    Occupation:
    Hiring content writer, please PM
    do u have a lot of spam comments in your wordpress?
    had the same experience before and i went to phpadmin and comment table and flush it all out

    otherwise, try wp super cache

    or maybe contact ur hosting company to ask how many memory they giving u and compare with the original one
     
  3. Zwielicht

    Zwielicht Moderator Staff Member Moderator Jr. VIP

    Joined:
    Aug 31, 2013
    Messages:
    6,612
    Likes Received:
    11,754
    Gender:
    Male
    Occupation:
    Private Investigator
    Location:
    Riverside, California
    Home Page:
    Run the site through the tool in the link below, scroll down to the file requests when the tool is done, and take a look at what's slowing the site down (post a screenshot here if he want).
    https://tools.pingdom.com/

    Using my business site as an example, the site loaded in 1.44 seconds, but if I look at the file requests, I can see that there's a huge amount of wait time for the server to send the files (so the server is at fault here) and quite a bit of receive time (I think this is caused by large files).
    [​IMG]
     
    • Thanks Thanks x 1
  4. tomoisme

    tomoisme Newbie

    Joined:
    May 30, 2016
    Messages:
    25
    Likes Received:
    4
    Gender:
    Male
    Occupation:
    Miner
    Location:
    Gold Mine
    Home Page:
    I had the same problem when i use w3 total cache. my themes breaks and failed to load many times.

    Then I disable w3 total cache, delete it, and install wp super cache to replace it. everything works fine again.

    is your hosting using Litespeed Webserver?

    If yes, you might want to use Litespeed Cache. It works better than WP Super Cache.

    Maybe this will help with the load time.
     
  5. ahansson89

    ahansson89 Newbie

    Joined:
    Jan 19, 2016
    Messages:
    19
    Likes Received:
    3
    When I run into this kind of issue on a client site, I either switch hosting provider or/and install a caching plugin.

    On the hosting side, there are only two providers that stand out IMHO... Flywheel and LightningBase. Awesome support and awesome speeds.

    If you do not want to switch hosting, then I recommend you install a caching plugin. The best one out there is WP Rocket.

    Send me a PM if you need help with any of this.
     
  6. Koenza

    Koenza Jr. VIP Jr. VIP

    Joined:
    Dec 23, 2015
    Messages:
    132
    Likes Received:
    33
    I would try tomoisme's method, most likely a cache issue.