• Generosus

    (@generosus)


    Good Day,

    Your SEO analyzer is classifying Page Objects test results that don’t pass your screening as a “Failed Test.”

    They should be classified as a “Warning” for two reasons:

    1. Your scanner is still detecting lazy loaded images which should not count toward SEO scoring. GTMetrix, DebugBear, PageSpeed Insights, and other highly-reputable SEO analyzers follow this criteria. We mentioned this a while ago and still not fixed.
    2. Websites that use HTTP/2 or HTTP/3 do not need to concatenate (i.e., combine) CSS or JS files. Websites actually perform better when these files are not combined. Your SEO analyzer is not taking that into account. Here’s a great article about that.

    Please review your SEO analyzer logic and update it to reflect the above. Currently, the results are misleading.

    Thank you!

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support Rank Math Support

    (@rankmathsupport)

    Hello @generosus,
    ?
    Thank you for contacting Rank Math support.
    ?
    We sincerely appreciate your feedback and have forwarded this to the development team. We will inform you once we implement these suggestions in SEO Analyzer.
    ?
    Please do not hesitate to let us know if you need our assistance with anything else.

    Thread Starter Generosus

    (@generosus)

    Hi @rankmathsupport,

    Thanks for that. When received, kindly share your developers’ feedback on this.

    Until then, please do not close this topic as “Resolved” (i.e.., leave it open).

    Cheers!

    Plugin Support Rank Math Support

    (@rankmathsupport)

    Hello @generosus,
    ?
    We have added the feature request to the roadmap and it will be implemented very soon. We will notify you when that happens.
    ?
    Please do not hesitate to let us know if you need our assistance with anything else in the meantime.
    ?
    Thank you.

    Thread Starter Generosus

    (@generosus)

    Great, thank you! We’ll close this topic as “Resolved” once the fix has been released.

    Cheers!

    Plugin Support Rank Math Support

    (@rankmathsupport)

    Hello,

    For our tracking purposes, we will have to mark it as resolved because we have noted down your feedback and now it will undergo our internal process to be implemented.

    If you want, you can open a new ticket again in the future if you wish to get an update but we will be sure to update you nonetheless when there is an update with a fix.

    Thread Starter Generosus

    (@generosus)

    Respectfully, I created the topic and it has not been resolved. When resolved, I will close it.

    It has been over two months and still no resolution.

    Thank you for understanding.

    Plugin Support Rank Math Support

    (@rankmathsupport)

    Hello @generosus,

    We’ve made some updates to enhance how we handle object requests on your pages.

    1. HTTP/2 and HTTP/3 Detection: If our system detects that your remote server uses HTTP/2 or HTTP/3, the test will automatically be marked as a Success, regardless of the number of objects on the page.
    2. Request Threshold Warning: When a page makes more requests than recommended, the test will now show a Warning rather than a Fail, providing a heads-up without penalizing your score.

    These updates are designed to provide more accurate insights without negatively impacting performance scores in scenarios where newer protocols or slightly higher request counts are used.

    Let us know if you have any other questions or need further assistance!

    Thread Starter Generosus

    (@generosus)

    Hi @rankmathsupport,

    Thank you for the update and changes made to your SEO Analyzer.

    I re-ran your SEO Analyzer. Two items that are not fully resolved:

    1. The results match the changes you described, except the score did not change when Page Objects went from a Failed condition to a Warning (details). It appears to me the score should change in this case by +3 points (in our case, from 94 to 97).
    2. Page Objects is still detecting and listing objects (e.g., images) that are lazy loaded. All of our images are lazy loaded (except 3) on our home page. You analyzer is listing 14 images. All other analyzers, except yours, reflect this. If the purpose of Lazy Loading is to decrease page loading time and improve SEO scores, why haven’t you fixed this yet? Think of it this way too: It’s a good way to measure if the user (i.e., website) has properly lazy loaded its images (or other embedded objects). The code changes shouldn’t be that difficult to make. The code simply needs to search for the strings: “lazy”, “lazyloaded”, etc in the page source. If detected, it should skip those objects.

    Please review once again and consider making the adjustments.

    Thank you!

Viewing 8 replies - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.