[Support request] Embeds causing mobile-friendly issues on search console

[Antoinette]

I am not super technical, so please be patient.

I am using GP Pro with the Dispatch site from the library. I am having a strange issue where posts that include an embed (iframe or js) which renders fine on the front-end is raising the “not mobile friendly” issue on search console.

Any ideas what might be causing this?

[David]

Hi there,

could you link me to a page where there is an embed so i can take a look?

[Antoinette]

Here you go: https://extratime.media/2019/10/11/rugby-world-cup-fixtures-australia-vs-georgia-live/

It might not even be GP related and more to do with how the RSS is being rendered. All help and patience appreciated.

[David]

This is Google telling you the page / site is not optimized.
When google tests your site it sets a limit on the resources it will use. If your site requires more resources, in the form of server requests it simply passes them by.
See this GTMetrix report:

https://gtmetrix.com/reports/extratime.media/myedA0jm

There are 105 requests being made. Which has exceeded its resources and therefore fails to load the necessary stylesheets and scripts required to render the page correctly, which results in the errors.

The key to optimizing the site is to reduce:

A. the number of requests being made – ideally as low as possible, above 35 and your likely to get into trouble.
B. the size of the requests being made – anywhere you can compress images or remove content the better.

Our optimization tips will help somewhat towards this by combining and minimizing CSS and JS:

https://generatepress.com/fastest-wordpress-theme/

The rest of it will be down to you challenging what you need on the site for example you have 11 fonts and FontAwesome being loaded.

[Antoinette]

These tips are super helpful (thank you!). However, I’m refering to the following specific niggle from the Google Producer feed guidelines. Again, not sure if that’s on the GP side or the feed rendering side:

Use <content:encoded> to contain the full contents of every article. If you do not use a <content:encoded> tag, Producer defaults to content in the <description> tag.

Important:

For <content:encoded>, you must use the namespace xmlns:content=”http://purl.org/rss/1.0/modules/content/&#8221;.
HTML must be escaped or preferably wrapped in a CDATA section. For example:
<content:encoded><![CDATA[<b>This is some HTML text.</b>]]></content:encoded>

Producer removes <script> and <iframe> tags, except for the ones included in the Media assets section.

Producer removes inline styles (e.g. <style> tags or style=”” attributes.

[David]

Those specific issues will be related to the emebed/iframe/script being used. All of it will be a 3rd party request so neither WP or the Theme will have any impact on that.

[Antoinette]

Thank you David. You’ve been about 100 times more helpful than I could have hoped.

[David]

You’re welcome 🙂

[Author]

Posts