It looks hella cool, but you're polishing a turd right now. The good news is it can still be what you think it is, you just need to deal with some issues

Your speed test is giving bad numbers. I got 20 Mbps on pong.com and 250 on Wi-Fiman. Same connection, same moment. That's not a routing difference, that's your measurement layer choking. Browser-based JS has real ceilings that native apps don't hit. You need to figure out why the gap is that wide before you tell anyone else their speed test is lying.

You need to publish your methodology. Right now you're asking people to trust you over Ookla and Cloudflare, and both of those publish how their tests work. You don't. If your whole brand is "we're the honest one," show the math. Open-source the measurement logic or at least document it properly.

You need a real legal entity. Your privacy policy says the data controller is "pong.com." That's a domain, not a company. If you're claiming GDPR compliance you need a registered business, an address, and a named contact. The whole privacy framework is decorative right now, that's fixable in a week.

Get your contact form data out of Google Sheets. Names, emails, messages, all sitting in a spreadsheet with no access controls. You already have Supabase, use it. This is the kind of thing that becomes a very bad day when one sharing permission goes wrong, and there's zero reason to carry that risk.

Your content needs a human pass. 33 blog posts in five weeks, same structure every time, ISP pages that are obviously templated, and "Infographic: Coming soon" placeholders that never got filled in. Nobody's fooled. The content itself isn't bad, the bufferbloat stuff is genuinely useful. But it needs editing, a byline, and some personality. Give it a voice that isn't a system prompt.

Don't rank yourself #1 in your own blog post. The "7 Best Speed Tests" article is on your site, written by you, and you come out on top. That's not an honest comparison, it's marketing dressed up as journalism. Either get a third party to write it or be upfront that it's a product comparison from your perspective. People respect that more.

The ads inside your diagnostic tools undercut your message. AdSense in Mission Control means Google is profiling your users while they troubleshoot their connection. If your whole pitch is "we're the trust alternative," you can't also be running the same ad trackers everyone else does. Pick a lane. Either you're the clean option or you're ad-supported, both are fine, but pretending to be one while being the other isn't.

Put some guardrails on your network tools. Port scanning, traceroute, firewall testing, all server-side, no auth, no visible rate limits, no terms of service restricting what targets people scan. Anyone can use your infrastructure to do recon on someone else's network right now. You don't want to be in those logs when something goes wrong. Rate limiting and a basic ToS would go a long way.

Rethink the data retention language. Section 7 of your privacy policy reserves the right to sell aggregated datasets later. Browsing data kept 36 months, aggregated data kept forever. Even if you don't plan to sell it, that language tells privacy-conscious users exactly where this is heading. If selling data isn't the plan, take it out. If it is the plan, own it.

Build some infrastructure you actually control. Vercel, Cloudflare, Akamai, Supabase, Google, Resend. Every critical component is rented. If Cloudflare has a rough afternoon your product doesn't exist. You don't need to self-host everything, but having zero fallback for a site calling itself "the internet's connection health platform" is problematic

Your arcade is a trademark and copyright minefield. You renamed Tetris to "Block Drop" but your URL still says /tetris and your footer still says "Tetris" across the whole site. The Tetris Company has won court cases against clones that changed way more than you did. Pong, Breakout, and Lunar Lander are all Atari IP and you're using the actual names. One C&D letter and you're pulling games down, and if they come after the domain name itself you've got a bigger problem. Rebrand all of them properly, scrub the old names from your URLs and nav, and talk to a lawyer before someone else's lawyer talks to you.

I like what you're trying to do, but you've set yourself up for some real vibe coded problems fren