ragtech

The core file was only modified to see if it resolved the issue… which it did. It was driving me crazy as I always (as good old fashion best practices) use only one ‘H1’ tag per page.

So, then I came across the ”media-template.php” ‘H1’ tag and made the change just to see… I mean even if I left it that way it would have been replaced in any core update most likely. Besides we’re just talking about an ‘H1’ tag… If just that would break WordPress; then boy do we really have issues.

It may be just me, but I don’t see why an ‘H1’ tag is necessary there anyway. An ‘H2’ would work just as well as a ”Drop files to upload” message.

BTW; Yoast claims (Just as W3C does) – Using one ‘H1’ tag is still a good/best practice; even with the onset of HTML5.

FROM YOAST:
‘H1’ is the title of the page or the blog post, and you should only use it once. The other headings can be used multiple times, as long as it makes sense. It’s a hierarchical structure, so before you use H3, you should have used H2…

W3C
It is worth noting that in their examples and their tutorials… W3C says to utilize only ONE instance of H1 per page.

I did a Fetch as Google and you’re correct! Google does not pick it up.

I’m curious why the Indexability check by Ryte / Yoast https://en.ryte.com/lp/yoast/ finds it as an error?

I know when I changed the ”media-template.php” to

<h2><?php _e( 'Drop files to upload' ); ?></h2>

and let it re-analyze – The Ryte / Yoast Analyzer shows the issue as resolved.

I guess maybe their Analyzer is not so good.

Curious as to why Yoast recommends its use via the admin Dashboard?

Google it… there may be some differences of opinion here and there… But generally, Google looks at h1 tags as clues to what the page’s content is about. If you have multiple h1 tags with different keywords then it is difficult for Google to contextualize the page.

Best practice: one h1 tag with the keyword or theme you are trying to optimize for.

Also when I use Indexability check by Ryte / Yoast https://en.ryte.com/lp/yoast/ It shows multiple H1 on any one page as an error and suggest that it be fixed.

So why would WordPress want to add to this problem with H1 tags that show up in the page code like with this media-template.php file does?

OK, I’ve posted this question in three (3) places!

Here: https://www.ads-software.com/support/topic/will-birchpress-scheduler-work-with-payments-standard/

Here: https://www.birchpress.com/support/contact-us

And, Here: https://www.birchpress.com/forums/topic/will-birchpress-scheduler-work-with-paypal-standard

My Client is very interested, but need answers, please

OK, I’ve posted this question in three (3) places!

Here: https://www.ads-software.com/support/topic/will-birchpress-scheduler-work-with-payments-standard/

Here: https://www.birchpress.com/support/contact-us

And, Here: https://www.birchpress.com/forums/topic/will-birchpress-scheduler-work-with-paypal-standard

My Client is very interested, but need answers, please

• This reply was modified 7 years, 1 month ago by ragtech.

Is this your site: https://thegingeek.com/

Run in Pingdom:

The following publicly cacheable, compressible resources should have a “Vary: Accept-Encoding” header:

https://thegingeek.com/
https://thegingeek.com/sitespeed-js/36b7b49cbadc466b80f45d56d7417ce5.js
https://z-na.amazon-adsystem.com/widgets/onejs? … dInstanceId=06c4d9ae-9595-4e02-8c64-a69bae60f606

My guess is it would be the last one “https://z-na.amazon-adsystem.com/widgets/onejs?”

Search Google for “Specify a Vary: Accept-Encoding header https://z-na.amazon-adsystem.com/widgets/” and see what turns up. I found this on a quick search https://amzn.to/2H7qp9Y

There is “No” particular area the code needs to be placed within your “.htaccess” file.

And do NOTE: I too still get the “The following publicly cacheable, compressible resources should have a “Vary: Accept-Encoding” header:” message!

It was the score that was improved… As I mentioned above – it improved my score to “A” (93)… (from what was a “D”) – If you’re trying to get to a score of 100%; you may have to look at what files (Most likely they’re JS files) are causing the low scores.

For instance, Google Maps & Twitter JS files seem to still show up for me. It may also include removing one or more Plugins… you may even need to remove some HTML.

