• Hi

    Firstly, congratulations on a great theme, probably my favourite I have ever used.

    I just have one issue that hopefully you can help with.

    I was running a Chrome Lighthouse test on a site using Customify and came across a couple of errors which I believe are to do with the theme, rather than any on-page content or plugins.

    Accessibility:
    ————–
    > Buttons do not have an accessible name
    Failing Elements
    button.search-submit

    Best Practices
    ————–
    > [id] attributes on the page are not unique
    Failing Elements
    ul#menu-main-menu.primary-menu-ul.menu.nav-menu

    > Does not use passive listeners to improve scrolling performance
    …js/theme.min.js?ver=0.3.4 line: 0

    > Links to cross-origin destinations are unsafe
    (www.facebook.com) _blank nofollow
    (twitter.com) _blank nofollow
    etc

    So I’m trying my best to get all these Lighthouse scores up into the 90s to provide the best UX possible, and would like to fix these issues.

    Can you give me some indication of how to go about this? I’m not a developer so I don’t fully understand everything about how the theme works, but am perfectly happy to give it a go myself (unless an updated version is coming that will fix these issues).

    If I need to create a child theme to do it, then which theme files / lines do I need to edit in the child? Or is there a better or easier way?

    Thanks in advance.
    David

    • This topic was modified 4 years, 9 months ago by davgraham.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Links to cross-origin destinations are unsafe:

    I’ve solved with this plugin: WP External Links by WebFactory Ltd

    It checks all your internal and external link, allowing you to activate or deactivate “nofollow”, “noopener”, “noreferrer”

    I’m looking how to solve “Buttons do not have an accessible name
    Failing Elements
    button.search-submit” did you solved it?

    • This reply was modified 4 years, 4 months ago by coca123seo.
    Thread Starter davgraham

    (@davgraham)

    I got rid of the error, but only by going in and hacking the theme files. No sign of any support reply on here so had to do something, even if it’s not very clean.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Lighthouse Errors on Customify’ is closed to new replies.