We Inspected 20 Portfolio Homepages. Here Is What Failed.

Half of the 20 homepages failed the opening-answer check, while none showed a structural failure. The weak spot was content shape, not the build underneath it.

By Krisada. Updated October 5, 2026.

The result in one table

On October 5, 2026, QuickRankAI inspected one public homepage from each of 20 sites in Krisada's portfolio. The same live 38-check engine read every page from the outside. It used no analytics, server logs, Search Console data, or private access.

The opening failed most often

The category scores make the same point. Discovery averaged 99, page structure averaged 97, entity clarity averaged 99, and AI readiness averaged 94. Content signals averaged 76.

These sites were generally easy to reach and easy to identify. The weaker part was what the page said first, how specific the claims were, and whether the main content had a clear HTML landmark.

A high score can still hide a weak first paragraph

QuickRankAI.com scored 96 in this run and still failed its own opening-answer check. The headline promised a decision, but the useful explanation came after the form. That is now fixed: the answer appears before the input.

This is why the score is not the verdict by itself. A page can have HTTPS, canonicals, structured data, a sitemap, and clean headings while making the reader work too hard for the point. The finding tells you what the total score compresses.

The semantic landmark miss was one line with a large effect

Six homepages had no <main>, <article>, or role="main" around the primary content. The pages still looked fine. The missing landmark made it harder for an extractor to separate the page from its navigation and footer.

The HTML standard defines the main element for the dominant content of the document. On a shared template, this is usually one repair that reaches every page.

All 20 scores

What this sample does not prove

This was a controlled portfolio check, not a random sample of the web. These sites share an owner, many share a PHP and JSON architecture, and several have been through the same technical standards. Their high discovery and entity scores should not be treated as a general benchmark.

The run also covered homepages only. An article, category, product, or service template on the same site may return a different result. That is why the repair-or-rebuild decision calls for checking representative page types before changing the whole build.

The next metric is repeat failure rate

The next run should drive the opening-answer failures below 10, the specificity failures below 7, and the landmark failures below 6. A score increase is useful, but the better proof is that the same named problem stops appearing across the portfolio.

The raw lesson from this run is simple. Mature technical foundations did their job. The larger opportunity is to make the useful answer visible sooner and support it with evidence a reader can check.