Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #170109

    Hi guys,

    i finished the first version of my website:

    I am now starting with the SEO for my site and just ran the W3C CSS Validator. I was shocked as it showed my site has 325 CSS Errors!! A lot of them are inside of the Enfold Theme. And a bunch are on the Website. Where do they all come from?

    Here is the link:

    Please help me to reduce these errors. I am ready to pay extra for this. I expected the CSS Code of your Enfold Theme to be better.



    Hello Jeffrey!

    That customization is beyond the scope of our support form. If you really need it try hiring a freelancer for the job.



    Hi Josue,

    to be honest i am not content with your response.

    If i fix the Errors myself in the code and i make an Enfold Update a few weeks later, will my fixed code be overwritten with your Code with Errors again?!
    1) How can i deal with this?

    2) Could you maybe at least try to adress these bunch of CSS Errors in the next update?! The Validator shows me more than 800 Errors. Most of them in the Layerslider, which are unchangable, because the whole Layerslider tool is based on these mistakes.

    It’s a ridicilous high number of Errors and they make it hard to optimize your Website for Search Engines.

    I would really appreciate it. And i am sure a lot of users would, too.

    Thanks and Best,



    2) No, I’m sorry. These “css errors” are actually no errors but the code is required to maintain the cross browser compatibility for webkit browser users. The browser specific prefixes (like -webkit, -moz, etc.) are not part of the CSS3 specifications and thus the w3c validator will mark them as “errors” although the code makes sense and works perfectly fine. Removing the code can cause styling issues for some users and that’s why we think it’s better to use browser prefixes even if w3c does not accept them. In addition I’m not sure who told you that 100% valid css code will improve your seo but you’re wasting your time – search engines do not care about these browser prefixes at all. Even invalid html code can make sense – i.e. if you add semantic markup to the code which is not part of the html5 standard and which helps the search engines to parse your content. See also:


Viewing 4 posts - 1 through 4 (of 4 total)

The topic ‘W3C CSS Validator: 325 CSS Errors!!!’ is closed to new replies.