Title: Mobile Usability errors
Last modified: January 29, 2022

---

# Mobile Usability errors

 *  [jennyparker](https://wordpress.org/support/users/jennyparker/)
 * (@jennyparker)
 * [4 years, 4 months ago](https://wordpress.org/support/topic/mobile-usability-errors-2/)
 * **I have Mobile Usability errors in google console: **
 * [Error](https://www.dropbox.com/s/n4fw4s7uyoqpzoc/1.PNG?dl=0)Text too small to
   read
    Error Clickable elements too close together Error Content wider than screen
 * I have so far tried to increase the font using elemetor and just change the font
   for mobile devices but still the same results.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fmobile-usability-errors-2%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 7 replies - 1 through 7 (of 7 total)

 *  Thread Starter [jennyparker](https://wordpress.org/support/users/jennyparker/)
 * (@jennyparker)
 * [4 years, 3 months ago](https://wordpress.org/support/topic/mobile-usability-errors-2/#post-15312497)
 * Is there anyone here to help with this issue? I have been waiting for 2 days?
 *  [Herman Asrori (BSF)](https://wordpress.org/support/users/bsfherman/)
 * (@bsfherman)
 * [4 years, 3 months ago](https://wordpress.org/support/topic/mobile-usability-errors-2/#post-15347540)
 * Hi [@jennyparker](https://wordpress.org/support/users/jennyparker/),
 * **Text too small to read**
    Basically, Google considers a font size less than
   12 as not readable. You will have to check other font sizes as well that you 
   have set for the content on mobile.
 * Font sizes less than 12px are too small to be legible and require mobile visitors
   to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. 
   [https://web.dev/font-size/](https://web.dev/font-size/)
 * **Clickable elements too close together**
    Google’s recommendation is – Interactive
   elements like buttons and links should be large enough (48x48px), and have enough
   space around them, to be easy enough to tap without overlapping onto other elements.
   [https://developers.google.com/web/fundamentals/accessibility/accessible-styles](https://developers.google.com/web/fundamentals/accessibility/accessible-styles)
 * You will need to check the size in between elements on the page for the mobile
   view.
 * **Content wider than screen**
    I checked your site above on mobile view and didn’t
   see a [Horizontal Scrollbar](https://elementor.com/help/horizontal-scrollbar-on-mobile-devices/).
   I am not sure why Google warned you about this.
 * I hope it will help.
 * Kind regards,
    Herman 🙂
 * P.S. We recommend reaching out to us through our Support Portal for faster help
   and resolution as mentioned [here](https://wordpress.org/support/topic/read-this-first-17/).
 *  Thread Starter [jennyparker](https://wordpress.org/support/users/jennyparker/)
 * (@jennyparker)
 * [4 years, 3 months ago](https://wordpress.org/support/topic/mobile-usability-errors-2/#post-15352044)
 * Thanks, [@bsfherman](https://wordpress.org/support/users/bsfherman/) I just checked
   on the customization menu and custom CSS there is the only piece of code found
   that has 10 px so it changed to 13px and try to validate via google console but
   still not got validated?
 *  Thread Starter [jennyparker](https://wordpress.org/support/users/jennyparker/)
 * (@jennyparker)
 * [4 years, 3 months ago](https://wordpress.org/support/topic/mobile-usability-errors-2/#post-15352052)
 * **Clickable elements too close together**
 * I am still not sure why I am getting this error all clickable elements such as
   buttons and texts are already standard space from each other?
 *  [Herman Asrori (BSF)](https://wordpress.org/support/users/bsfherman/)
 * (@bsfherman)
 * [4 years, 3 months ago](https://wordpress.org/support/topic/mobile-usability-errors-2/#post-15391888)
 * Hi [@jennyparker](https://wordpress.org/support/users/jennyparker/),
 * You might want to try to temporarily switch to a default WordPress theme to check
   whether or not this is a theme-related issue. Maybe you can do this on a staging
   site as your site is a live site.
 * Kind regards,
    Herman 🙂
 *  Thread Starter [jennyparker](https://wordpress.org/support/users/jennyparker/)
 * (@jennyparker)
 * [4 years, 3 months ago](https://wordpress.org/support/topic/mobile-usability-errors-2/#post-15395310)
 * Thanks, [@bsfherman](https://wordpress.org/support/users/bsfherman/) for the 
   suggestion I will revert to the dfault theme and check the problem.
 *  [meistereder](https://wordpress.org/support/users/meistereder/)
 * (@meistereder)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/mobile-usability-errors-2/#post-15726664)
 * Hi there! [@jennyparker](https://wordpress.org/support/users/jennyparker/) It’s
   been a while since you’ve created this thread. Could you find a fix for the mobile
   usability messages?
 * I’m experiencing the same with a new website ([https://www.kinderhauszuffenhausen.de/](https://www.kinderhauszuffenhausen.de/))
   and have no clue whatsoever, what is leading to these messages. The website is
   using the latest WordPress 6.0 version and latest Astra Theme. Plugins: Yoast,
   Modula and WP Forms. Thanks for any suggestion!
 * Best,
    Meistereder

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Mobile Usability errors’ is closed to new replies.

 * ![](https://i0.wp.com/themes.svn.wordpress.org/astra/4.13.3/screenshot.jpg)
 * Astra
 * [Support Threads](https://wordpress.org/support/theme/astra/)
 * [Active Topics](https://wordpress.org/support/theme/astra/active/)
 * [Unresolved Topics](https://wordpress.org/support/theme/astra/unresolved/)
 * [Reviews](https://wordpress.org/support/theme/astra/reviews/)

## Tags

 * [Mobile Usability](https://wordpress.org/support/topic-tag/mobile-usability/)

 * 7 replies
 * 3 participants
 * Last reply from: [meistereder](https://wordpress.org/support/users/meistereder/)
 * Last activity: [3 years, 11 months ago](https://wordpress.org/support/topic/mobile-usability-errors-2/#post-15726664)
 * Status: not resolved