Why I Use the WordPress Divi Theme

Why I Use the WordPress Divi Theme

If you ask a WordPress developer what their favorite builder theme is, you’ll get a very opinionated answer, kind of like asking a photographer what brand of camera is best, or a gamer what console is best. The truth is, there are a lot of great themes out there. Many of them can be used to create great sites in the hands of an experienced developer.

These are the reasons that I use the Divi Builder theme for most of my personal and client WordPress sites.

Note: I receive compensation from service providers when you purchase through the affiliate links (at no extra cost to you). I test and/or research each service thoroughly before endorsing it. I own this site and the opinions expressed here are mine.

What I Love About Divi

1. It’s Intuitive and Relatively Easy to Learn

Every WordPress builder has its learning curve, but I think Divi is one of the easier ones to learn. The Divi Visual Builder lets you edit in WYSIWYG mode, which is great for beginners.

The reason why ease of use is so important to me is that I like to empower my clients to edit their own sites. I wouldn’t dare expect my clients to learn how to use some of the other builders out there. The whole point of WordPress is to let people edit their sites without hiring a developer!

2. It Looks Great Out of the Box

Elegant Themes has always had a reputation for making really great-looking themes. Divi is no different. Most of the modules look great out of the box.

3. It Has the Right Amount of Adjustability

There is a tradeoff between how much adjustability a theme has vs. how cluttered and overwhelming the user interface is. You could make every single thing adjustable, but then the theme would be a bloated mess. The perfect theme makes the items that need to be adjustable, adjustable, while leaving the rest fixed.

I’d say that Divi strikes a pretty good balance between adjustability and keeping the user interface manageable. Sure, there are a few things that I would love to have more control over (like feeds), but for many of those, I can adjust using CSS or custom code in a pinch.

The Divi Theme Builder lets you build completely custom blog templates (or any other type of template). This is a huge deal.

4. I Can Develop Polished Sites Using Divi Really Fast

Because of many of the reasons I’ve mentioned, I can develop polished sites using Divi really fast. My clients are often amazed at how quickly I can get their sites done – and they really appreciate it.

5. It Has Great Documentation and Support

Divi is one of the most popular WordPress themes around, so it has tons of documentation, informational blog posts, videos, and third-party plugins. If you need to make Divi do something, you can usually just Google it, and someone has found a solution or created a plugin to do it.

6. It Doesn’t Break When Updating

Because Divi has been around for so long, a lot of the bugs have been ironed out. Some of the newer themes have some great features, but I’ve found some to be buggy. Divi just works and is reliable.

Probably the biggest problem I’ve encountered is that some older Divi sites can’t use the latest version of the Divi Builder editor (called “The Latest Divi Experience”). This is not really a show-stopper though, because the Visual Builder still works, and it’s only happened in a few cases for me.

Other than that, I’ve rarely had a site break after a Divi theme update. With certain other themes (i.e., WP Bakery), I dread pressing the “update” button.

7. You Pay For It Once (Lifetime Deal)

I love software that you pay for once, as opposed to having to renew every year, even though Divi would be well worth paying for every year. Although there is no free version, Divi has a lifetime deal which is a steal if you use it on multiple sites.

What Detractors Say

Probably the biggest complaint you’ll hear from some developers about Divi though, is that it is “bloated”. It’s true that full-featured builder themes like Divi and Elementor generate lots of levels of div tags. But that in itself doesn’t have a noticeable impact on load time.

Detractors will point to poor website speed test grades for Divi (and Elementor) compared to Oxygen or Gutenberg sites. But those grades are actually not that relevant; I can fix that by installing a plugin. What really matters is the actual page load time in seconds. And while Divi isn’t the fastest-loading theme around by any means, you can get really fast Divi site load times (i.e., one second or less) if you use caching and premium-quality hosting.

When Divi Might Not Be the Best Choice

If you need to create a very customized site with unorthodox design elements, Divi might not be the right choice. You may need to with a builder with more customizability like Oxygen or perhaps a full-custom theme made from scratch.

Divi specifically lags behind Elementor and Oxygen when it comes to the customizability of feeds. There is no built-in blog feed layout with the image on the left and the excerpt on the right; there’s only full-width and masonry-style. I compensate for this by using CSS or by writing my own feed plugins in PHP. If you’re not a programmer and need really customized feeds, then you might want to go with a different builder.

If you want to create a complex WooCommerce store, there are probably much better themes out there specifically optimized for WooCommerce.

Finally, if your client is obsessed with site load time, then you should probably look for a solution other than Divi (or Elementor). Check out some of my other recommended themes below, or consider using WordPress as a static site generator; you’ll get insanely fast load times.

Other Recommended Themes

