How To Reduce CPU Usage In WordPress (Bandwidth Limits)

How To Reduce CPU Usage In WordPress (Bandwidth Limits)

I had serious issues with CPU overages on my WordPress site.

All this means is we need to reduce the amount of resources consumed by high CPU plugins, images, wp-cron, databases, external requests (usually generated by plugins), comment spam, and prevent spammy bots from crawling your website using the Blackhole For Bad Bots plugin.

We will also utilize Cloudflare’s CDN, remove bloat from the WordPress admin using Clearfy and Hide SEO Bloat, then test common settings in cache plugins that often consume high CPU.

When you’re done, hopefully your CPU graph looks like this:

By reducing CPU usage, you will be putting less stress on your server, making your site faster. Hosting companies want you to upgrade your plan which does work since you will be getting more server resources, but you should try these alternatives before reaching into your pocket.

If you’re using slow hosting like EIG or GoDaddy, I would seriously reconsider. I use SiteGround who is also used by Yoast, recommended by WordPress, and was #1 in 20+ Facebook polls. I’m on their semi-dedicated GoGeek plan and  not only are my server response times well under 200ms, but my GTmetrix report is pretty much unbeatable. They will also migrate you for free.


1. Check CPU Usage In AWStats

AWStats is built-in to most cPanels (SiteGround, Bluehost, GoDaddy) in their “statistics” section and can help identify the source of high CPU. It tells you how much bandwidth specific elements are consuming including unknown bots, images, pages, files, downloaded files, etc.

AWStats helps you find:

  • Total bandwidth usage
  • High bandwidth crawlers
  • High bandwidth IP addresses
  • High bandwidth download files
  • High bandwidth files (eg. images)


If unknown bots are consuming CPU, try blocking spam bots with Blackhole For Bad Bots.


If images are consuming high CPU, use GTmetrix to find which images need to be optimized. Serve scaled images, compress them with ShortPixel, and use Cloudflare’s hotlink protection.


Server Response Time
High CPU can also lead to slow response times, which you can test in Bitcatcha or PageSpeed Insights. Google says it should be under 200ms. Of course, this is mostly controlled by hosting.

Bitcatcha Server Speed Report


2. Eliminate High CPU Plugins

These resource-hungry plugins are CPU killers.

High CPU plugins usually include social share, statistic, chat, calendar, page builders, backup, and plugins that run ongoing scans/processes or show multiple times in your GTmetrix report.

  • AdSense Click Fraud Monitoring
  • Backup Buddy (use UpdraftPlus)
  • Better WordPress Google XML Sitemaps (use Yoast)
  • Broken link checker (use Dr. Link Check)
  • Constant Contact for WordPress
  • Contact Form 7 (load JS + stylesheet only when necessary)
  • Contextual Related Posts
  • Digi Auto Links
  • Disqus Comment System (use Disqus Conditional Load)
  • Divi Builder
  • Essential Grid
  • Fuzzy SEO Booster
  • Google XML Sitemaps (use Yoast)
  • Jetpack
  • NextGEN Gallery
  • NewStatPress
  • Pods
  • Reveal IDs
  • Revolution Slider
  • S2 member
  • SEO Auto Links & Related Posts
  • Similar Posts
  • Slimstat Analytics
  • SumoMe
  • Talk.To
  • VaultPress
  • WooCommerce
  • WordPress Facebook
  • WordPress Related Posts
  • WordPress Popular Posts
  • WP Bakey (formerly Visual Composer)
  • WP Statistics
  • WP-PostViews
  • WP Power Stats
  • wpCloaker
  • WPML
  • Yet Another Related Post Plugin
  • Yuzo Related Posts

Find Slow Loading Plugins
If the same plugin appears multiple times in your GTmetrix Waterfall report, you may want to find an alternative plugin that is more lightweight. External requests can also destroy your report (eg. from Google Fonts, Gravatars, AdSense, and the high CPU plugins I mentioned).


Query Monitor
Query Monitor shows your slowest plugins, scripts, styles, queries, hooks, PHP errors, and a wealth of information to pinpoint speed issues. This may require some technical knowledge, but it’s worth hiring a developer who can make optimizations with the help of Query Monitor.



3. Remove Bloat With Clearfy

