[Resolved] Google Mobile Usability > Text too small to read

Home Forums Support [Resolved] Google Mobile Usability > Text too small to read

Home Forums Support Google Mobile Usability > Text too small to read

Viewing 11 posts - 16 through 26 (of 26 total)
  • Author
    Posts
  • #900088
    Janine

    I removed the pasword from the wp-content folder, David.

    #900667
    Janine

    David, I removed the password from the wp-content folder. Can you check on the issue for me, please?

    And how can I protect the uploads folder properly?

    Thank you!

    #900736
    Tom
    Lead Developer
    Lead Developer

    Hi there,

    I just ran your site through this tool and didn’t notice any issues: https://search.google.com/test/mobile-friendly

    There are some “Page loading issues”, but those seem to be coming from your robots.txt file.

    #900786
    Janine

    Hi, Tom.

    I edited the robots.txt file. Are there still “page loading issues?”

    Thanks!

    #901189
    David
    Staff
    Customer Support

    There are still some scripts being blocked by your robot.txt but the site passes the test.

    #901190
    Janine

    How can I find out which scripts are being blocked? Thank you!

    #901274
    David
    Staff
    Customer Support

    If you test your site on: https://search.google.com/test/mobile-friendly
    Click the Page Loading issues and you will see a list of files that are noted as being blocked.

    #955478
    Gabriel

    Hello,

    I recently purchased GeneratePress and switched the theme I had on my site. Within a short period of time I got the “text too small to read” issue for 3 pages on Google Search Console.

    I followed this support forum thread, removed W3 total cache plugin and installed/activated autoptimize. I started a new validation on Google Search Console and after about 2 days I saw 1 of the pages got fixed but the other 2 did not.

    I run https://search.google.com/test/mobile-friendly for both pages

    result:
    Page is mobile friendly
    This page is easy to use on a mobile device

    One of the pages having issues is:
    http://www.smartipadguide.com/spam-email-on-ipad

    How can I fix the validation issue seen on Google Search Console?

    Thanks

    #956058
    Tom
    Lead Developer
    Lead Developer

    Hi there,

    I’m not seeing that issue on the page, and the Google mobile test doesn’t seem to be reporting it as an error. I also ran the page through Lighthouse and the issue didn’t come up.

    Perhaps it just needs a couple more days for search console to remove the issue?

    #1960423
    Richard

    Just an add-in from a GP user. This problem is not at all related to GP. It’s an issue between the cache plugin and the mobile googlebot. I have had it with both autoptimize and swift, on sites built with GP/Elementor and Gen/Beaver. Not optimizing css generally works, but that’s not really a “fix” is it?

    I still haven’t figured out the magic formula of settings is for either plugin, and truth is there may not be one — this could be a random googlebot thing that you just have to babysit (unless cloudflare works for you or you can afford a better off-site caching solution).

    I just babysit and when a problem pages (or several) pops up in Search Console (usually all three of the issues noted above, as they are all CSS related), I go through the following process:

    1. Cache Plugin – delete the cache for the problem page
    2. Cache Plugin – re-cache that page
    3. Repeat 1 and 2 for all pages listed as problems by Search Console for issue X
    4. Search Console – initiate Validation for issue X
    5. Repeat 4 for issues Y & Z.

    Sometimes it takes multiples attempts to get Validation to start, but once it does you will get a (usually) pass or (sometimesd) fail message from google ~24 hours later. If you pass, you can look forward to doing it all again in about a week 😉

    Still searching for a real solution (especially now that Experience” scores actually matter), but until then, this vigilance keeps my sites in the green.

    #1960809
    David
    Staff
    Customer Support

    Hi Richard,

    thanks for the feedback and your findings.
    We wrote this article a little while back to assist with this topic:

    https://docs.generatepress.com/article/text-too-small-to-read-and-clickable-elements-too-close-together/

    The big frustration upon receiving a Search Console mobile usability failure, aside from the lack of info google provides, is when you check the site visually and run a Mobile Friendly test all things are OK.

    If this is the case, then it generally points to Google Bot not having enough resources, at the time of testing, to load all the necessary site resources to correctly render the page, which leads to the failure.

    The resource limit that google sets for testing sties, is an unknown variable, so its not a simple case of keep your resources below X and all things will be fine…

    BUT anything you can do to optimize the site to reduce the number of requests a site makes, the size of those requests and improve the speed they can be loaded will help minimize this kind of problem. Things to look for:

    1. Fonts
    a) Use less google font families.
    b) remove unused variants – https://docs.generatepress.com/article/google-font-variants/
    c) serving the fonts locally – https://docs.generatepress.com/article/adding-local-fonts/
    d) Or simply use system stack fonts instead of google to remove all font requests.

    2. Combining CSS
    Most servers run HTTP 2.0 protools – which allow more concurrent network requests to be made by a server. Which means many small minimized files can be loaded quicker than 1 large combined file.

    3. Scripts
    Lots of scripts can quickly tank a sites performance, especially if those scripts rely on 3rd party domains, such as Ads, Analtyics or Social Sharing metrics. Where possible deferring the load of 3rd party scripts to keep them out of the critical chain requests will stop them form interfering with load performance. Consider, as with fonts, additional DNS lookups and reliance on 3rd party servers to deliver the request can add uncontrollable variables to the site loading.

    4. Hosting
    Shared Hosting can introduce more issues if other sites hosted on the server are maxing out the resources at the the time of testing. If this applies then it may be worth checking with the host to see what load the server was under when the failures occurred.

    Hope that gives you some pointers to reduce the chances google has an issue with loading the site.

Viewing 11 posts - 16 through 26 (of 26 total)
  • You must be logged in to reply to this topic.