If you are creating a really simple personal blog or WooCommerce store, I like GeneratePress. It’s easy to use, blazing-fast, and has accessibility built-in. It’s not nearly as customizable as Divi though, even with the paid add-ons.

If you need more customizability than GeneratePress offers, I’d recommend Kadence. It’s also super fast and accessible. It’s a great theme to use with Gutenberg when you don’t need the full customizability of Divi.

If you need a very customizable theme that also loads very fast, check out Oxygen. I love the customizability of this builder, but it has a steeper learning curve and there’s no way I’d expect clients to learn how to edit using this builder. It’s also not as elegant-looking as Divi out of the box. Of course, it can be made to look nice, but it takes more effort. For example, the built-in Oxygen menus are terrible; most people use the Max Mega Menu plugin with Oxygen instead.

A Word About Elementor

No discussion on WordPress builders would be complete without mentioning the other industry-standard builder out there, Elementor, which is used by many WordPress professionals.

I actually like Elementor. If Divi didn’t exist, I’d probably be using Elementor. In some ways, it has more adjustability than Divi and in other ways, Divi is more adjustable. But, I find Divi to be easier to learn and use, which is very important for my clients. I like the fact that Divi is a theme rather than a plugin like Elementor. With Elementor, you have to choose a theme to use it with. Also, Elementor Pro has an annual fee; there is no lifetime deal like Divi has.

Conclusion

So, I’ve tried to give the pros and cons of the Divi Builder, along with honest comparisons to other builders, and the reasons I ultimately chose Divi. If you’re interested in a super-powerful drag-and-drop WordPress builder that is relatively easy to learn and has lots of support and add-ons available, check out Divi!

My Website Accessibility Checklist

My Website Accessibility Checklist

Although I do not guarantee 100% WCAG compliance for my websites (and as I explain below, such a thing doesn’t really exist), I do try to make them compliant in the ways that are most important for accessibility. The goal here is to make your site more accessible and less-attractive for accessibility litigation than the other guy’s site.

If you do require strict WCAG compliance, I have a third-party firm that specializes in accessibility that I can work with to get your site compliant.

Note that there is actually no formal certification process you can go through to have your website definitively declared “100% compliant”. There are just a set of guidelines that are somewhat open to interpretation and a continuum of compliance levels.

My Accessibility Checklist

Below are areas where I strive for accessibility compliance. Often there are exceptions that are not compliant though, that are signed off by the client. And, this list is by no means a complete list of requirements for WCAG compliance.

Appearance

  • Text at least 14 px in size
  • Minimum color contrast rules are followed
  • States are not communicated just by color

Keyboard Access

  • All links are keyboard-accessible
  • All navigation (menus) are keyboard-accessible
  • All dynamic elements (i.e., accordions, tabs, etc.) can be operated by keyboard
  • Keyboard focus is visible

Links

  • <a> tag is used for links
  • Links in body are distinguished from surrounding text (usually by underlining)
  • Link text is descriptive

Structure

  • Only one h1 per page
  • Headings should be in sequence
  • Heading levels should not be skipped

Images

  • Images have alt text or captions
  • Images do not have title attributes

Videos

  • Video does not auto-play
  • Video can be paused
  • Video has accurate transcript or captions (read how to edit YouTube captions)

Forms

  • Fields have label tags
  • Fields are keyboard-accessible

PDFs

As I mentioned, this is not a comprehensive list, but rather some of the “biggies” that can have a really obvious effect on your site’s accessibility.

Tools and Resources

Some Common Website Features that Are Not ADA Compliant

I don’t know of a third-party slider carousel that meets WCAG guidelines. The accessibility professionals who I’ve asked have told me not to use carousels on sites that need strict accessibility compliance.

Most social embeds and embedded ads are not accessible. Animation effects may not accessible, and auto-playing videos are not allowed.

Any linked PDFs need to be re-generated with accessibility in mind, and all embedded videos need captions or transcripts.

A Note About Overlays and Instant Compliance

You might have heard of services that claim to make your website “100% accessibility compliant” instantly by adding a button or “overlay”. The vast majority of accessibility experts see these services as snake oil which don’t work. Worse, they may make your site an even bigger target for accessibility litigation:

nearly all of the functionality provided by these tools has no impact on your level of WCAG conformance whatsoever. Furthermore, these overlays provide little or no additional legal protection for your website. In fact, in recent lawsuit filings, screenshots of these tools are being used to build the claim against websites that are not also seeking a holistic approach to ADA compliance. It is also a common belief that these tools may increase your risk with regards to security, and many company’s security policies prohibit the installation of widgets like these.

Michele Landis, Kelly Heikkila, Jason Webb, Accessible360

So obviously, I don’t advocate using services, whether free or paid, that promise instant accessibility simply by installing a plugin or code snippet. As the quote says, it takes a wholistic approach to many aspects of the website itself, as well as offline resources like videos, embeds, and PDFs.

