Dimitar Petrov

We were unable to determine if a specific setting was causing the issue. If the issue reoccurs, please open a ticket so we can investigate the case further.

Regards,
Dimitar Petrov

The auto-flush feature is triggered upon saving post/page or modifying settings.

Please post a new ticket in our support system once you notice the issue again so we can perform further investigation.

I have replicated the issue, however, once I purged the SiteGround Optimizer cache the forms were displayed as expected. Our plugin has an auto-flush feature, however, it seems that specific modification was applied to these sites that did not trigger the mentioned feature. I tried to replicate the issue again, by changing our plugin’s settings but the forms have not disappeared anymore.

I would recommend purging the cache from the applications dashboards > top menu > Purge SG Cache and testing again. If that resolves the issue, you should flush the cache after every form modification. If not, please update us with the site that does not display the form correctly after flushing the cache.

Best Regards,
Dimitar Petrov

Hello,

Our developers have discussed the case and decided that at this stage the requested modification cannot be applied. Indeed, the WordPress application allows overriding HTTP methods used by the client, however, this is a workaround for specific environments and not the standard. We follow strictly the standards and best practices.

If you maintain such an environment, I would recommend allowing all default HTTP verbs required by the WordPress app.

Regards,
Dimitar

Thank you for your collaboration.

I have reported the case to our developers and they will consider the requested feature.

Best Regards,
Dimitar Petrov

Indeed, your solution is one line.
Our developers are still reviewing the request and note that extensive testing is also required. I’m afraid, we cannot provide an ETA.

Best Regards,
Dimitar Petrov

Hi @jr104,

We cannot provide an ETA. My colleague from the mentioned chat session has misunderstood the case and considered it as a bug fix request. We apologize for that.

Our developers are reviewing the request in detail and if possible the solution will be implemented in the future versions of the SiteGround Optimizer plugin.

Best Regards,
Dimitar Petrov

Hey Matthew,

Thank you for your collaboration.

I have reported the case to our developers and they will consider the requested feature.

Best Regards,
Dimitar Petrov

Hello @kerouac_zoso,

The issue could be caused by a different plugin that provides optimization features, but we cannot confirm that without performing further tests.

As the reported issue is specific to your website, please open a ticket from your SiteGround User Area so we can investigate the case further.

Best Regards,
Dimitar Petrov

Thank you for the update.

I have checked your website and noticed that the Lazy Load feature is currently activated.

The W3C validator is indeed reporting the issue in question. Please note that this tool loads the HTML output without being an actual browser, so we could consider this as speculative parsing.

The srcset attribute is actually added, correctly, following the best practices to be defined as data-srcset. When the Lazy Load feature is disabled, the srcset attribute is not converted to data-srcset and this is why the validator does not report any errors.

Defining the attribute dynamically, as data-srcset, we avoid loading the image in non-browser requests(speculative parsing). This is why you can safely disregard those warnings.

In order to fully confirm that the attribute is passed correctly, you could
open your website directly in your browser, right-click on some image and click the Inspect(or Inspect Element) button. The srcset attribute should exist. In case it is missing on specific images, revise the way you are including these images to your posts, as WordPress by default adds srcset attribute.

Best Regards,
Dimitar Petrov

Hey @gabe9,

It is up to you which plugin’s functionality will be enabled. Essentially our Web Fonts Optimization feature requests the required Google fonts, saves them locally, and performs further optimizations to render them as quickly as possible.

Best Regards,
Dimitar