GSC Page Experience https report: FAILING

Hi @deforeman,

This one:

<svg xmlns="https://www.w3.org/2000/svg...

Should not have anything to do with http/https links, since this is not a link, this is a type of SVG tag, it is not possible to go anywhere external and it should not cause any problem in any way, since I repeat that this is not a link but the name of the type of the SVG element, or rather its namespace.

Moreover, you have no problems with that,because your site fully complies with the https, based on this icon:

It seems to me that the problem may be with the report itself, perhaps it does not have an feature to handle this situation in order to understand that this is a namespace, and not a link.

However, please send any additional information for us – screenshots, link to the report and any other if it’s possible. By the way, if it contains any private information, you can send it to support[at]richplugins.com.

Thanks!

• This reply was modified 3 years, 6 months ago by richplugins.

It is useless to argue that the ‘name’, link, or tag is not harmful in your opinion. Google has determined that its presence IS harmful, and has clearly stated so. You must well know the impossibility of arguing with Big G.

I do hope you can modify the ‘name’, link, or tag as my only alternate is to discontinue using it.

If this support link had a way to attach screenshots I would have sent a pic of the report already.

Hi @deforeman,

Sure, no problem, it’s not hard to change and I think we can make it in the next release, but to be honest, this is my first time meeting this problem and I’m just interested in investigate it deeper. Is it possible to send (screenshots or link to test page) to support[at]richplugins.com?

It’s very important for us.

Thanks!

Link to my GSC Page Experience report showing HTTPS FAILING:

https://i.imgur.com/lrl42FLl.png

Viewing my homepage source code and searching for “http:” will bring up 77 instances of this tag.

Hi @deforeman,

Thank you for information.

Here’s what I think. In fact, the namespace attribute ‘xmlns’ is optional for embed SVG tags in a regular HTML page, which means that we will remove this attribute with a type (https://www.w3.org/2000/svg) in the next version of the plugin. Release will be in this week, for the next few days.

On the other hand, I still think that this is not the problem, and then, even after the release, warnings may remain, but let’s take a look at this. Unfortunately, I have no experience of understanding Google’s Page experience.

Hi @deforeman,

Sorry for late release.

Please update the plugin to the recent version 1.9.5 and check it after while.

Let me know how it goes.

Thanks!

Hi @richplugins,

Version 1.9.5 shows zero “http:” names, links or tags in my source code – down from 75+ in the 1.9.4 version.

Further, GSC’s Page Experience Report no longer shows FAILING on the https: evaluation – everything is in the green.

Thank you for promptly responding to my report of an issue.

Best regards,
Dennis Foreman

Hi @deforeman,

It’s really important, now we know it depends on that.
Thank you too for a good topic!