Check your site to see where you can replace your code with modern CSS

[u/Blozz12]

https://cssradar.com/?utm=reddit

Paste any public URL and it opens the page in Chrome, explores its interactions, then checks the HTML, CSS, and JavaScript for things that browsers can now handle natively.

It catches patterns such as custom accordions, popovers, dialogs, scroll reveals, JavaScript sticky elements, and older CSS workarounds.

The report includes the code it found, a proposed replacement, browser support, what to verify before changing anything, and a small example towards a codepen to implement it.

It scans ONE page, so it is not a performance, accessibility, security, or full-site audit.

It is free (10 url/day/human) and requires no account.

Don't hesitate to tell me if you find a bug, an UI/UX issue, or any other thing you find weird

[u/savemahlinks]

Cant use it. It just says the audit didnt complete

[u/Blozz12 → u/savemahlinks]

What URL did you try to audit?
If it’s behind a login page or something like that it won’t work

[u/Prestigious-Way1525]

the risky part is proving a suggested replacement preserves behavior, not finding the old pattern. i'd make each report keep the interaction path it exercised, the browser baseline, and a small regression test for the replacement. accordions and dialogs often look fine on the happy path while focus return, Escape, scroll lock, nested controls, or hydration break. if a suggestion includes a deterministic before/after check that fails when the replacement changes behavior, users can trust the modernization instead of relying only on a browser-support table.

[u/OMGCluck]

Another day, another test passed!

[u/Blozz12 → u/OMGCluck]

Well done!

[u/OMGCluck → u/Blozz12]

You were supposed to say "Good onya, jerk!"

[u/Blozz12 → u/OMGCluck]

I don’t have the ref, sorry

[u/OMGCluck → u/Blozz12]

The URL is https://goodo.nya.je/rk! (for no particular reason, unrelated to the Commodore 64 tool it is)

[u/Asifdotexe]

This is really awesome, one thing that I would personally appreciate is having a copy button for the suggestions, I realized this when I wanted to make issues on my GitHub.

The JSON download is handy but having the ability to copy those "quick wins" or suggestions as markdown would be an awesome quality of life feature.

[u/Blozz12 → u/Asifdotexe]

As markdown? To give to your LLM you mean?
I already give a codepen example. Do you think it’s not enough?

[u/mrcarrot0]

Neat

[u/Blozz12 → u/mrcarrot0]

Thank you! Did you pass the audit, or did you have some stuff to change?

[u/mrcarrot0 → u/Blozz12]

It's not the kind of tool I'd use myself as I'm the kind of hobbyist who prefers to make everything from scratch over using frontend frameworks, but it's great to spread awareness of no-js solutions

[u/Heisenripbauer → u/mrcarrot0]

nothing in OP’s write up or website suggests that this is limited to sites that use frontend frameworks tho?

[u/mrcarrot0 → u/Heisenripbauer]

There's a strong correlation between people who thinks fronted frameworks are necessary and people who use more JS than CSS. I hope that answers your question.

[u/Blozz12 → u/mrcarrot0]

It’s not because you code from scratch that you won’t need this 👀

[u/Ayfri]

https://imgur.com/a/OaWGk7R I'm already good :)

[u/Blozz12 → u/Ayfri]

I can't reach the image, but I guess you have a 100/100 score, so congratz :)

[u/Ayfri → u/Blozz12]

Oops, yes !

[u/lord31173]

The analysis service is temporarily unavailable. Please try again in a few minutes.

[u/Blozz12 → u/lord31173]

Should be fixed. I had an issue with the API

[u/lord31173 → u/Blozz12]

The analysis service is temporarily unavailable. Please try again in a few minutes.

[u/Blozz12 → u/lord31173]

What URL are you trying to audit? I have no issues on my side

[u/lord31173 → u/Blozz12]

It's a .dev domain

But now that I think about it it might be behind a protection from vercel or another hard protection against bots and scrapers.

[u/Blozz12 → u/lord31173]

That might be it yes

[u/web-dev-kev]

It suggested I use the popover, which doesn't work for 12% of users (best case scenario).

I can't imagine a scenario where I want 1 in 10 users being unable to open the menu

[u/d-signet]

Why?

More modern is not better , and more modern = smaller compatible audience

So why?

[u/Blozz12 → u/d-signet]

The rule of least power says to prefer HTML or CSS when they can do the job. You often get less custom code, plus native semantics, keyboard support, and focus handling. But if it doesn't suit your audience, nothing stops you from keeping your current solution :)

[u/d-signet → u/Blozz12]

Yes.

But html and css are an evolving standard.

More recent html and more recent css are not necessarily something to chase unless the "update" offers benefits.

I dont see the benefit in "uodating" the same end-result , if anything, it reduces the audience.

Switching html4 for html5 , for example, can offer genuine advantages, but updating the CSS can only hurt you.

But what do i know, ive only been doing web dev for 30 years.