Core web vitals error

  • Resolved yondermann

    (@yondermann)


    1 year, 8 months ago

    Hi,

    There is an error in Google’s core web vitals for mobile: Browser errors were logged to the console:

    …litespeed-cache/guest.vary.php:1:0(www.suncakemom.com)Failed to load resource: the server responded with a status of 403 (Forbidden)/treats/chimney-cake-recipe:1:0(www.suncakemom.com)SyntaxError: Unexpected token ‘<‘, “<!DOCTYPE “… is not valid JSON

    A report was sent in

    ANHCAUCH

    Thanks!

    The page I need help with: [log in to see the link]

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

  • If you have any security plugin installed this plugin causes the issue and prevents access to guest.vary.php.

    Thread Starter yondermann

    (@yondermann)

    There is antispam bee and loginizer installed. If antispam bee is deactivated nothing happens. If Loginizer is deactivated the same error is still logged with the only difference that there are a bunch of .js errors also being logged. The cache is purged after each activation and deactivation.

    I can only tell you that “something” in your WP installation is blocking the guest.vary.php request. You have to find out what that is for yourself. The guest.vary.php is needed in any case for the Guestmode.

    Thread Starter yondermann

    (@yondermann)

    So you say if this isn’t solved then enabling guest mode and guest optimization has no effect whatsoever?

    That means if something blocks guest.vary.php the Guestmode doesn’t work.

    Thread Starter yondermann

    (@yondermann)

    That blog post says nothing about why google mobile bot is incompatible with guest mode.
    The speed scores are mostly fine. This is only a best practices error which doesn’t really impact anything probably. Still it would be nice to eliminate it.

    This issue has nothing to do with Google. As I said, something on your server is blocking the request to guest.vary.php. Most of the time this is caused by some security plugins. In the end you have to find the cause yourself. In any case, the problem is not a cache plugin problem.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Core web vitals error’ is closed to new replies.