By “bloat” I am referring to the heartbeat API, autosaves, post revisions, pingbacks, and all the “miscellaneous” things that consume resources and should be disabled for most sites. The top 3 plugins to disable these are Clearfy (recommended), perfmatters by Kinsta, and WP Disable.

Option 1: Clearfy

Clearfy Performance Settings

Clearfy Defence Settings

Clearfy Advanced Settings

Option 2: Perfmatters By Kinsta ($25/Year)

perfmatters settings

Option 3: WP Disable






4. Disable WP-Cron

The wp-cron is loaded on every page load and schedules automated tasks like publishing scheduled posts, checking for theme and plugin updates, and sending email notifications. Instead of running it on every page load, you can schedule it to run every 90 minutes or so.

Step 1: Disable WP Cron Jobs

Add the code to wp-config.php, before where it says “That’s all, step editing! Happy blogging.”

define('DISABLE_WP_CRON', true);

Step 2: Replace With A Real Cron Job
You still need wp-cron (eg. checking for theme/plugin updates), just not on every page load. Each host has their own instructions for this, here is SiteGround’s tutorial. You can set the cron job to run every 90 minutes, or increase it even more if you don’t have lots of scheduled tasks.


5. Clean Your Database

Deletes post revisions, spam, trash, transients, and database tables that accumulate overtime are often left behind when you uninstall plugins… making your site slower with higher CPU.

You should clean these at LEAST once a month using WP Rocket or WP-Optimize. They have similar settings with an automatic cleanup option (I highly recommend enabling this) but I like WP Rocket since it was rated the #1 cache plugin in this Facebook poll and has options for database cleanup + lazy loading images/videos/iframes. Most other cache plugins don’t have these extra options which means you also need to install WP-Optimize and a lazy load plugin.



6. Upgrade To PHP 7+

About 50% of WordPress users run PHP 5.6 or lower:


When upgrading to PHP 7+ can process requests almost 3x faster:


SiteGround (and most hosts) have an option to upgrade in their cPanel:


I recommend PHP 7.2:


The last step is to check your website for errors. If you see any, run the PHP Compatibility Checker to make sure your plugins are compatible. Poorly-maintained plugins may not be.


7. Offload Resources To CDNs

CDNs reduce the load on your server by offloading resources to their data centers. Each CDN has their own set of data centers, and more data centers = more offloading (and faster delivery of your content). I use both Cloudflare (free) and StackPath ($10/month with free 30-day trial).

Cloudflare offloads resources to their 150+ data centers:



Sign up for Cloudflare, add your site, and run the scan. You’ll come to a page where Cloudflare assigns you 2 nameservers. Then in your hosting account, change nameservers to Cloudflare’s.

Cloudflare Nameservers

StackPath offloads resources to 31 additional data centers:


Step 1: Sign up for StackPath (they have a 30-day trial).

Step 2: In the dashboard, click the CDN tab, then create a StackPath CDN Site:




Step 3: Copy your CDN URL and paste into your cache plugin (you can also use CDN Enabler).


Step 4: In StackPath go to CDN → Cache Settings, then click Purge Everything…


Step 5: Run your site in GTmetrix and “content delivery network” should be green in YSlow.

CDN GTmetrix YSlow


Hotlink protection can be enabled in Cloudflare (or sometimes your hosting account). This prevents people from copying/pasting your images onto their own website, which sucks up bandwidth. This usually happens if you have high quality images on your site (eg. photography).

Cloudflare Hotlink Protection


9. Block Bad Bots

In AWStats, you might see bots + spiders consuming a lot of bandwidth. Obviously we don’t want to block Googlebot and other legitimate crawlers, but we do want to block spammy ones.


Step 1: Install Wordfence.

Step 2: View Your Live Traffic Report (in Wordfence’s Tools settings) which shows you all bots hitting your site in real-time. Googlebot is obviously OK, but when I observed mine, I saw was making a ridiculous amount of requests every couple seconds. I Googled it and sure enough, this was a bot known for sucking up bandwidth. View your report for a minute or two and see if bots with sketchy names are constantly hitting your site. If you have doubts, Google their hostnames and see if other people are having issues with that bot.


Step 3: Block Bad Bots (3 Options): Wordfence, Blackhole For Bad Bots, or Cloudflare Firewall Rules. Wordfence itself can cause high CPU (I recommend one of the other options).