Conclusion

Let me know if you have any questions or comments about this topic! – Brian

Why You Should Own Your Own Domain Name and Web Hosting Accounts

Why You Should Own Your Own Domain Name and Web Hosting Accounts

I always tell my clients to set up their own domain name and web hosting accounts and pay for with their own credit card. I do not provide hosting. Here’s why I think you should not let your web developer (or any third party) own your web and domain name accounts.

1. You could get held hostage by your web developer

Your domain name and web hosting are too important to be in the hands of a third party. Your domain name is an important part of your brand’s identity, with SEO value that can’t easily be replaced. You might have put a lot of work into your website. Unless you’re doing offsite backups, all of that resides on your hosting. You or your business needs to control these, not a third party that can hold you hostage if you have a disagreement over payment terms or services.

2. Your web developer might go M.I.A.

Maybe you get along with your developer fine, but you never know what could happen to them. He or she could quit web development and become a monk and move to Tibet. They could get hit by a bus. You could lose control of your domain and website if any of these happen.

3. You might want to move your web business elsewhere

I’ve seen the awkward situation where my client wants to move away from a web developer who owns their web hosting and domain name. It’s a delicate situation. Will the developer happily provide you with a backup so you can move the site? Will they take the steps necessary to unlock the domain name and transfer it? Will they resist, delay, or even sabotage the process? Moving these resources from an existing developer is always a stressful process. Plus, it costs time and money to transfer the domain and hosting.

If you own the hosting and domain, you can do whatever you want with them, whenever you want. You don’t need to ask for permission from anyone and pray that they comply. And switching web developers is FREE.

4. You’re paying for a middleman

When you pay someone to host your domain and site for you, you’re paying for a middleman who will go out and purchase these from a third-party hosting company, probably with a markup. They might provide additional maintenance and help, and that’s fine, but you should pay for those services separately and not mix these with hosting.

Conclusion

In all fairness, I do know situations where developers control the web and domain name hosting and their clients are completely happy with them. That’s great. If you’re looking to launch a website though, you should consider the reasons above before deciding on your web and domain name hosting. – Brian

My Website Project Kickoff Checklist

My Website Project Kickoff Checklist

These are some questions I think about before starting a new website project. It’s a great checklist to go through before starting to help you scope out your project.

A. Audience and Purpose

  1. Who is the target audience of the website?
  2. What is the site tagline, in non-marketing speak?
  3. What is the number one thing you want your visitors to accomplish on the site?
  4. What are the top three goals of the website?
  5. What is the criteria for success for this website?
  6. Will the site visitors be mainly new visitors (for example, for a sales funnel) or repeat visitors (for example, for an association website)?

For more information on this section, see “Three Basic Questions You Should Answer Before Building Your New Website“.

B. For Site Revisions / Migrations

  1. Is this a brand new site or a revision of an existing site? If new site, skip to next section.
  2. Do you see this as a complete re-do of your current site, or just a cosmetic makeover?
  3. What things do you hate about your current site?
  4. What things do you like about your current site?
  5. How will the old site be backed up before we replace it?
  6. How much content will be re-used from the old site vs. new content?
  7. What is the plan to migrate data from the old site to the new one?
  8. What is the plan to update the new site with new content while it is in development?
  9. Do we need to redirect old URLs?

C. Structure

  1. Do you have a site map for the new site?
  2. How many pages will it have?
  3. Do you have an outline for each page?

D. Written Content

  1. Do you have all of the text content for the site ready?
  2. Will the text be completely proofread and approved, or are changes / corrections likely during development?
  3. Who will do most of the content entry?

E. Image Content

  1. Do you have all of the logos and icons for the site?
  2. Do you have all of the images for the site?
  3. Are the images existing original images? Stock? New photography?
  4. Will the images need to be cropped, adjusted for brightness or edited in any way?
  5. Will there be background images with text over them?

F. Video Content

  1. Will there be video on the site?
  2. What format will be video be in? (I highly recommend hosting embedded videos on YouTube or Vimeo, not serving video files from your webserver!)
  3. Will there be video backgrounds?

G. Features

  1. What features do you want on the site?
  2. Blog?
  3. Commenting?
  4. Events management?
  5. Contact forms? With logging?
  6. Other forms? With logging?
  7. Popups? (Searchable, linkable, shareable?)
  8. Social sharing buttons? Social follow buttons?
  9. Custom post types?
  10. Custom fields?
  11. Custom search/filtering?
  12. Google map?
  13. Ability to upload documents?
  14. AJAX (elements of the page loading without a full page reload)?
  15. Third-party plugins, widgets, APIs?
  16. Will the site be sending email?

