Catalog / tomstrong.org
63

SEO audit for tomstrong.org

Tom Strong

other

Health 63/100 (fair) · 50 pages crawled · generated 2026-07-29

Download Markdown report (feed to ChatGPT / Claude / Cursor)

Home page of Tom Strong

Screenshot of tomstrong.org
50
pages crawled
45
indexable pages
4
errors
285
warnings
540
notices
0
orphan pages
0
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Security 67 4 41 44
Links 52 0 80 3
Canonical 74 0 44 0
Mobile 74 0 44 44
Content 83 0 28 73
Meta Description 87 0 21 23
Duplicate 92 0 13 23
Agent Readiness 96 0 7 39
Images 96 0 6 5
Crawlability 99 0 1 12
Headings 100 0 0 7
Performance 100 0 0 64
Robots 100 0 0 1
Social 100 0 0 88
Structured Data 100 0 0 44
Titles 100 0 0 58
URL 100 0 0 12
Findings

Errors (1 rules)

error Mixed content on HTTPS page

Rule security.mixed_content · Security · 4 occurrence(s)

Warnings (12 rules)

warning Control has no accessible name

Rule agent.control_no_name · Agent Readiness · 7 occurrence(s)

warning Missing canonical tag

Rule canonical.missing · Canonical · 44 occurrence(s)

warning Thin content (low word count)

Rule content.thin · Content · 28 occurrence(s)

warning Duplicate page content

Rule duplicate.content · Duplicate · 4 occurrence(s)

  • http://www.tomstrong.org/ — content shared by 4 pages: https://tomstrong.org/, https://tomstrong.org/index.html, https://www.tomstrong.org/index.html
  • https://tomstrong.org/ — content shared by 4 pages: https://tomstrong.org/index.html, http://www.tomstrong.org/, https://www.tomstrong.org/index.html
  • https://tomstrong.org/index.html — content shared by 4 pages: https://tomstrong.org/, http://www.tomstrong.org/, https://www.tomstrong.org/index.html
  • https://www.tomstrong.org/index.html — content shared by 4 pages: https://tomstrong.org/, https://tomstrong.org/index.html, http://www.tomstrong.org/

warning Homepage duplicated across protocol/host variants (no redirect)

Rule duplicate.protocol_host · Duplicate · 1 occurrence(s)

  • https://tomstrong.org/ — https://www.tomstrong.org/ serves the same homepage content with a 200 and no redirect — Google sees a duplicate. Pick one canonical host/scheme and 301-redirect the others.

warning Duplicate <title> across pages

Rule duplicate.title · Duplicate · 8 occurrence(s)

warning Incomplete/empty response after retries (likely transient — re-crawl)

Rule fetch.incomplete · Crawlability · 1 occurrence(s)

warning Content-Type header doesn't match the actual content

Rule headers.content_type_mismatch · Security · 41 occurrence(s)

  • http://www.tomstrong.org/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.tomstrong.org/colors.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.tomstrong.org/countries/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.tomstrong.org/gen/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.tomstrong.org/links/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.tomstrong.org/patch/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.tomstrong.org/photo/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.tomstrong.org/physics/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.tomstrong.org/quotes/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.tomstrong.org/recipes/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://tomstrong.org/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://tomstrong.org/bsa/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://tomstrong.org/bsa/adk.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://tomstrong.org/index.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://tomstrong.org/others.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tomstrong.org/countries/au.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tomstrong.org/gen/tree.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tomstrong.org/links/comp.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tomstrong.org/patch/cspwant.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tomstrong.org/photo/event.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tomstrong.org/photo/headshots.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tomstrong.org/photo/tech.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tomstrong.org/physics/collision.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tomstrong.org/quotes/index.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.tomstrong.org/recipes/buttercream.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".

warning Images missing alt text

Rule images.missing_alt · Images · 6 occurrence(s)

warning Internal link points to a redirect

Rule links.redirect_target · Links · 80 occurrence(s)

warning Missing meta description

Rule meta_desc.missing · Meta Description · 21 occurrence(s)