Wordfence – Go to the Blocking settings and add the spam bots you wish to block. Asterisks serve as wildcards, so if I block ** it means any hostnames containing (whether it has characters before or after it), that bot will be blocked. I have saved thousands of requests/bandwidth just by blocking these two spammy hostnames:

  • *
  • *


Blackhole For Bad Bots – adds a hidden link to your pages that forbids all bots from following the link. If a bot disobeys it, they are blocked. Googlebot and other good bots are whitelisted.

Blackhole for Bad Bots

Cloudflare Firewall Rules – Cloudflare lets you create up to 5 firewall rules for free. Copy the hostnames of the most common bad bots (found in your live traffic report) and add them here.

Cloudflare Firewall Rule To Block Bad Bots

Step 4: Go to your Blocking log and enjoy watching those spam bots get blocked.


Step 5: If you do decide to use Wordfence, configure rating limiting settings. This limits/blocks crawlers (and humans) from making excessive requests, blocks fake Google crawlers, and improves security on 404 pages. These are the same settings recommended by Wordfence:


Be sure to tweak the Wordfence “options” tab to limit bandwidth consumed by this plugin:

  • Do not “enable automatic scheduled scans”
  • Do not “enable email summary”
  • Enable “use low resource scanning”
  • Decrease “limit the number of issues sent in the scan results email” to 500
  • Do not enable “updates needed (plugin, theme, or core)”
  • Increase “update interval in seconds (2 is default)” to 10-15 seconds
  • Decrease “how much memory should Wordfence request when scanning” to 100MB
  • Enable “delete Wordfence tables and data on deactivation”
  • View Wordfence’s options page for more recommendations


10. Optimize Images

Images can consume lots of bandwidth, as shown in AWStats:


There are 3 ways to optimize images in GTmetrix.


  • Serve scaled images – resize larges images to be smaller
  • Specify image dimensions – specify a width/height in the HTML or CSS (screenshot)
  • Optimize images – losslessly compress images (I recommend ShortPixel or Imagify)

Start by optimizing images that appear on multiple pages (logo, sidebar, footer images). Then run your most important pages through GTmetrix and optimize individual images on those. The first item you should work on is “serve scaled images” since this requires you to scale (resize) an image to the correction dimensions, upload the new version to WP, and replace it.


11. Common Fixes In WP Rocket

WP Rocket says:

Occasionally some of the options on the File Optimization tab, such as Remove Query Strings, or Minify/Combine can cause high CPU usage in cases where your site has a lot of CSS or JS files. Try disabling these options and then monitor your CPU usage.

There have also been reports that critical path CSS and preloading can increase CPU. You can use a plugin to increase the preload crawl interval from 500ms (the default) to 1.5s or higher.


12. Common Fixes In W3 Total Cache

Common CPU solutions for W3 Total Cache:

  • Test object cache
  • Delete and reinstall the plugin


13. Configure Optimal Cache Plugin Settings

These 3 are all very important:

  • If you’re using a cache plugin
  • Which cache plugin you’re using (I recommend WP Rocket)
  • Whether the settings are configured optimally (some can cause high CPU)

Why WP Rocket?
It has more features than most cache plugins, which means you don’t need to install extra plugins for these, while giving you better results. Otherwise you will need to research which features your cache plugins comes with, then install these plugins if it doesn’t support them:


If you can drop $49 on WP Rocket, buy it then see my WP Rocket tutorial. It’s easy to setup, updated frequently with new features, includes documentation, and support. If not, I have tutorials for Swift, WP Fastest Cache, W3 Total Cache, WP Super Cache, and Autoptimize. For free plugins, I recommend Swift or WP Fastest Cache (Swift is a tricky to setup but has great reviews in the WordPress Speed Up Facebook Group and comes with most features as WP Rocket, while WP Fastest Cache is easy to setup but lacks features included with WP Rocket).


Some hosts like GoDaddy and WP Engine blacklist cache plugins because they have their own built-in caching system. In this case, use Autoptimize to optimize HTML, CSS, and JavaScript. It also has a CDN option. See my Autoptimize tutorial, otherwise if your host doesn’t blacklist cache plugins, I recommend either WP Rocket or Swift.

You can also try disabling your cache plugin and checking CPU usage. If your cache plugin is indeed causing issues, reach out to the plugin developer (or switch plugins).