H. Design

  1. Has the new site already been designed by another designer?
  2. If not, are we creating a brand new design concept, or are we adhering to an established design language?
  3. Are we using an existing design template?
  4. Is there a style guide?
  5. What fonts are we going to use? Paid or free?
  6. How many different types of page designs will there be?
  7. What percentage of your users will be on mobile vs. desktop?
  8. Does the site need to work on Internet Explorer or any other non-modern browsers?
  9. Do you want any special hover effects? (Note that hover is not good for ADA compliance and that there is no hover on mobile devices).

I. Compliance

  1. Do you have a GDPR / CCPA compatible privacy policy?
  2. What user information do you intend to collect? (contact forms, email addresses, email list signup forms)
  3. Are you prepared to comply with the requirements of GDPR and CCPA if a user makes a request for their data?
  4. Does the site need to be ADA (WCAG2.0) compliant?
  5. Are you prepared to create a Terms of Use document for the site?

J. Search Engine Optimization

  1. Do you need help with SEO?
  2. Do you need help optimizing your content for SEO?

K. Analytics

  1. Do you have analytics data for your current website (if there is one).
  2. Do you have a Google Analytics account? (If so, I’ll need your UA- tracking number if you want to track your site using GA).
  3. Do you need to track any other events on the site other than simple page loads? (i.e., button clicks, form submits, etc.)
  4. Do you need any other tracking services on the site?

L. Security

  1. Do you want to do eCommerce on this website?
  2. Are there known individuals or parties who might target your website for attack (such as DDOS attack). Examples include disgruntled ex-employees, activists, political enemies, etc.

M. Logistics

  1. What hosting service will we use? (I can offer suggestions)
  2. Does your host offer SSL?
  3. Do you have control over your domain name?
  4. Do you have an SMTP email account that we can use to send email from the site?
  5. What is the estimated traffic of the site?
  6. How much storage (in GB) will be needed for the site?

N. Testing and Approvals

  1. Who will help test the website before launch?
  2. Who needs to approve the website before launch?
  3. Who are the stakeholders for the website?

O. Schedule

  1. What is the desired launch date?
  2. Is this a hard deadline (such as a trade show, event, etc.)?
  3. How long will it take to create and gather your content?
  4. How long will the approval process take? (Is your boss easy to reach? Are they responsive?)

P. Cost

  1. What is your budget for the site?
  2. Do you want to pay hourly for the site, or have a fixed price?
  3. If fixed, it is a “not-to-exceed” or is an estimate OK?

Q. Post-Launch

  1. Who will be updating the site content after launch? What is their technical experience?
  2. Do you need training on how to update the site?
  3. Who will do maintenance on the site? (WordPress core, plugin, and theme updates)
  4. How often will the site content be updated?
  5. What is the backup strategy?
  6. Do you need a staging site? (i.e., a copy of the site that you can play around without affecting the production site).

Conclusion

Please let me know if you have any comments or questions! – Brian

Nine Things You Should Do Before Updating Your WordPress Core, Plugins, or Theme

Nine Things You Should Do Before Updating Your WordPress Core, Plugins, or Theme

WordPress makes it very easy to update your website to the latest versions of the WordPress core, plugins, and theme. Just click a few buttons, right?

Well, anyone who’s worked with WordPress for a while knows that simply pressing “update” without some serious preparation can be a recipie for disaster.

Here is a list of things you should do BEFORE updating your WordPress site!

1. Make a Backup

If you do nothing else on this list, please do this one thing: make a backup of your site. I like to use the Duplicator plugin to do this. Some web hosts like WP Engine have one-click backups in their admin panels (in addition to daily automatic backups).

2. Test the Live Site Before Updating

It might seem strange to test something that is supposed to be working before you even touch it, but I’ve had cases where a site wasn’t working properly after an update, and it turned out that the problem actually had nothing to do with the update.

Make sure the live production site is working properly BEFORE you do anything to it, or else the update could lead you on a wild goose chase while you try to figure out why your update “broke” the site (when it had nothing to do with it). Not to mention, this way you won’t be wrongly blamed for a site that was broken before you did your updates!

3. Take Screenshots of Important Pages Before Updating

I’ve had situations where I’ve updated a site, then wondered, “hmmm… was the space between the header and the body really that big before the update??” (In this particular case, nothing changed after the update; I was just paranoid).

Taking a screenshot of the Home page and any other key pages can calm your fears if you start to get paranoid and think something changed after the update. Or, it can confirm that the update did indeed break something.

A variation of this is to load some of the pages of the website in a separate browser window, leave them there, then open a new window to do the updates. Then, you can compare the new site to the old (just don’t accidentally refresh the windows with the pre-updated site!)

4. Keep a Log of Changes

