Internet Marketing LLC - Naples, Florida

Debra Jalinas

Wodu is very prompt and efficient!! I can always rely on them!

Jim Hayward

Highly recommended. Professional and reliable. The experts at Wodu have solved multiple website and blog issues for me over the years.

Gordon

Sometimes fresh eyes on a problem makes all the difference in manageability. I was dubious about security and if the system would end up worse. Not the case. These folks helped me realize what was going on, implemented a basic fix I was able to apply to the other projects. I'm a satisfied customer.

Aden Hirtle

This is the third time I have used Wodu, and they have been super responsive to my inquires and work requests. I would highly recommend them. They have helped secure some of the websites I oversee and have provided great support.

John Iantosca

Excellent service. Took care of issue with my website right away and kept me posted of progress the whole time until completed which was done promptly. Also fixed issues I was not aware of. Extremely satisfied with their service.

Alyssa Hollingsworth

Prior to the events below, Wodu rescued our conference website during February 2017, service which it provided with dedication and kindness. During the 2018 conference Wodu provided additional resources to see the conference through the peak traffic period.

On January 23, 2019, two and a half weeks prior to our annual conference, we initiated a ticket requesting that Wodu prepare to accommodate our temporary needs as it had done previously. Details were provided regarding the days when we would need additional support, and what our usage was likely to be based on analytics from the 2018 conference. We updated to PHP 7 on Wodu's recommendation.

Later on February 7, the day before the conference officially started, we began to experience higher traffic and outages. Wodu’s response was that our checkout pages weren’t caching properly, an explanation that puzzled us as those pages only received a total of 229 views, about 5.6% of all traffic on Thursday February 7th.

With the site still shaking a bit and the real traffic surge due the next day we were understandably concerned.

The conference’s first event went live at 10am on February 8th, 2019. Almost immediately the site was throwing errors. At 10:06am we updated the ticket asking for immediate help. When we did not hear back in thirty minutes (again, we had requested weeks ago that someone be ready to help us on the 8th) we filed a new high-priority ticket. There was no reply for an hour, so our owner Seabrooke Leckie replied to the thread and an attempt was made to reach the Wodu team via chat (answered only by a bot).

Nearly two hours after the conference began (noon on February 8th) and we began reaching out for help we got a response from Wodu. Their response was unprofessional and uninformative. Customer Support does not define what is good or poor support, the customer does. The support we got was inadequate in relation to the scale of our issues and the lead time we had provided for preparing for an anticipated spike in traffic.

Wodu claimed that the site had outgrown the server, which may be true, but we actually received only 76% of the traffic from 2018, with 88% of the users. Our usage was down, we had upgraded the code, and still the server struggled.

We responded swiftly (within 10 minutes) asking for more information about what moving to a dedicated server would entail, as no details had been provided. At 12:37 we followed up again asking for more information.

At quarter to 4pm we sent an update/inquiry, emphasizing again the importance of support at this time. This finally prompted a curt reply (4 hours after the previous response from Wodu, and 6 after the start of the conference).

The ticket was then closed by Wodu, although the conference was ongoing.

This reply was insufficient for a number of reasons. Having identified that the storage culprit was WP Rocket caching, the only option offered was to disable it entirely, which would result in more hits to the database and strain on the system. No mention was made of how to optimize Rocket, nor a recommendation for another caching plugin.

Increasing our storage needs helped in the interim, but we were not told how much this might cost us or how long we could keep it elevated before charges would kick in.

Wodu specifically said: “This single site has increased the load on the server 10X.” This has a passive-aggressive tone, suggesting that we are to blame for the predicament we were in. This completely ignores our early attempts to be prepared and work with Wodu to be ready for an event we all knew was coming.

Closing the ticket was passive-aggressive, unprofessional, and extremely poor service. What conclusion could we draw but that we were on our own from that point on?

Our developer did some research and found a setting that greatly reduced Rocket’s storage demands, which helped the site continue to run through the rest of the weekend.

We also began researching new hosting options.

Dave Proulx

This was my second time using Wodu's services to do some repairs on my WordPress site. Both times the work was completed efficiently and professionally.

Ross Trottier

After severely under-performing on their contract, they refuse to let me out of a year's worth of service. If you don't want to be charged randomly, and then locked into a contract with the worst service ever: DO NOT DO BUSINESS WITH THESE PEOPLE