warning Missing viewport meta tag

Rule mobile.viewport_missing · Mobile · 44 occurrence(s)

Notices (29 rules)

notice No llms.txt for AI agents

Rule agent.llms_txt_missing · Agent Readiness · 1 occurrence(s)

  • https://tomstrong.org/ — no llms.txt found at the site root — add one so AI agents get a curated site summary

notice No main landmark for AI agents

Rule agent.no_main_landmark · Agent Readiness · 38 occurrence(s)

notice Low text-to-HTML ratio

Rule content.low_ratio · Content · 1 occurrence(s)

notice Main text is hard to read (low Flesch Reading Ease)

Rule content.readability_poor · Content · 8 occurrence(s)

  • http://www.tomstrong.org/colors.html — this page reads as very difficult (Flesch Reading Ease -24, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.tomstrong.org/countries/ — this page reads as very difficult (Flesch Reading Ease 26, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.tomstrong.org/patch/ — this page reads as difficult (Flesch Reading Ease 48, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.tomstrong.org/links/ent.html — this page reads as difficult (Flesch Reading Ease 41, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.tomstrong.org/links/guns.html — this page reads as difficult (Flesch Reading Ease 38, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.tomstrong.org/links/misc.html — this page reads as very difficult (Flesch Reading Ease 24, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.tomstrong.org/links/scout.html — this page reads as difficult (Flesch Reading Ease 43, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.tomstrong.org/patch/cspwant.html — this page reads as very difficult (Flesch Reading Ease 27, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.

notice Duplicate meta description across pages

Rule duplicate.meta_desc · Duplicate · 23 occurrence(s)

notice No character encoding declared (meta charset or Content-Type)

Rule encoding.charset_missing · Content · 41 occurrence(s)

notice Multiple <h1> elements

Rule h1.multiple · Headings · 7 occurrence(s)

notice Missing html lang attribute

Rule i18n.lang_missing · Mobile · 44 occurrence(s)

notice Likely hero image lacks fetchpriority=high

Rule images.hero_no_fetchpriority · Performance · 27 occurrence(s)

  • http://www.tomstrong.org/gen/ — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.tomstrong.org/links/ — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.tomstrong.org/patch/ — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.tomstrong.org/photo/ — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.tomstrong.org/public/ — the likely hero/LCP image (blank.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.tomstrong.org/recipes/ — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://tomstrong.org/bsa/ — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://tomstrong.org/bsa/adk.html — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/countries/au.html — the likely hero/LCP image (au_flag.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/gen/tree.html — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/links/comp.html — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/links/ent.html — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/links/food.html — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/links/guns.html — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/patch/cspwant.html — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/photo/event.html — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/photo/headshots.html — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/photo/tech.html — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/physics/archive — the likely hero/LCP image (blank.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/physics/bench.html — the likely hero/LCP image (logo_tiny.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/physics/collision.html — the likely hero/LCP image (logo_tiny.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/physics/lenses.html — the likely hero/LCP image (logo_tiny.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/physics/mirrors.html — the likely hero/LCP image (logo_tiny.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/public/crypto/ — the likely hero/LCP image (blank.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.tomstrong.org/recipes/buttercream.html — the likely hero/LCP image (cleardot.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.

notice Images without width/height (layout shift / CLS)

Rule images.missing_dimensions · Images · 5 occurrence(s)

notice Internal link has no anchor text / accessible name

Rule links.no_anchor_text · Links · 3 occurrence(s)

  • https://tomstrong.org/bsa/adk.html — 10 internal link(s) have no anchor text, aria-label, or image alt — they pass no keyword signal and are unusable to screen readers. Add descriptive text or an aria-label.
  • https://www.tomstrong.org/photo/event.html — 9 internal link(s) have no anchor text, aria-label, or image alt — they pass no keyword signal and are unusable to screen readers. Add descriptive text or an aria-label.
  • https://www.tomstrong.org/photo/tech.html — 7 internal link(s) have no anchor text, aria-label, or image alt — they pass no keyword signal and are unusable to screen readers. Add descriptive text or an aria-label.

