• Resolved donmcleman

    (@donmcleman)


    Hi, Matt. As I said in the other thread, I’ve activated the plugin and enabled the api but after I click to check pages what I get is an error message that says I still need to enable the page speed api in the console: ‘The “PageSpeed Insights API” service is not enabled.’

    I’ve activated the log feature as suggested but as far as I can tell the entries don’t show anything of interest – I’m guessing that they show that I deleted my old api key and tried another one:

    <script src=”https://pastebin.com/embed_js.php?i=VReV6xj4″></script&gt;

    (I haven’t used pastebin before so it may not work…).
    Edit: I knew it wouldn’t work, but the link does.

    Having thought about it, I have a suspicion that the problem may lie with my webhost – they’re called one.com and they apply very tight restrictions to their service. Can you think of any particular setting on their part which may be preventing the plugin information from getting through?

    Thanks for any help you can give,
    Don

    https://www.ads-software.com/plugins/google-pagespeed-insights/

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Matt Keys

    (@mattkeys)

    If you force Google PageSpeed to check page scores again (from options), does the log file continue to log these same errors again?

    As far as your webhost causing this issue, I cannot think of any limitations they could apply that would block the plugin from functioning, but allow it to get as far as it has (receiving a response from google).

    Thread Starter donmcleman

    (@donmcleman)

    I’ve forced it to check the page scores again as suggested but I still see the same errors and nothing more. Looking on the chart on the Google Developers Console the request has been registered.

    In the previous post you suggested adding a line of code for a more detailed report – I’ll try that.

    Thread Starter donmcleman

    (@donmcleman)

    I’ve added the line of code and re-run the check but no new info has appeared in the log file. The chart on the console does register that a check was made.

    I’ll try simple things like disabling other plugins, re-installing, installing on another site.

    Thread Starter donmcleman

    (@donmcleman)

    Well, that didn’t narrow it down much. Disabling other plugins made no difference; installed it on two other sites (one of which was also on one.com so for once they’re not responsible) and both came up with the same error.

    I didn’t try uninstalling and re-installing as the installing on other websites will have dealt with that possibility.

    The page on the Developers Console that lists projects shows the number of requests made for each site and the same number of errors. (For the main site I’m looking at there there are slightly more requests than errors as I’m also running the Web Fonts Developer API).

    To cover all bases: I’ve been using Chrome on Windows 8, I’ll try Firefox on Windows 7.

    Is this particular api dependent on another api to run perhaps?

    Plugin Author Matt Keys

    (@mattkeys)

    Browsers will not make a difference because all of this happens on the server before your browser ever starts receiving information.

    There are no other API’s that this depends on outside of the Google API used by the plugin.

    I would like to send you an API key that I know to be working for you to enter into your settings and test. Can you get in touch with me through my contact form so that I have an email address to send that to: https://mattkeys.me/about/

    Thread Starter donmcleman

    (@donmcleman)

    Hey, thanks!

    Thread Starter donmcleman

    (@donmcleman)

    It worked! So presumably this means there’s something wrong with my console settings. It happened on three sites I installed it on so I’m probably missing out some very basic stage, I’ll have another look.

    Thank you!

    Plugin Author Matt Keys

    (@mattkeys)

    Wonderful! If you are able to identify what is off in your settings please post back here as I am sure others will find it to be helpful as well.

    Thread Starter donmcleman

    (@donmcleman)

    And the answer is… I checked on another website and when setting up a project you leave the referrer box blank, ignoring the example underneath.

    My own api key now works. Thank you.

    Bryan

    (@bryanshumakergmailcom)

    I have been following this for awhile and am still experiencing this same problem (“No Pagespeed Reports Found” and advising me to make sure to enable and enter an API).

    -I have a new WP install hosted on Dotster.com
    -I have the latest version of WP and Google Pagespeed Plugin
    -I have disabled all other plugins
    -I have copied the htaccess file here for review
    -I have setup a brand new Google project
    -I activated the Pagespeed Insights API
    -I did NOT use any referring domain
    -I have verified that the correct API is entered into the plugin
    -I have tried WP Cron, Ajax, and Session Flush

    Any ideas?

    Plugin Author Matt Keys

    (@mattkeys)

    Hey Bryan,

    It sounds like you have ruled out the majority of the possible causes for failure. My only thought currently is that your server does not support the Ajax or Session Flush methods (possibly due to php being in Safe Mode?), and that the WP Cron is disabled or not functioning properly on your server.

    You can try triggering the WP Cron manually by going to this URL (updated with your domain name) https://yourwebsite.com/wp-cron.php?doing_wp_cron

    Some people switch from wp cron’s to a *real* cron as outlined here: https://wpdailybits.com/blog/replace-wordpress-cron-with-real-cron-job/74.

    If you do use this method you will find that the report scans do not start immediately but instead start the next time your Cron runs.

    Your problem appears to be unrelated to the issue experienced here by Don (“The “PageSpeed Insights API” service is not enabled.” Error), if you continue to have issues please make a new thread and I will try to help further.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Unable to see reports’ is closed to new replies.