When I update a site, I keep a log of every change I make. I note the old and new versions of everything I update. To make that easier, I copy the plugins section of the WordPress Updates page and paste it into a file. That gives me the old and new versions of every plugin that needs to be updated.

If something goes wrong, I have a list of plugins that could have caused the problem!

5. Check for Major Version Updates

Before updating, I scan the plugin version numbers to see if any are jumping to a new major version, like going from V2.9.2 to V3.0.5. If any are, I read the plugin notes to check for any compatibility problems with the new version. Same goes for themes, and the WP core.

6. Check for Recent Updates

Building on the previous point, if there has been a major update to a plugin or theme, I check to see when that update happened. If it was very recently, like yesterday, I will sometimes hold off on the update for a while and let other people be the guinea pigs to test the new version, rather than having it break my site.

7. Check Your Server’s Version of PHP

If you’re updating a site that hasn’t been updated in a very long time, there’s a good chance that it’s running an old version of PHP. Doing updates to such a site could be disastrous, because the new versions of the theme and plugins might not be compatible with your server’s version of PHP.

I like to use the Duplicator plugin to check the version of PHP. Go to Duplicator -> Tools -> PHP Information to see what version of PHP your server is running. Call a web developer if it is below 7.0.

8. Test Updates On a Staging Copy

Now that you’ve done a lot of the preliminary work, it’s time to test the updates on a staging site, i.e., a non-public copy of your site.

This can be a site hosted locally on your computer using a program like MAMP (kind of advanced), or a copy of your site online that your web developer can create for you. (Just make sure the staging site is running on the same version of PHP that your production site is).

WP Engine provides a free one-click staging copy for this purpose. Siteground offers staging copies, but you have to set up the subdomains in your DNS records first. Whatever way you do it, if you want to avoid downtime after a botched update, test on staging first!

9. Have FTP and Database Access

Sometimes, even when you do everything “right”, things go wrong. That’s why I make sure that I have FTP access to the website’s server and phpMyAdmin access to the database (or SSH access) BEFORE I update anything. That way, I know I have a way to restore the site if anything should go horribly wrong.

If you’re not a developer, then you should have a developer “on call” in case something goes south.

After the Update – Do Not Skip This!

OK, so you’ve done everything on this list, and clicked “update”, so now you’re done, right? Not quite. You need to test the production site thoroughly for any issues. Remember to clear all caches!

The one thing folks always forget to test is the contact form! Do a test submission and make sure the person at the other end receives the email. Do not skip this step!

Oh, and don’t forget to make another backup of your site, so you have a nice clean updated copy!

A Final Note

The steps I’ve outlined above should be considered the minimum you should do before updating a WordPress website. If you’re running an e-commerce site that brings in thousands of dollars per day for example, I would go over and above the steps I’ve outlined here.

Please leave questions and comments below! – Brian

What Is the Difference Between SiteGround Web Hosting vs. SiteGround WordPress Hosting?

What Is the Difference Between SiteGround Web Hosting vs. SiteGround WordPress Hosting?

I personally use and recommend SiteGround shared web hosting for WordPress sites because their servers are fast and reliable, the cost is reasonable, and their support is good.

But, if you go on their website to pick web hosting for your WordPress site, you’ll find “Web Hosting” and “WordPress Hosting”. What’s the difference?

I was wondering that too so I messaged them. The answer is pretty simple and less than what you’d think.

The Answer

SiteGround’s “WordPress Hosting” comes with WordPress pre-installed. That’s it.

Since you can easily install WordPress on their regular Web Hosting Plan, the two plans are pretty much the same.

I suspect they have the two plans for marketing reasons, to compete with other providers’ “WordPress Hosting” plans. But the truth is that you can install WordPress on either plan (or not). – Brian

Note: I receive compensation from service providers when you purchase through the affiliate links (at no extra cost to you). I test and/or research each service thoroughly before endorsing it. I own this site and the opinions expressed here are mine.

How to Clear Your Browser Cache to See the Latest Version of a Website

How to Clear Your Browser Cache to See the Latest Version of a Website

When your web developer makes changes to a website, you might not see those changes in your browser because of something called “browser caching”.

Basically, that means that the browser keeps old copies of parts of the website locally so it doesn’t have to re-load them each time you visit a new page on the site.

That’s great for making pages load fast, but it could mean that you’re viewing an old version of the site, especially if your developer has made changes recently.

Here’s how to do a “hard refresh” to clear your desktop computer’s browser cache:

Windows Browsers


Windows Chrome and Edge

Hold the CTRL key, then click the “Reload” button on your browser.

Windows Firefox

Hold the CTRL key down and press F5

Mac Chrome, Firefox, and Safari


Hold the SHIFT key, then click the “Reload” button on your browser.
On Chrome, you can also hold down COMMAND SHIFT and press the R key.