notice Legacy <meta name=keywords> tag present (Google ignores it)

Rule meta.keywords_present · Content · 23 occurrence(s)

notice Meta description too short

Rule meta_desc.too_short · Meta Description · 23 occurrence(s)

notice Missing Open Graph tags

Rule og.missing · Social · 44 occurrence(s)

notice Large DOM (over 1500 elements) slows rendering & interaction

Rule perf.dom_size_large · Performance · 2 occurrence(s)

  • https://www.tomstrong.org/quotes/q_B.html — the page has 2430 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://www.tomstrong.org/quotes/q_C.html — the page has 2047 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.

notice Legacy image format (jpg/png/gif) with no next-gen fallback

Rule perf.images_legacy_format · Performance · 27 occurrence(s)

  • http://www.tomstrong.org/gen/ — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.tomstrong.org/links/ — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.tomstrong.org/patch/ — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.tomstrong.org/photo/ — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.tomstrong.org/public/ — 11 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • http://www.tomstrong.org/recipes/ — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://tomstrong.org/bsa/ — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://tomstrong.org/bsa/adk.html — 13 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/countries/au.html — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/gen/tree.html — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/links/comp.html — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/links/ent.html — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/links/food.html — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/links/guns.html — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/patch/cspwant.html — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/photo/event.html — 11 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/photo/headshots.html — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/photo/tech.html — 9 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/physics/archive — 10 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/physics/bench.html — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/physics/collision.html — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/physics/lenses.html — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/physics/mirrors.html — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/public/crypto/ — 11 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.tomstrong.org/recipes/buttercream.html — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.

notice Large HTML document

Rule perf.large_html · Performance · 1 occurrence(s)

notice No ETag header (no conditional GET for unchanged pages)

Rule perf.no_etag · Performance · 3 occurrence(s)

  • http://www.tomstrong.org/public/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.tomstrong.org/physics/archive — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.tomstrong.org/public/crypto/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.

notice No Last-Modified header (no conditional GET for unchanged pages)

Rule perf.no_last_modified · Performance · 3 occurrence(s)

  • http://www.tomstrong.org/public/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.tomstrong.org/physics/archive — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.tomstrong.org/public/crypto/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.

notice Slow server response

Rule perf.slow_response · Performance · 1 occurrence(s)

notice URL redirects to another URL

Rule redirect.single · Crawlability · 12 occurrence(s)

notice robots.txt missing (root returns 404/none)

Rule robots.txt_missing · Robots · 1 occurrence(s)

  • https://tomstrong.org/ — robots.txt did not return a 200 at the site root — a healthy site should serve one (declare your sitemap and confirm the host serves root files)

notice No structured data detected

Rule schema.none · Structured Data · 44 occurrence(s)

notice Missing recommended security headers

Rule security.missing_headers · Security · 44 occurrence(s)

notice Title tag is identical to the H1 (missed keyword variation)

Rule title.same_as_h1 · Titles · 36 occurrence(s)

notice Title is very short

Rule title.too_short · Titles · 22 occurrence(s)

notice Missing Twitter Card tag

Rule twitter.missing · Social · 44 occurrence(s)

notice Underscores in URL path (prefer hyphens)

Rule url.underscores · URL · 6 occurrence(s)

notice Uppercase letters in URL path

Rule url.uppercase · URL · 6 occurrence(s)

