Lighthouse returned error: PROTOCOL_TIMEOUT. Waiting for DevTools protocol response has exceeded the allotted time. (Method: Page.getAppManifest) (PROTOCOL_TIMEOUT

2,886 views
Skip to first unread message

tan...@muvi.com

unread,
Feb 1, 2019, 2:25:11 AM2/1/19
to pagespeed-insights-discuss
Hi Team,

All of sudden i am experiencing "Lighthouse returned error: PROTOCOL_TIMEOUT. Waiting for DevTools protocol response has exceeded the allotted time. (Method: Page.getAppManifest) (PROTOCOL_TIMEOUT" while testing the site https://www.muvi.com and google bot complaining issue Clickable contents are too closer and content width exceeding device width by dropping many pages from index which is a serious issue.

What i believe here the bot is not able to load the complete site with all required js and css, causing this issue.

Could anyone please help here ?


dm Opr

unread,
Feb 3, 2019, 8:37:07 AM2/3/19
to pagespeed-insights-discuss
I have the same situation with:   www.cityunscripted.com

177.jpg

 Could anyone please help here to us? 
Thanks

wil...@foriio.com

unread,
Feb 4, 2019, 1:22:22 AM2/4/19
to pagespeed-insights-discuss
We at foriio.com are having the same error when looking the Desktop insights. We currently deployed a version to add a robots.txt route and sitemaps, but that shouldn't be causing this kind of problem..

Panagiotis Padazopoulos

unread,
Feb 4, 2019, 8:29:04 AM2/4/19
to pagespeed-insights-discuss
I have the same issue.

Panagiotis Padazopoulos

unread,
Feb 4, 2019, 9:59:11 AM2/4/19
to pagespeed-insights-discuss
it seems that the manifest declaration is responsible for this error.

        <link rel="manifest" href="/public/manifest.json">

rajesh singh

unread,
Feb 4, 2019, 10:57:27 AM2/4/19
to pagespeed-ins...@googlegroups.com
the complete file is creating a problem or some specific variable in the manifest file is causing the problem?

--
You received this message because you are subscribed to the Google Groups "pagespeed-insights-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pagespeed-insights-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pagespeed-insights-discuss/70a8b999-07ad-4090-ad0d-cff68ea5e776%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--

        Best Regards,
        Rajesh Singh,
        Contact No.(+91)7208413963

Pylon Design

unread,
Feb 5, 2019, 4:18:42 AM2/5/19
to pagespeed-insights-discuss
We are also experiencing this for https://www.southwarkeba.org.uk on Desktop only. But other speed checkers not returning any problems. What gives?

Panagiotis Padazopoulos

unread,
Feb 5, 2019, 5:21:47 AM2/5/19
to pagespeed-insights-discuss
I have to try by removing a variable each time. Not tested yet.
Here is the manifest to check if something is missing or is wrong.
{
  "short_name": "Ekdromi",
  "name": "Ekdromi.gr",
  "icons": [
    {
      "src": "/public/images/general/icons/192x192.png",
      "type": "image/png",
      "sizes": "192x192"
    },
    {
      "src": "/public/images/general/icons/512x512.png",
      "type": "image/png",
      "sizes": "512x512"
    }
  ],
  "start_url": "/?utm_source=installed_app",
  "background_color": "#f3f3f3",
  "display": "standalone",
  "scope": "/",
  "theme_color": "#044077"
}

On Monday, 4 February 2019 17:57:27 UTC+2, rajesh singh wrote:
the complete file is creating a problem or some specific variable in the manifest file is causing the problem?

On Mon, Feb 4, 2019 at 8:29 PM Panagiotis Padazopoulos <takis...@gmail.com> wrote:
it seems that the manifest declaration is responsible for this error.

        <link rel="manifest" href="/public/manifest.json">


On Monday, 4 February 2019 15:29:04 UTC+2, Panagiotis Padazopoulos wrote:
I have the same issue.

On Friday, 1 February 2019 09:25:11 UTC+2, tan...@muvi.com wrote:
Hi Team,

All of sudden i am experiencing "Lighthouse returned error: PROTOCOL_TIMEOUT. Waiting for DevTools protocol response has exceeded the allotted time. (Method: Page.getAppManifest) (PROTOCOL_TIMEOUT" while testing the site https://www.muvi.com and google bot complaining issue Clickable contents are too closer and content width exceeding device width by dropping many pages from index which is a serious issue.

What i believe here the bot is not able to load the complete site with all required js and css, causing this issue.

Could anyone please help here ?


--
You received this message because you are subscribed to the Google Groups "pagespeed-insights-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pagespeed-insights-discuss+unsub...@googlegroups.com.

ramon...@afil.io

unread,
Feb 5, 2019, 10:32:40 AM2/5/19
to pagespeed-insights-discuss
Hi Panagiotis,

I removed the manifest.json and keeps throwing the same error message. I think we can discard this possibility.

Pylon Design

unread,
Feb 6, 2019, 11:31:38 AM2/6/19
to pagespeed-insights-discuss
Turns out we had an issue with multiple cron tasks overflowing. The number of cron jobs neared 30MB in size and so it can not be executed, leading to the timeouts and a huge error log, generated in the site directory  with a single line of the error being about 11MB in size!

Stefan Maier

unread,
Feb 7, 2019, 5:22:32 AM2/7/19
to pagespeed-insights-discuss
we have the same issue with https://www.schwedenliebe.com
deleting the manifest.json has no effect - problem occurs in 4/5 tests approx. any ideas?

Conrado Medeiros

unread,
Feb 7, 2019, 11:54:18 AM2/7/19
to pagespeed-insights-discuss
we have the same issue

Any idea?

Elly Prior

unread,
Feb 8, 2019, 5:25:09 AM2/8/19
to pagespeed-insights-discuss
I have the same problem with various pages at various times: https://www.professional-counselling.com/.
Elly

paulirish

unread,
Feb 8, 2019, 2:26:11 PM2/8/19
to pagespeed-insights-discuss
Thanks all.

This bug is now resolved. We pushed a fix at 6PM PST last night (about 17 hours ago).


Specifically the fix for PROTOCOL_TIMEOUT and Page.getAppManifest. It's possible to see other PROTOCOL_TIMEOUT errors, but this one is sorted for now.
Reply all
Reply to author
Forward
0 new messages