Mobile Browsers


On mobile devices such as iPhones, iPads, and Android devices, you need to completely clear the browser history to see the latest version of a website.

iOS Chrome

  1. Open the Chrome app.
  2. Tap the three dots at the bottom to get to the main options
  3. Tap History
  4. Tap “Clear Browsing Data” in red at the bottom of the screen
  5. Confirm all of the types of data are checked off, then tap the red “Clear Browsing Data” at the bottom of the screen again.
  6. In the popup, tap “Clear Browsing Data” yet again!
  7. Tap “Done”.
  8. Tap “Done” again.

iOS Safari

  1. Go to the Settings app and find Safari. I find it easiest to type “Safari” in the search field.
  2. Tap “Clear History and Website Data”.
  3. Tap “Clear History and Website Data” again.

Android Chrome

  1. Open the Chrome app.
  2. Tap the three dots in the upper right corner of the browser.
  3. Tap History
  4. Tap “Clear browsing data…”
  5. Tap the “Clear data” button at the bottom.
  6. Tap X to close the window.

Conclusion

If you do this, you should be able to see the latest version of the website. The browser cache will clear itself naturally over time, so your visitors will eventually be able to see the latest changes as well without having to do a hard refresh. – Brian

Three Basic Questions You Should Answer Before Building Your New Website

Three Basic Questions You Should Answer Before Building Your New Website

Knowing the answers to these three questions will help your site’s messaging stay focused and clear.

Before thinking about your site’s colors, fonts, images, and content, you should answer these three basic questions about your website’s messaging and goals. The answers will guide you throughout your site design process and help insure your site is focused and will get the results you want.

1. Who is your target audience?

Sometimes the answer to this question is obvious, but in many cases it’s not. Often companies and organizations will offer a variety of goods or services which target different markets. It might be best to split your site into two very targeted sites rather than having one aimed at two separate markets, which would be confusing.

2. What is your tagline, in non-marketing speak?

Have you ever visited a corporate website, studied their home page, and still had no clue about what their product or service was? I see this all of the time. Often, there are two reasons for this.

  1. The website didn’t bother to mention it succinctly. Companies can be so wrapped up in the minute details of their products or services that they forget to mention, in basic language, what they actually do on a fundamental level. Or…
  2. Their tagline consists of marketing gibberish which is virtually meaningless, i.e., “Enterprise solutions that adapt to your business needs” or something like that. Don’t try to sound fancy. Explain your product or service in one sentence of plain English and make that your tagline! It’s what everyone will be seeing on your home page and in Google search results. (You should include search keywords in that tagline, but that is an entirely different conversation about SEO).

Your visitors should be able to tell what your company offers within ten seconds of visiting your site.

3. What is the number one thing you want your visitors to do on your site?

This is another seemingly obvious consideration that is often overlooked. Folks want their site to have the latest widgets and animation effects, but don’t consider the fundamental purpose of the site. Perhaps you want people to:

  • fill out a contact form
  • give you their email addresses for future communications
  • purchase your product or service via your online store
  • donate to your organization
  • sign up to volunteer
  • call your business’ land-line
  • come to your physical store

Make sure your call-to-action is clear, and that your site clearly guides people to that goal.

The End Goal

The goal of these questions is to make your site FOCUSED and CLEAR.  The message has to be really dumbed down. I’m not saying that your visitors are dumb, but they are busy and don’t have patience to decipher vague websites and messaging, and they’ll move to competitors who can communicate clearly.

So, stay laser-focused on keeping your messaging clear and your call-to-action prominent and simple on your website! – Brian

Which Web Hosting Company Should You Use?

Which Web Hosting Company Should You Use?

If you want to put your content on the Internet, you’ll have to choose a web hosting provider. This is the company that will store your website on a computer which is connected to the Internet and can serve it up to visitors.

If research hosting companies on the Internet, you’ll find so many conflicting opinions about hosting companies it will make your head spin. I’ve used all of the large hosting companies on dozens and dozens of websites.  Here are the companies that have the reliability, speed, and cost in my experience.

My Recommended Shared Hosting: SiteGround

For low-cost shared hosting suitable for most small business and small nonprofits, I recommend SiteGround. When I migrated all of my personal WordPress blogs from a big-name competitor to SiteGround (I used the “GoGeek” shared hosting plan), I noted the load times before and after. On average, the load time was cut in half from around 5 seconds to a little over 2 seconds with SiteGround! After that, my sites were a joy to use and maintain.

Web Hosting

They also offer some perks like powerful caching (which makes your site even faster), and free Let’s Encrypt SSL certificates, which provides additional security for your site, and is indicated by a green lock in the browser bar. They also offer easy staging site generation and backups.

