Mobile Friendly

m_abed · September 2019

Hi.there is a bad error from google webmaster tools for my website :

انرژی خورشیدی

this is a sample. i dont know if the BE theme is mobile friendly why the problem must exists!

the testing tool is there:

https://search.google.com/test/mobile-friendly

the messsage from google is:

Fix the following 3 issues

Content wider than screen

Text too small to read

Clickable elements too close together

Pablo · September 2019

Hello,

Of course BeTheme is made to be fully mobile friendly.

Also, I did the test and it shows that everything is fine.

https://search.google.com/test/mobile-friendly?id=BF9D8-daTvE6Kr1F_WBAQQ

Thanks

m_abed · September 2019

you testes the main page. but the problem is the other pages.now i removed one by one elements and found that the Action (Slogan ,Tel1 ,Tel2 ,Email ) bar on the top of page makes this Error for the google mobile friendly test:

Clickable elements too close together

you can see this at :

https://search.google.com/test/mobile-friendly?id=ULvX1XacmYs9UoXMhRgiJQ

when i hide this the error go out! and i show it again to get seen by you. its a bug i think for RTL version. i dont know its for LTR version also or not. other errors went by hiding other elements.

Pablo · September 2019

Notice, that your website on this tool is not loading whole website

http://prntscr.com/p52nsw

This tool is not a good way to test responsive of your website.

The best way, is to test it through browserstack.com or by resizing your browser.

We assure, that BeTheme is fully responsive.

Thanks

egylearn · December 2019

same problem here but it's not fixed for me even I hide action bar.

the solution is: make your theme with English language and edit in layout.css and base.scc files to get it rtl made. Thanks

Pablo · December 2019

egylearn,

I answered you in your topic:

https://forum.muffingroup.com/betheme/discussion/50590/blog-post-displayed-far-right-in-browser#latest

Thanks

m_abed · December 2019

why i cannot see the discussion? the problem was not solved for me too

Pablo · December 2019

Sorry, I attached the wrong URL - now it's correct - I edited it.

Thanks

Mobile Friendly

Comments