14. Delete Unused Plugins + Themes

Unused themes store preconfigured settings in your WordPress database (similar to plugins). Go to Appearance > Themes then delete all the WordPress themes you’re not currently using.



15. Disable Unused Settings In Plugins

Just like we tweaked Wordfence’s settings to reduce CPU usage created by the plugin, go through each one of your plugin settings and decide whether you need individual features. For example, in Yoast under Settings > General > Features I disabled all of the following…


Disable plugin settings that:

  • Provide statistics
  • Run ongoing scans
  • Send admin or email notifications
  • Pull resources from external websites


  • WP Rocket’s preload bot
  • Wordfence’s live traffic reports
  • Broken Link Checker’s ongoing scans
  • Yoast’s settings under Dashboard > Features
  • Chat and calendar plugins that run constantly
  • Statistical plugins that constantly collect data
  • Related post and popular post plugins that store tons of data


16. Block Comment Spam

An ongoing accumulation of spam comments isn’t good for your CPU usage. The Anti-Spam plugin has always work well for me (I tested plenty of others) and it doesn’t use CAPTCHA.


17. Protect Your WP-Admin

Attacks are commonly targeted at the WordPress admin, which is not only a security threat, but will consume high amounts of CPU especially since these pages aren’t usually not cached.



18. Minimize External Requests

External requests are hard on the server.

  • Gravatars
  • Google Fonts
  • Google Maps
  • Google AdSense
  • Some Social Sharing Plugins
  • Many others from my list of high CPU plugins

Often times, these will be very noticeable in your GTmetrix report:



Step 1: Eliminate Them If Possible

Step 2: Optimize Them

Step 3: Prefetching DNS Requests
Some cache plugins like WP Rocket let you prefetch DNS requests (as well as perfmatters and WP Disable). This helps browsers anticipate external resources so they can load them faster. Luke created a nice list of common domains to prefetch which you can then add to WP Rocket:




19. Limit Crawl Rate By Google + Bing

Google is usually the most resource-hungry crawl bot (by far) and you can limit their crawl rate in the “site settings” section of Google Search Console. This lowers the requests made by Googlebot and does NOT affect your rankings or penalize you in any way. Unless you run a news website or publish time-sensitive content (and you have a hosting plan with sufficient resources), you don’t need Google crawling your site quickly and consuming tons of resources. Websites struggling with CPU usage should lower this – keep in mind it resets every month.


Google says this on their crawl rate page…

“If Google is making too many requests per second to your site and slowing down your server, you can limit the crawl rate… we recommend against limiting the crawl rate unless you are seeing server load problems that are definitely caused by Googlebot hitting your server too hard… you canot change the crawl rate for sites that are not at the root level.”

You can do the same thing with Bing Webmaster Tools in the crawl control settings…



20. Avoid Resource-Hungry Themes

Bloated, poorly coded, and non-maintained themes are a recipe for disaster.

Instead of using a theme with tons of built-in features, use a lightweight (minimal) theme and rely on plugins to only add functionality you absolutely need. I always recommend StudioPress along with their Genesis Plugins which is what I use on my own site. Yoast also uses Genesis.



21. Disable Resource-Hungry WooCommerce Features

WooCommerce sites naturally require more CPU. This is something to keep in mind when choosing your hosting plan, and you should ideally not be using shared hosting.

Optimizing Woocommerce

  • Disable WooCommerce cart fragments
  • Disable WooCommerce scripts and styles
  • Disable WooCommerce widgets
  • Disable WooCommerce status metabox
  • Disable automatic product feed plugins

Most of these can be done using the perfmatters plugin.

perfmatters woocommerce optimization


22. Host Download Files On External Websites

I barely have any files to download on my website so the bandwidth is low enough where I don’t worry about this. But if you have tons of large files that suck up bandwidth when people download them, consider uploading them to Dropbox or another file sharing website and pointing people there. That way will be handling the bandwidth and not you.



23. Disable AWStats + cPanel Statistics

AWStats, Webalizer, and other statistical programs in the cPanel are good for identifying the source of high CPU usage, but these actually increase CPU just like any WordPress plugin that collects statistics. All I’m saying is that when you’re done using these, you should delete them.


24. Turn Off SiteGround’s Site Scanner