Another important factor is customer service. Last time I had to talk to them, I was able to get a real person on chat in about a minute. She was able to solve one of my problems right away. She created a ticket for my other one, which was solved in about ten minutes.

These are the reasons why I’m a huge fan of SiteGround! They are perfect for small to medium traffic sites (100,000 visitors per month of fewer).

SiteGround is based in Sofia Bulgaria (although they have data centers around the world).

My Recommended Managed WordPress Hosting: WP Engine

If you need a more premium WordPress hosting solution, I would recommend WP Engine. Yes, they’re more expensive, but their servers are insanely fast and they offer really easy staging sites, backups, along with all of the amenities that SiteGround offers.


WP Engine is based in Austin, TX. I’ve visited their headquarters and spoken with their employees there. I recommend them for high-end WordPress hosting, if you have the means.

My Recommended WordPress Cloud Hosting: Gridpane with Vultr

If you need more powerful, scalable, hosting, you’ll probably look to a cloud hosting solution like Amazon Web Services (AWS), Digital Ocean. However, these companies provide unmanaged servers, meaning you’ll need sysadmin expertise (or an IT person) to set up and maintain your servers.

One solution is to use a hosting control panel service on top of your cloud hosting. This provides a slick interface to your server with simple controls to create servers, install WordPress, set up SSL, and so forth, so you don’t need to do any command-line work to set up your servers. Unless you’re a server expert, these are worth every penny!

Gridpane is my recommended WordPress control panel. Gridpane is specifically geared to WordPress hosting only, so they’ll take good care of your sites. I use them along with servers from Vultr, which provides super-fast cloud hosting (check out this speed comparison).

My Recommended Domain Name Hosting

If you’re starting a website, you’ll need a domain name. I recommend Namecheap. They have great prices and are highly rated in the industry.

Do not purchase your domain name from your web hosting company. Someday, you might want to move your web hosting and you’ll have to go through the painful process of moving your domain name as well if you want to be free of them.

Companies to Avoid

I don’t want to mention any hosting companies by name, but many of the most well-known hosting companies cram so many users on a single server that the sites on them are as slow as molasses. If you message me privately I can steer you clear of these. Unfortunately, some of the largest, most popular hosting companies are now among the worst.

I hope this has helped! – Brian

Note: I receive compensation from service providers when you purchase through the affiliate links (at no extra cost to you). I test and/or research each service thoroughly before endorsing it. I own this site and the opinions expressed here are mine.

WordPress vs. Wix, Weebly, and Squarespace

WordPress vs. Wix, Weebly, and Squarespace

One question I sometimes get from clients is whether they should use WordPress or one of the online website builder services like Wix, Weebly, and Squarespace. Unlike some web developers (and designers), I believe those services can be the right choice in some situations.

Just to be clear though, when I mention “WordPress” in this article, I’m talking about hosting it on your own hosting, not at WordPress.com. WordPress.com is a all-in-one hosting service similar to Wix, Weebly, and Squarespace.  More on this in my article, What is WordPress?

When I mention “website builder services”, I’m talking about services like Wix, Weebly, and Squarespace.

When a Website Builder Service (Wix, Weebly or Squarespace) Can Be the Right Choice

Some web designers and developers like to disparage services like Wix, Weebly, and Squarespace. But honestly, the quality of the templates provided by these services has risen dramatically, to the point where sites based on these services look very modern and are mobile-friendly. So, the previous argument that these sites didn’t look good just isn’t true anymore.

Here are some situations where using a website builder service might be a good choice:

  • You have limited budget and web development experience
    Unless you create your WordPress site yourself, these builders will get your site up and running for very low cost compared to hiring a web developer to set up a WordPress site.
  • Your site is purely informational without unusual functionality. 
    If you are a small business that just needs an informational website, hiring a web developer to create a site might be overkill. There’s nothing wrong with using a website builder service in this case.
  • You don’t want to worry about site maintenance
    WordPress sites require maintenance in the way of updates to the core, theme, and plugins. Plus, you’re responsible for backing up your site and restoring it if it gets hacked. If you use a builder service, they will do all of these functions for you.

When Site Builder Services Are Not the Right Choice

Here are cases where site builder services probably won’t cut it:

  • You want a full custom design
    Site builder services are limited in how much you can modify the design of the site. If you want full control over your site’s appearance, don’t use a site builder service.
  • You need special functionality not offered by the website builder services
    If you need to interface with an API or have some feature on your site not offered by the builder services, you’ll have to look elsewhere. WordPress has tons of plugins to do almost anything under the sun.  If you can’t find what you need in a plugin, a programmer can probably do it for you.
  • You want to save on monthly fees
    While site builder services don’t have an up-front development cost (except for your time), they do charge monthly fees.  Hosting a WordPress site has fees as well, but they are slightly less for the equivalent hosting.
  • You want to tinker
    If you enjoy tinkering with the nuts and bolts of your site, a self-hosted solution like WordPress will give you much more freedom.

