google.com scored 75 on Inspectrosite

I pointed Inspectrosite at google.com to see what it would say. It followed the redirect to www.google.com/, checked that final page, and came back with 75 out of 100, grade C, with the caption “5 critical issues to fix first.”

Quick disclosure: Inspectrosite is Byteslip’s own free browser tool. The badge above is just a picture of the score from our scan, not proof of anything (anyone can type a number into a badge link). The real record is the scan itself, and you can run it again here.

What the 75 is, and isn’t

We started at https://google.com. Inspectrosite cleaned that up to https://google.com/, followed Google’s redirect, and audited https://www.google.com/. That’s why the results say www.google.com while the badge just says google.com.

It ran 54 checks: 26 passed, 17 warned, 5 failed, and 6 were info only. The score is an average of the checks that count: a pass is worth 100, a warning 60, a fail 0, and info checks are left out. So 75 tells you how this one page did on Inspectrosite’s checklist. It isn’t a grade for Google as a company, and it says nothing about how good Google search is.

It also helps to remember what this page is. Google’s homepage is basically a search box run by a lot of JavaScript, not an article. A missing description, no <h1>, and no viewport tag would hurt a blog post much more than they hurt a page like this. Still, those are real findings, and they’re what the tool flagged.

The raw numbers from the scan: the HTML came back in 0.65s (651 ms including our proxy), the document was 219.9 KB, and the page had 14 scripts (2 external) and 6 images.

The five fails, in plain language

1. 1. Missing mobile viewport meta

   The page has no <meta name="viewport"> tag. Without one, a phone browser may lay the page out like a desktop screen and shrink it down. Google probably handles phones some other way, but the tag isn’t in the HTML we received.

2. 2. Missing meta description

   There’s no meta name="description", so a search engine has to write the snippet under the link itself. That’s kind of funny when the search engine is Google.

3. 3. No <h1> heading

   The page has no top-level heading. The scan actually found no headings at all, which was also logged as a warning. The logo and search box do that job visually, but screen readers and crawlers get no text heading to go on.

4. 4. Duplicate IDs: ZnpjSd

   The id="ZnpjSd" shows up more than once. IDs are meant to be unique. When one repeats, anchor links, form labels, and getElementById only find the first copy.

5. 5. Inline JS totals 93.9 KB

   About 93.9 KB of JavaScript is written right into the HTML instead of loaded from separate files. Browsers can’t cache inline code from one visit to the next. Google may well do this on purpose to make the first load faster, but by Inspectrosite’s rule it’s a fail.

A few warnings worth a look

• Thin text: only about 42 words of visible text, so the indexing outlook was “Indexable, with risks.”
• Head tags: the title is just “Google” (6 characters). There’s no canonical tag, no theme-color, 0 of 3 Open Graph tags, and no Twitter/X card.
• Old-school markup: 2 obsolete <center> tags, 1 inline onclick, and 1 of 4 landmark elements.
• Images and forms: all 6 images have empty alt text, none lazy-load, and none have width/height set. 2 form fields have no label.
• Weight: the 219.9 KB HTML document and 16 render-blocking resources.
• One header: no X-Content-Type-Options: nosniff.

On the necessary-components panel that adds up to 5 of 9. Doctype, charset, favicon, JavaScript, and HTTPS are present. The viewport, meta description, and single H1 failed, and the title got a warning.

What looked solid

Security and basic delivery were the strong parts of this scan. Most of what cost points was markup and SEO housekeeping, which matters less on a search box than on a page meant to be read.

Scores change

This is one scan, taken at 12:50 AM Hawaii time (HST) on November 6, 2026. Google changes its homepage all the time, and Inspectrosite gets updates too, so a scan today might not come out to 75. Re-scan www.google.com, or try your own site.