infoharness

← Scan another site

databn.com

13 pages read on 03 Nov 2026. 2 links checked. Contradictions come from pattern matching, so give each a quick look before you act on it.

What this scan covered
  • 3 links not checked: large sites such as Google, Facebook or LinkedIn block automated checks, or the link limit was reached.

No serious problems. 2 small things left to tidy.

2 findings in all: 0 serious, 2 minor. Most serious first.

Score out of 100. A is 90 and up; each problem lowers it in proportion to the size of the site.

Page speed

Measured by infoharness for https://databn.com/. We loaded the page in a real browser, once as a phone and once as a computer, from our server with no slowdown added, so slower real connections will see longer times.

Phone

56

Speed score45 files, 90.2 MB

  • First Contentful Paint1.5 s
  • Largest Contentful Paint8.7 s
  • Layout shift (CLS)0.13
  • Fully loaded12.6 s

What to fix

  • Mobile viewport. No viewport tag, so phones show a shrunken desktop page.
  • Page weight. 90.2 MB downloaded. Aim for under 2 MB.
  • Page caching. The page itself isn't cached. Fine for docs that change often, but a short cache or a CDN makes repeat visits faster.
  • Server response. The first byte arrived after 1.0 s. Slow servers delay everything else. Look at caching, hosting and database queries.
  • Oversized images. 1 images are much larger than they appear. Serve smaller versions.

3 other checks passed.

Computer

61

Speed score61 files, 90.5 MB

  • First Contentful Paint1.7 s
  • Largest Contentful Paint5.3 s
  • Layout shift (CLS)0.22
  • Fully loaded5.1 s

What to fix

  • Mobile viewport. No viewport tag, so phones show a shrunken desktop page.
  • Page weight. 90.5 MB downloaded. Aim for under 2 MB.
  • Page caching. The page itself isn't cached. Fine for docs that change often, but a short cache or a CDN makes repeat visits faster.
  • Server response. The first byte arrived after 1.0 s. Slow servers delay everything else. Look at caching, hosting and database queries.

3 other checks passed.

Send findings to GitHub or Linear
Then use "Create issue" on any finding.

Thin pages

2

Near-empty pages still show up in search and in AI answers, and say nothing useful.

  1. Very little content (0 words)

    low

    Near-empty pages (placeholders, 'coming soon') add noise to AI search results.

    How to fix
    1. Write the missing content, or delete the page and redirect it to the closest useful page.
    2. Placeholders such as 'coming soon' should not be published: they appear in search and in AI answers.
  2. Very little content (28 words)

    low

    Near-empty pages (placeholders, 'coming soon') add noise to AI search results.

    EXCLUSIVELY FOR JEWELRY STORES We become your marketing department so you can focus on selling beautiful jewelry while we bring customers back. Done-for-you service No contracts Cancel anytime

    /marketing-for-jewelers
    How to fix
    1. Write the missing content, or delete the page and redirect it to the closest useful page.
    2. Placeholders such as 'coming soon' should not be published: they appear in search and in AI answers.