If any of these are true in your situation, WordPress might be a better alternative than one of the online website builders.

My other caveat about “do-it-yourself” builder services is that although they are marketed as being easy to use, they actually do have a significant learning curve. If your time is very valuable or scarce, you might be better off hiring a developer than spending your time learning how to use these builders.

I hope this has helped you understand when site builder services might work for you, and when they won’t.  Please leave your questions below in the comments! – Brian

What Is WordPress? A Guide For Absolute Beginners

What Is WordPress? A Guide For Absolute Beginners

WordPress is free software that lets you create a website using pre-made templates and plugins, and it allows you to update content by logging into the site and typing in a text editor. This allows you to create professional-looking sites and update the content yourself, without writing code (as long as the features you need are not too specialized).

In technical terms, WordPress is a “content management system” (CMS).

WordPress started out as blogging software but is now used in many other kinds of websites. It is the most widely-used website content-management system in the world.  It has been estimated (as of 2017) that WordPress powers 20% of the websites in existence.

WordPress.org vs. WordPress.com

Before I go any further, I want to sort out one of the most confusing things about WordPress: the difference between WordPress.com and WordPress.org.

WordPress.org is where you can get the free WordPress software, but you need to have a place to put it, namely, web hosting from a provider such as GoDaddy, Inmotion, WP Engine, SiteGround, or many others.  You’ll need to get a domain name (URL) as well.

WordPress.com is a fully hosted service.  You can sign up for a WordPress site there, and you don’t need to worry about hosting it or getting a domain name (you can get one in the “wordpress.com” domain).  It’s kinda like Squarespace or Wix, where you just sign up and instantly you have a live website.  The downside is that your choices of themes is limited, and there are many other limitations to what you can do on your site. If you’re doing a personal blog though, it’s probably fine.

In this site, when I say “WordPress”, I’m usually referring to the first case, namely, WordPress software hosted on your hosting provider, not on WordPress.com.  When most people talk about WordPress, that’s usually what they are talking about, not the hosting service.

The Benefits of Using WordPress

OK, back to the fun stuff. Here are some of the reasons why so many people, companies, and organizations use WordPress for their sites:

  • Tons of themes available. Themes determine the “look” of your site.  There are themes specifically for restaurants, churches, photographers, design firms, corporations, and many other niches.
  • Tons of plugins available.  Plugins add functionality to your site, such as e-commerce, photo galleries, events management, forums, membership, and much more.
  • Ability to edit without writing or understanding HTML code. Text editor is similar to Microsoft Word.  No need to hire a programmer every time you want to change the content of your site.
  • Huge installed base means lots of support in the form of online help (just Google the problem you’re having), meetup groups, freelance contractors, training programs and annual WordPress gatherings called Word Camps.
  • It’s a mature, stable, platform that is constantly being updated with new features and security fixes.
  • It’s flexible, enabling programmers to create custom themes and plugins suited to your specific needs.

The Downsides of WordPress

No content management system is perfect for all applications. Here are some of the downsides of WordPress:

  • Because WordPress is so popular means it’s a target of hackers and bots.
  • It requires maintenance. The WordPress core, themes, and plugins require regular updates for security fixes.
  • You need to have a backup strategy, in the form of manual backups, an automatic backup plugin, or automatic server backups provided by your host.  Otherwise, if your site is hacked or your server drive dies, your site could be lost forever.
  • The fact that there is a database means that a WordPress site will load slightly slower than a pure HTML site (but there are some things you can do to mitigate this issue, like installing a caching plugin).

There are many other pros and cons which require a greater understanding of how websites work, but I believe these are the biggest issues.

What WordPress Is Good For

WordPress can be used to create almost any kind of site.  Here are a few categories that it is especially well suited for:

  • Corporate or nonprofit informational sites
  • Portfolio sites
  • e-Commerce sites
  • Events management sites
  • Membership sites
  • Sites that store information in the form of custom post types and taxonomies (for example, if you have an dog rescue service and you want to display the name, breed, color, age, etc. for a large number of dogs).
  • Blogs

WordPress can be used for many other types of sites!

What WordPress Isn’t Good For

  • Super high-security websites like banking sites
  • Super high-performance websites, where there are extremely high numbers of visitors at the same time (i.e., like the NFL website during the Superbowl).
  • “One page websites”, i.e., web apps where the whole site loads at once instead of having individual pages loaded from the server as they are visited.

I hope this short introduction has helped you understand what WordPress is, and its strengths and weaknesses. Please leave any questions in the comments! – Brian