Pingdom shows you the specific files you’ll need to deal with (by clicking the Down Arrow). Find what those files are linked to and then you’ll have to make the choice (As an example… do I want that Map or Twitter button or can I do without it on that page).

For me getting my score from a “D” to an “A” was good enough… I was not looking to get to 100%!

There is “No” particular area the code needs to be placed within your “.htaccess” file.

And do NOTE: I too still get the “The following publicly cacheable, compressible resources should have a “Vary: Accept-Encoding” header:” message!

It was the score that was improved… As I mentioned above – it improved my score to “A” (93)… (from what was a “D”) – If you’re trying to get to a score of 100%; you may have to look at what files (Most likely they’re JS files) are causing the low scores.

For instance, Google Maps & Twitter JS files seem to still show up for me. It may also include removing one or more Plugins… you may even need to remove some HTML.

Pingdom shows you the specific files you’ll need to deal with (by clicking the Down Arrow). Find what those files are linked to and then you’ll have to make the choice (As an example… do I want that Map or Twitter button or can I do without it on that page).

For me getting my score from a “D” to an “A” was good enough… I was not looking to get to 100%!

Is this your site: https://thegingeek.com/

Run in Pingdom:

The following publicly cacheable, compressible resources should have a “Vary: Accept-Encoding” header:

https://thegingeek.com/
https://thegingeek.com/sitespeed-js/36b7b49cbadc466b80f45d56d7417ce5.js
https://z-na.amazon-adsystem.com/widgets/onejs? … dInstanceId=06c4d9ae-9595-4e02-8c64-a69bae60f606

My guess is it would be the last one “https://z-na.amazon-adsystem.com/widgets/onejs?”

Search Google for “Specify a Vary: Accept-Encoding header https://z-na.amazon-adsystem.com/widgets/” and see what turns up. I found this on a quick search https://amzn.to/2H7qp9Y

• This reply was modified 7 years, 1 month ago by ragtech.

Yes, added the code below to my “.htaccess” file…

<IfModule mod_headers.c>
  <FilesMatch ".(js|css|xml|gz|html)$">
    Header append Vary: Accept-Encoding
  </FilesMatch>
</IfModule>

…Improved my “Specify a Vary: Accept-Encoding header” score to “A” (93)

Also, use https://tools.pingdom.com/ it’s much better than Google’s “PageSpeed Insights” it also will show you your Google PageSpeed Performance Grade and so much more!

How to Fix “Specify a Vary: Accept-Encoding Header” Warning

https://kinsta.com/knowledgebase/specify-vary-accept-encoding-header/

• This reply was modified 7 years, 1 month ago by Jan Dembowski. Reason: Removed shortlink

I’ll 2nd That – Keep it SIMPLE – If it’s not broke don’t fix it!

BTW; I’m using the PREMIUM Version it that helps

C’mon!?!? Would someone from the ”dsIDXpress IDX Plugin” support team PLEASE let us know what the hold up is…

To my knowledge (As I’ve done with many a website); all that needs to me done is to change all your ”https://” prefix’s to ”//” — it really is that simple.

If this is NOT the case in your situation’ can you PLEASE inform the community what the problem (Hold up) is.

In case your team has not been keeping up with the new updates planned for many Browsers… Visitors will begin seeing a ”Warning” that these non-SSL sites are not safe! So, it is imperative that all plugins modify their code to keep this from happening.

I’m already getting Warnings from google about my sites that are not SSL.

So, PLEASE be kind enough to keep your community/clients/subscribers up to date as to the progress of modifying the dsIDXpress IDX Plugin code and its readiness for SSL (https://)

Regards,
~ragtech

• This reply was modified 7 years, 6 months ago by ragtech.

I just about got it there using Cloudflare with these 3 plugins

• cloudflare.3.3.1
• cloudflare-flexible-ssl.1.2.2
• ssl-insecure-content-fixer.2.4.0

It’s this one item that is preventing a fully Secure SSL website using Cloudflare’s Flexible Encryption service.

http :// api-idx.diversesolutions.com/images/dsIDXpress/ds-colorbox/overlay.png

It’s really %$%#^#$ me off

Found the problem after searching the forum for an answer…

RESOLVED