Ars Technica Website Analysis

“Your accessibility is surprisingly decent, but your usability is crippled by bloat.”

88/100 accessibility is genuinely solid—no alt text disasters, proper heading structure, and screen reader consideration. But UX suffers from forced reflows (0/100), deprecated APIs (0/100), and third-party cookie hell. Your buttons and links lack accessible names in critical areas (0/100 on two separate audits), meaning keyboard users and assistive tech users hit dead ends. The 200ms FID creates that 'lag when I click' feeling that makes sites feel broken. Fix your interactivity by removing unused third-party scripts and optimizing your JavaScript bundle.

“Your SEO is so good, we'd mistake it for excellence if your technical foundation wasn't collapsing.”

You nailed the SEO fundamentals: proper title tags, comprehensive meta descriptions, solid OG implementation, 192 internal links for crawlability, and zero broken image alt text. Google loves you structurally. But here's the problem—you've got 0/100 on 'Links are not crawlable,' which means your technical debt is choking your actual search visibility. All that SEO optimization is like polishing a car with a flat engine.

“Your words are sharp; your technical execution makes you sound like a robot speaking through a broken speaker.”

The copy is snappy, authoritative, and exactly what a tech publication should be—clear, opinionated, and substantive. Your meta descriptions and OG tags are properly crafted. The issue? Nobody's reading your brilliant words if the page takes 4 seconds to load. Copy quality means nothing when performance makes users bounce before they see a single article headline. Your 1,680 words are wasted if they're delivered at dial-up speeds.

“Your layout works, but your performance metrics suggest you're running it on a potato.”

The design itself is clean and readable—nothing offensive, which is the problem. You've got 61 images but a Speed Index of 3/100, meaning visitors are literally watching your site load like a 90s dial-up nightmare. Your font display is completely broken (0/100), causing that classic text-flash-of-doom experience. You need to implement font-display: swap immediately and lazy-load those images like your reputation depends on it.

“Your 4-second LCP and 200ms FID would make a 2008 web developer weep.”

54/100 on PageSpeed is embarrassing for a tech publication—you're literally slower than the average website despite being the site that *reviews* fast websites. Your main culprits: unused CSS (0/100), JavaScript execution time spiraling out of control (0/100), Total Blocking Time at 29/100, and eight external scripts acting like anchor weights. You need to audit every third-party script, implement critical CSS inline, defer non-critical JS, and actually minify your unused code. Your readers deserve better, especially from *Ars Technica*.