How I Fixed ‘Text Too Small’ Issue In Less Than a Minute (& You Can Too)

You write a new post on a very low-difficulty keyword, all excited waiting for it to rank, and boom! There comes an onslaught. The text is too small for mobile users.

And you’re like WHAT!? How come only this specific post has too small text while you have the same size font on other posts, and they are not causing any problem. 

The same was the case with me a couple of hours before writing this post. But, after a couple of hours of shouting at myself and Google, I finally figured it out.

And here’s what I did (and what you can too) to get rid of this annoying error.

Fix ‘text too small’ to read in less than a minute (in WordPress).

Log in to your dashboard and go to the plugins section.

Click add new and search “Autoptimize”.


After installation, don’t forget to activate. 

Now, go to the plugin’s setting and check the following boxes.

  • Optimize JavaScript Code.
  • Optimize CSS code.
  • Inline all CSS.

After it’s done, save the changes and head back to the mobile responsive test

Bingo! I passed, Hopefully, you will too.


Why does this happen?

There are two reasons why this can happen.

Reason #1.

The first one is obvious (and sorry I have to point it out because a lot of people misunderstand this warning) the text on your site is too small. 

And let me clarify, the warning is not only about the text of your blog, but the text on the whole webpage.

Maybe there’s a small text on your site’s footer that is less than 16px, or maybe there is something in your sidebar that looks small and hard-to-read on a tiny screen of a mobile phone.

More than 70% percent of the text on your website has to be larger than 16px. Only then your website will be considered friendly for mobile users.

I can’t tell you the exact reason because anything can be a problem for you and only you can catch the culprit here. 

Check your site’s code by pressing F12 key.

Find the text that is smaller than 16px and kick that out.

Reason #2.

If everything seems fine, the problem could be the code.

To crawl and index the web pages, Google sends these small bots known as Googlebot Smartphone. These small crawlers crawl through your website from page to page.

And they are very impatient. These bots don’t wait more than 5 seconds for CSS elements to load. 

Note: the time given above is approximate and not necessarily accurate. It’s because we don’t know exactly how long these bots stay on a page. I used 5 seconds because read it from somewhere.

In such circumstances, some critical CSS elements don’t get enough time to load properly. Which results in errors like these. 

In other words, your text is not small it’s just the code that the Googlebot couldn’t properly understand. 

To make sure the critical elements don’t get left out, you can find and take them out of the files and put them into the page’s header. 

This sounds too scary for a non-techy person like me, that’s why downloading the Autoptimize plugin is the easiest option. 


Upgrade your host. 

Note: I’m a proud affiliate of Hostinger. Which means if you use the link below to make a purchase I may earn a small commission with no extra cost to you.

I recommend Hostinger. As you get a free domain, SSL certificate, unlimited bandwidth, and 100GB storage, and most importantly, 99.9% guaranteed server uptime, all in just $2.59/mo.

There is 24/7 live support available, but still, if anything goes wrong, you can always get your money back with their 30 days money back policy.   

What are you waiting for? Head over to Hostinger and enjoy the lightning-fast website speed.

I hope it answers your question. If something is hard to digest for you, let me know in the comments, I’ll try my best to help you out.

Sharing is caring!

Leave a Reply