Welcome to the Question2Answer Q&A. There's also a demo if you just want to try it out.
+1 vote
1.4k views
in Q2A Core by
Google find the website not mobile friendly but the mobile test tool says the website is mobile friendly
Q2A version: 1.8.3 bugfix
by
Cleanstrap does not have these errors I just stopped using it because it is no longer updated. I used snow flat on both websites.
by
Please confirm that "cleanstrap" theme did not cause the "Clickable elements too close together" error.  Because you had said:  "I think this was caused by cleanstrap since it overrides some q2a functions . "
by
Yes it did not caused the problem. The reason I'm getting this error on my end is because cleanstrap did overrided some q2a function which resulting snowflat to use some of cleanstrap functions instead of q2a's. What is the name of the theme you were using before coming to Snow flat?
by
Sorry, the following does not make sense to me, so I just ignore it:  "The reason I'm getting this error on my end is because cleanstrap did overrided some q2a function which resulting snowflat to use some of cleanstrap functions instead of q2a's. "


I do not remember what I was using before the SnowFlat.  But I can tell you I was using SnowFlat for a long time, when SUDDENLY I started having mobile google errors, around April 2019.

Tip:  Check your website with https://web.dev.  It does have errors:  
Mobile Friendly.  
Tap targets are not sized appropriately. 81% appropriately sized tap targets

1 Answer

0 votes
by
edited by
I did a quick test changing the mobile theme.  The "classic" theme worked fine without errors.  Quick test on one page only though.

EDIT:  The Classic Theme started giving different errors on the google mobile test.  It seems that this is an issue that depends on the themes.

Any good themes that do not give errors out there?
by
I switched to CLASSIC.  After some tests the pages all pass the google mobile test.  However the SnowFlat theme looked much better.  So maybe I will look for a better but bug-free theme.
by
How did you solved this mobile-friendly issue?
...