How to Tell If Your Website Was Built Badly (7 Checks You Can Run Yourself)

Check 1: Run PageSpeed Insights

Go to Google's PageSpeed Insights, enter your homepage URL, and read the mobile score. This is the single fastest quality signal available. A score in the green suggests a well-built site. A score in the red on mobile means real performance problems that are costing you both rankings and conversions, since Google indexes the mobile version of your site first.

Check 2: View the Page Source for Basic Tags

Right-click your homepage, choose 'View Page Source,' and use Ctrl+F to search for '<title>' and 'description'. If your title tag is generic ('Home' or your platform's default) or the meta description is missing entirely, basic SEO was never configured. This takes ninety seconds and tells you whether anyone thought about search at all.

Check 3: Use Your Site on a Phone, on Cellular Data

Not on office WiFi. Turn WiFi off, use your actual mobile connection, and complete a purchase. Most site owners have never done this. If pages take several seconds, if buttons are hard to tap accurately, or if a form field disappears behind the keyboard, your majority of traffic is experiencing that every day.

Check 4: Count Your Third-Party Scripts

Press F12 in Chrome, open the Network tab, and reload. Every file loading from a domain that isn't yours is a third-party dependency. A handful is normal. Twenty or more means an app-heavy build where performance was never a priority, and where each dependency is also a potential security and reliability risk.

• — PageSpeed Insights mobile score — green, amber, or red?
• — Title tag and meta description present and specific?
• — Full purchase completed on a phone using cellular data?
• — Third-party script count under control?
• — HTTPS on every page, not just checkout?
• — Structured data present (test at Google's Rich Results Test)?
• — Images sized appropriately, not full-resolution photos scaled down in the browser?

Check 5: Confirm HTTPS Everywhere

Click through several pages and check the padlock stays present in the address bar. HTTPS on checkout only, or mixed-content warnings on some pages, indicates a build that cut corners on fundamentals. In 2026 this is table stakes and free to implement — there's no legitimate reason for a site not to have it site-wide.

Check 6: Test for Structured Data

Run a product page through Google's Rich Results Test. If no structured data is detected, your products can't appear with rich results in search, and AI shopping systems have far less to work with when deciding whether to recommend you. Absent schema on an e-commerce site in 2026 is a meaningful omission, not a nice-to-have.

Check 7: Look at Your Image Sizes

In DevTools' Network tab, sort by size and look at your images. If a product photo is several megabytes, someone uploaded a camera-resolution file and let the browser scale it down — meaning every visitor downloads the full file regardless. This single issue is the most common cause of slow e-commerce sites, and it's straightforward to fix.

What to Do With the Results

If most checks pass, your site is fundamentally sound and any problems are likely content or marketing rather than build quality. If several fail — particularly speed, mobile, and structured data together — you're looking at a build where fundamentals were skipped, and incremental patching usually costs more over time than rebuilding properly.

Getting an Honest Assessment — With Devrex Digital

Devrex Digital audits existing sites against exactly these fundamentals and tells you plainly whether the issues are fixable in place or whether a rebuild is genuinely the better investment. We'd rather tell you your site is fine than sell you a project you don't need.