If you’re getting CPU overages on SiteGround and you paid for their SG Site Scanner, try contacting their support team to turn this off. The ongoing scans may be causing high CPU.


As nice as these emails are, you should try turning this off…



25. Use A Hosting Plan With Sufficient Server Resources

Generally, the higher the plan the more server resources you get (and yes, upgrading should cure CPU overages/bandwidth limitations). For example on SiteGround’s features page you can see how many server resources come with their StartUp vs. GrowBig vs. GoGeek plan. Just scroll down to the “we allocate the resources you need” and look under the server tab…



26. Upgrade CPU/RAM

Make sure you have enough RAM so you’re not always on the edge of your limit. If it’s almost always maxed out, this puts stress on your CPU. You want to have enough resources so your server is relaxed. In this case, the 2GB of RAM was almost always maxed out, so upgrading to 4GB was a smart move. Most shared plans don’t let you add RAM (you’ll need to upgrade to a plan that includes more resources) but you can usually add them on most cloud hosting plans.



SiteGround (#1 Host In Facebook Polls)

SiteGround is used by Yoast, myself, and recommended by WordPress. They are #1 in nearly every Facebook poll and give most people significant load time improvements especially if they were using mediocre hosts: GoDaddy, Bluehost, HostGator, InMotion, Dreamhost, EIG.


I use their semi-dedicated GoGeek plan which comes with 4x more server resources than shared hosting. Click through my pages to see how fast they load, check out my GTmetrix report, or see people who migrated and posted new load times. They also do free migrations.

DigitalOcean on Cloudways and Kinsta are also good and start at $10/month and $30/month. Cloudways is more for developers who don’t need cPanel, email hosting, or the support you get with SiteGround. Kinsta is basically what WP Engine used to be (pricey, but awesome). My entire blog is basically dedicated to helping people make their website load faster. I refuse to recommend $2/month hosting since it’s most people’s biggest regret when running a website.

How To Check If Your Hosting Is Slow
Run your site through Google PageSpeed Insights to see if reduce server response time is in your report. Google recommends it should be <200ms. Anything above 1 second is not good. You can also check your TTFB (time to first byte) in GTmetrix’s Timings tab or


2019 Hosting Poll

SiteGround is recommended by WordPress:


And by Ivica who runs the WordPress Speed Up Facebook Group with 16,000+ members.

WordPress-Speed-Up Recommended Tools

A few threads:

Godaddy To SiteGround Migration



SiteGround has 3 plans:

SiteGround Hosting Plans

Higher plans include more server resources (#1 factor in the WordPress optimization guide). Here’s the full comparison chart, but GrowBig gives you about 2x more server resources than StartUp, and GoGeek is semi-dedicated hosting which gives you even more. GrowBig and up comes with a free migration, staging, advanced caching, and ability to host multiple websites. GoGeek comes with priority support. Their cloud hosting is quite the price jump at $80/month.

You can see this on their features page:


I use SiteGround because:

  1. My GTmetrix + Pingdom reports speak for themselves
  2. My pages load instantly (click through them if you want)
  3. Fast speed technology (PHP 7.3, NGINX, SG Optimizer, Cloudflare)
  4. Recommended by Yoast, WordPress, Ivica from WordPress Speed Up
  5. Free Let’s Encrypt SSL, easy to use cPanel, and features for eCommerce
  6. WordPress support is unbeatable even without GoGeek’s priority support
  7. GrowBig comes with staging, more storage, and more server resources (scroll down to “we allocate the resources you need” and hover over the server tab)
  8. GoGeek comes with even more server resources, storage, priority support
  9. Free migrations, migrator plugin, and a 30-day money back guarantee
  10. Plenty of praise on Reddit, Facebook conversations, Twitter, TrustPilot
  11. Tons of praise on Facebook: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11
  12. Many people already migrated and posted results on Twitter: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12, #13, #14, #15, #16, #17, #18, #19, #20, #21, #22, #23, #24, #25, #26, #27, #28, #29, #30, #31, #32, #33, #34, #35, #36, #37

Affiliate Disclaimer – if you sign up for SiteGround with my affiliate link I will donate a good chunk at no expense to you. Each year I donate $3k to GoFundMe campaigns (2018 was to feed the hungry in Denver, 2017 was to Red Cross at Hurricane Harvey). Your support helps and I genuinely appreciate it. I try to make my reviews unbiased and backed by evidence in the form of Facebook polls, tweets, and real conversations. If you don’t want to use it, here’s a non-affiliate link to SiteGround. Either way I truly believe they are a stellar WordPress host and your site will run faster/smoother… do your research on Facebook groups + Twitter and you’ll find most people say the same.


People usually migrate because their speed technology can cut load times in half:


Hire My Developer To Reduce Your CPU Usage

I’ve been working with the same guy since 2011 – he is amazing at speed optimization and helped me optimize my site to load in <1 second with great GTmetrix and Pingdom reports.

His name is Pronaya and he should be able to solve your CPU overages (if you still need help) and help you improve scores/load times in GTmetrix and Pingdom. You can hire him by creating a profile on and searching for username bdkamol. Here is his full WordPress speed portfolio. He’s $40/hour from Bangladesh (so there is a time change) and you can email him at [email protected]. He also has a perfect 5 star review on his profile.


You can also consider posting your problem in the WordPress Speed Up Facebook Group if you want feedback from people who have already been through the problem of high CPU, but I have covered the most common solutions throughout this tutorial.


Frequently Asked Questions

What are the easiest ways to reduce CPU in WordPress?

The easiest ways to reduce CPU include eliminating high CPU plugins, upgrading to PHP 7+, configuring a good cache plugin with optimal settings, using a CDN, and installing the Heartbeat Control plugin. Upgrading to faster hosting will also reduce CPU, especially if you’re using a low quality host like GoDaddy, Bluehost, or HostGator.

Which plugins consume the most CPU?

Most high CPU WordPress plugins include social sharing, statistic (analytics), sliders, portfolios, page builders, calendars, chat, contact forms, related post, sitemap, Wordfence, WPML, and any plugin that runs ongoing scans or processes. These can be found using Query Monitor or GTmetrix Waterfall.

Does all shared hosting have CPU limits?

Yes. Even though some shared hosting companies claim to have unlimited bandwidth, they still enforce CPU limits. This is usually found in their terms are conditions.

Does WooCommerce cause high CPU?

WooCommerce sites generally require more plugins, and often times, more CPU. If these are not selected carefully, the resources consumed by those plugins can put stress on your server. WooCommerce sites also load extra scripts, styles, and cart fragments which don’t help either.

How can I check my website’s CPU consumption?

Your hosting account should tell you how much CPU you’re consuming. Some hosts have tools like AWStats which show specific images, bots, and other resources that consume lots of resources.

Let me know if this tutorial worked in the comments!

See Also: How I Optimized My WordPress Site To Load In <1s (38+ Tips)


span,.wp-review-36413.wp-review-percentage-type .review-list li>span{display:inline-block;position:absolute;z-index:1;top:32px;left:45px;color:#ededed;font-size:14px;line-height:1;text-shadow:0 1px 1px rgba(0,0,0,.3);-webkit-touch-callout:none;-webkit-user-select:none;-khtml-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.wp-review-36413.wp-review-point-type .wpr-user-features-rating .review-list li>span,.wp-review-36413.wp-review-percentage-type .wpr-user-features-rating .review-list li>span{color:inherit;text-shadow:none}.wp-review-36413.wp-review-point-type .wpr-user-features-rating .review-list li .wp-review-input-set+span,.wp-review-36413.wp-review-percentage-type .wpr-user-features-rating .review-list li .wp-review-input-set+span,.wp-review-36413.wp-review-point-type .wpr-user-features-rating .review-list li .wp-review-user-rating:hover+span,.wp-review-36413.wp-review-percentage-type .wpr-user-features-rating .review-list li .wp-review-user-rating:hover+span{color:#fff}.wp-review-36413 .review-list li:nth-child(even){background:#fff}.wp-review-36413 .review-links{padding:30px 30px 20px 30px} .review-result-wrapper i{font-size:18px} .review-pros-cons{clear:both;padding:0;border-top:1px solid #fff} .review-pros-cons .review-pros, .review-pros-cons .review-cons{width:100%;flex:none;padding:0} .review-pros-cons .review-pros{background:#2c3fd3;padding:30px 30px 10px 30px;color:#fff;box-sizing:border-box} .review-pros-cons .review-cons{background:#5e1d9a;padding:30px 30px 10px 30px;color:#fff;box-sizing:border-box} .mb-5{text-transform:uppercase} .mb-5+p{line-height:26px}.wp-review-36413 .user-review-area{padding:15px 30px;border-top:1px solid}.wp-review-36413 .wp-review-user-rating .review-result-wrapper .review-result{letter-spacing:-2.35px} .review-title{letter-spacing:1px;font-weight:700;padding:15px 30px;background:transparent} .review-total-wrapper{width:40%;margin:0;padding:35px 0;color:#fff;background:#ededed;border-left:1px solid;text-align:center;float:right;clear:none;border-top:1px solid} .review-list{clear:none;width:60%;float:left;border-top:1px solid} .wpr-user-features-rating, .wpr-user-features-rating .review-list{width:100%;clear:both;border-top:1px solid #fff} .review-total-wrapper{padding:20px 0} .review-total-wrapper{margin:auto 0;padding-top:10px;width:auto;height:100%;clear:both} .user-review-area{padding:12px 30px} .review-list{width:100%} .review-result-wrapper{border-radius:25px} .review-percentage .review-result-wrapper, .review-percentage .review-result, .review-point .review-result-wrapper, .review-point .review-result{height:26px;margin-bottom:0;background:#fff;border-radius:25px} li .review-point .review-result{background:#5e1d9a} li:nth-of-type(2n) .review-point .review-result{background:#2c3fd3}.wp-review-36413 .review-total-wrapper,.wp-review-36413 .review-total-wrapper{width:70%;display:inline-block;margin:20px auto 0 auto} .review-total-wrapper .review-total-box{float:left;text-align:center;padding:0;color:#424242;line-height:1.5} .review-total-wrapper .review-total-box h5{margin-top:10px;color:inherit} .review-total-wrapper .review-total-box, .review-total-wrapper .review-total-box{width:100%}{color:#fff;margin-top:10px} .user-review-title{padding:15px 30px 10px;margin:0;color:inherit;background:#fff;border-top:1px solid;border-bottom:1px solid} .user-total-wrapper .user-review-title{display:inline-block;color:#424242;text-transform:uppercase;letter-spacing:1px;padding:0;border:0;background:transparent;margin-top:3px} .user-total-wrapper h5.user-review-title{margin-top:12px} .user-total-wrapper span.user-review-title{margin-top:8px} .reviewed-item{padding:30px} .review-total-wrapper>.review-total-box{display:block} .review-total-wrapper>.review-total-box>div{display:none} .user-review-area .review-percentage, .user-review-area .review-point{width:20%;float:right;margin-bottom:5px}.wp-review-36413 .review-embed-code{padding:10px 30px},.wp-review-36413 .review-title,.wp-review-36413 .review-list li,.wp-review-36413 .review-list li:last-child, .review-list,.wp-review-36413 .user-review-area, .review-total-wrapper,.wp-review-36413 .reviewed-item,.wp-review-36413 .review-links,.wp-review-36413 .wpr-user-features-rating, .user-review-title{border-color:#fff}.wp-review-36413 .wpr-rating-accept-btn{background:#5e1d9a;margin:10px 30px;width:-moz-calc(100% – 60px);width:-webkit-calc(100% – 60px);width:-o-calc(100% – 60px);width:calc(100% – 60px);border-radius:50px}@media screen and (max-width:480px){ .review-title, .reviewed-item, .review-list li, .review-desc, .user-review-area, .review-embed-code{padding:15px}.wp-review-36413.wp-review-circle-type .review-list li{padding:15px 15px 0 15px} .review-pros-cons>div>div{padding:15px;padding-top:0} .ui-tabs-nav{padding:0 15px} .review-links{padding:15px 15px 5px} .review-list, .review-total-wrapper{width:100%} .review-total-wrapper{padding:10px 0} .review-total-wrapper .review-total-box h5{margin-top:0} .review-total-wrapper .review-total-box div{line-height:1}}]]>

Keep reading the article at Tom Dupuis. The article was originally written by Tom Dupuis on 2019-06-10 10:25:50.

The article was hand-picked and curated for you by the Editorial Team of WP Archives.

Disclosure: Some of the links in this post are "affiliate links." This means if you click on the link and purchase the product, We may receive an affiliate commission.

Leave a Comment

Your email address will not be published. Required fields are marked *

Show Your ❤️ Love! Like Us
Scroll to Top