Pages (showing 50 of 50)
URLStatusIndexableWordsIn-links
http://www.tomstrong.org/
Tom Strong		 200 yes 394 35
https://www.tomstrong.org/physics/index.html
Mr. Strong’s Physics Class		 200 yes 106 6
http://www.tomstrong.org/physics/
Mr. Strong’s Physics Class		 200 yes 106 5
https://www.tomstrong.org/index.html
Tom Strong		 200 yes 394 13
http://www.tomstrong.org/public/
Index of /public		 200 yes 47 5
https://www.tomstrong.org/physics/archive
Index of /physics/archive		 200 yes 43 2
https://www.tomstrong.org/physics/bench.html
Virtual Optics Bench		 200 yes 18 2
https://www.tomstrong.org/physics/collision.html
Collisions		 200 yes 16 2
https://www.tomstrong.org/physics/lenses.html
Lens Animations		 200 yes 38 2
https://www.tomstrong.org/physics/mirrors.html
Mirror Animations		 200 yes 50 2
https://www.tomstrong.org/quotes/index.html
Quotes Page		 200 yes 127 8
https://www.tomstrong.org/quotes/q_A.html
A		 200 yes 7697 8
https://www.tomstrong.org/quotes/q_B.html
B		 200 yes 19729 8
https://www.tomstrong.org/quotes/q_C.html
C		 200 yes 16382 8
https://www.tomstrong.org/quotes/q_D.html
D		 200 yes 8555 8
https://www.tomstrong.org/quotes/q_E.html
E		 200 yes 6866 8
https://www.tomstrong.org/quotes/q_F.html
F		 200 yes 8933 8
http://www.tomstrong.org/recipes/
Recipes		 200 yes 139 5
https://www.tomstrong.org/public/crypto/
Index of /public/crypto		 200 yes 47 1
http://www.tomstrong.org/colors.html
RGB Web-Safe Color Chart		 200 yes 699 4
http://www.tomstrong.org/countries/
Country Information		 200 yes 116 4
http://www.tomstrong.org/gen/
Genealogy Pages		 200 yes 100 4
http://www.tomstrong.org/kappa/ 200 yes 20 4
http://www.tomstrong.org/links/
Links		 200 yes 289 4
http://www.tomstrong.org/patch/
Patch Collecting		 200 yes 208 4
http://www.tomstrong.org/photo/
Photography by Tom Strong		 200 yes 99 4
http://www.tomstrong.org/quotes/
Quotes Page		 200 yes 127 4
https://www.tomstrong.org/photo/headshots.html
Headshots by Tom Strong		 200 yes 58 4
https://www.tomstrong.org/links/food.html
Food and Drink		 200 yes 94 6
https://www.tomstrong.org/links/comp.html
Computers and Programming		 200 yes 89 6
https://www.tomstrong.org/links/ent.html
Entertainment		 200 yes 148 6
https://www.tomstrong.org/links/guns.html
Guns		 200 yes 96 6
https://www.tomstrong.org/links/misc.html
Misc. Links		 200 yes 197 6
https://www.tomstrong.org/links/scout.html
Scouting		 200 yes 156 6
https://www.tomstrong.org/photo/event.html
Event and Show Photography		 200 yes 87 3
https://www.tomstrong.org/photo/tech.html
Technical Photography		 200 yes 67 3
https://www.tomstrong.org/countries/au.html
Australia		 200 yes 177 1
https://www.tomstrong.org/gen/tree.html
Family Tree		 200 yes 231 1
https://www.tomstrong.org/patch/cspwant.html
Council Strip Want Lists		 200 yes 193 1
https://www.tomstrong.org/recipes/buttercream.html
Buttercream Icing		 200 yes 280 1
https://tomstrong.org/index.html
Tom Strong		 200 yes 394 2
https://tomstrong.org/bsa/adk.html
Adirondack Shelter Plans		 200 yes 662 1
https://tomstrong.org/bsa/
My Scouting Pages		 200 yes 52 2
https://tomstrong.org/others.html
Other Tom Strongs on the Web		 200 yes 90 2
https://tomstrong.org/
Tom Strong		 200 yes 394 0
https://www.tomstrong.org/gencolor.c 200 no 0 1
https://www.tomstrong.org/physics/fall08a.pdf 200 no 0 2
https://www.tomstrong.org/physics/fall08h.pdf 200 no 0 2
https://www.tomstrong.org/physics/year0809a.pdf 200 no 0 2
https://www.tomstrong.org/physics/year0809h.pdf 200 no 0 2

Audit your own site — free

157 checks, internal PageRank, render-diff. No signup, results in ~30s.

Scan your site →