custom css not showing in browsers, but show on tablet/phone

LOL I never know nowadays so I have to save face and just make sure gender isn’t placed on anyone.

You’re doing great. Like I said above. Someone has thrown ketchup all over that theme. Look at what I suggested above and you’ll be on your way to the finish line. Need more help with CSS and whatever just let us know.

Yeah, WP Fastest Cache is what is doing the minification and combining your files, and it might also be what is commenting out the different files. Can you try turning off that functionality?

@stefsternyc – I appreciate that, and at the same time don’t mind you giving me a hard time! I deserve it. To eliminate more errors I want to make sure I do this right. I will move my CSS from Site Origin Plugin to the CSS of my theme. Then I will delete all CSS from the Site Origin Plugin.

@phoenixfireball – Yes I will turn that off now.

@phoenixfireball – Just deactivated WP Fastest Cache. As my host has also shut of caching, should I activate another plugin?

@stefsternyc – Thanks! Can you toss my a rag so I can wipe up all the ketchup!! Honestly though, how do I go about cleaning up my mess? Since I did not mean to do it in the first place, knowing what to do to clean it up is confusing.

@farmsource – create a local environment where you can teach yourself and learn. If on a Mac grab MAMP Windows use WAMP or something sim. Download a fresh copy of your theme and see what the site looks like and go from there.

Some host also provide a staging area where you can test and try things out before pushing them to live.

I prefer to work local though as it is super fast.

@stefsternyc – I appreciate that guidance. I have a ton of learning to do. Can I please clarify from an early question. Should I move my custom CSS out of Site Origin and into my theme’s custom CSS? Will this help for now until I can learn why and how the comment strikeouts are there?

If you don’t have a ton of visitors per day, you can get away with not using caching. But you can also re-enable a caching plugin after you’ve made the changes you want. I’d recommend something like WP Super Cache or W3 Total Cache. If you are willing to spend money, WP Rocket has been amazing to me.

@famsource You don’t need to use Site Origin CSS if you know how to write CSS. If you depend on it to help you figure out the styles for different things, then keep it. You don’t have to remove it, but don’t duplicate your CSS between both things. And the strikeouts are gone now that you’ve disabled that caching plugin.

@phoenixfireball – Right now my site traffic is minimal, so that is good. I will absolutely take your advice and use one of the two free ones for now until I can get the site corrected and eventually (hopefully) generating some revenue. Then I will go for the WP Rocket.

@phoenixfireball – I didn’t even know what CSS was a few weeks ago. Now I am a little comfortable with it and finding the elements with the Inspect tool. I think I agree with you. I will not use Site Origin for CSS. I will move what I have over to Oceanwp and remove all CSS from the Site Origin Plugin.

@phoenixfireball – I just moved all CSS over to my Oceanwp theme custom CSS. I then removed all CSS from Site Origin. I also deleted the WP Fastest Plugin. All seems to look good so far.

@stefsternyc – You had mentioned some code being below an @media query. I am unfamiliar with that. Did any of the changes I just made fix that issue? Or is there something else I need to do now for that issue?

@stefsternyc & @phoenixfireball – Guys I can’t thank you enough for the time you took to help me out and get me to look at my site a little different to problem solve issues. Thank you again for all of your time!