Catalog / closure.wiki
65

SEO audit for closure.wiki

Closure Wiki

other

Health 65/100 (fair) · 50 pages crawled · generated 2026-08-26

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

Closure Wiki is a comprehensive database and wiki resource for Arknights.

50
pages crawled
50
indexable pages
0
errors
105
warnings
449
notices
0
orphan pages
0
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Security 70 0 50 50
Performance 87 0 21 200
Agent Readiness 89 0 19 1
Duplicate 94 0 10 13
Content 98 0 4 65
Titles 99 0 1 2
Canonical 100 0 0 2
Images 100 0 0 50
Meta Description 100 0 0 8
Sitemap 100 0 0 2
Social 100 0 0 24
Structured Data 100 0 0 23
URL 100 0 0 9
Findings

Warnings (6 rules)

warning Control has no accessible name

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

warning Thin content (low word count)

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

warning Near-duplicate page content

Rule duplicate.near · Duplicate · 10 occurrence(s)

  • https://closure.wiki/operators/aphrissa — near-duplicate of 9 page(s): https://closure.wiki/operators/pedro, https://closure.wiki/operators/zinogre-s-catapult, https://closure.wiki/operators/vij
  • https://closure.wiki/operators/botani — near-duplicate of 9 page(s): https://closure.wiki/operators/pedro, https://closure.wiki/operators/aphrissa, https://closure.wiki/operators/zinogre-s-catapult
  • https://closure.wiki/operators/closure — near-duplicate of 9 page(s): https://closure.wiki/operators/pedro, https://closure.wiki/operators/aphrissa, https://closure.wiki/operators/zinogre-s-catapult
  • https://closure.wiki/operators/crackborne — near-duplicate of 9 page(s): https://closure.wiki/operators/pedro, https://closure.wiki/operators/aphrissa, https://closure.wiki/operators/zinogre-s-catapult
  • https://closure.wiki/operators/pedro — near-duplicate of 9 page(s): https://closure.wiki/operators/aphrissa, https://closure.wiki/operators/zinogre-s-catapult, https://closure.wiki/operators/vij
  • https://closure.wiki/operators/ripresa — near-duplicate of 9 page(s): https://closure.wiki/operators/pedro, https://closure.wiki/operators/aphrissa, https://closure.wiki/operators/zinogre-s-catapult
  • https://closure.wiki/operators/ukusik — near-duplicate of 9 page(s): https://closure.wiki/operators/pedro, https://closure.wiki/operators/aphrissa, https://closure.wiki/operators/zinogre-s-catapult
  • https://closure.wiki/operators/vij — near-duplicate of 9 page(s): https://closure.wiki/operators/pedro, https://closure.wiki/operators/aphrissa, https://closure.wiki/operators/zinogre-s-catapult
  • https://closure.wiki/operators/zima-the-raging-tide — near-duplicate of 9 page(s): https://closure.wiki/operators/pedro, https://closure.wiki/operators/aphrissa, https://closure.wiki/operators/zinogre-s-catapult
  • https://closure.wiki/operators/zinogre-s-catapult — near-duplicate of 9 page(s): https://closure.wiki/operators/pedro, https://closure.wiki/operators/aphrissa, https://closure.wiki/operators/vij

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

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

  • https://closure.wiki/ — 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://closure.wiki/about — 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://closure.wiki/avatars — 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://closure.wiki/avatars/avatar_dyn_01 — 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://closure.wiki/enemies — 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://closure.wiki/enemies/enemy_10193_ubhh — 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://closure.wiki/gallery — 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://closure.wiki/integrated-strategies-7 — 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://closure.wiki/items — 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://closure.wiki/items/5001 — 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://closure.wiki/medals — 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://closure.wiki/medals/medal_activity_act2break_10 — 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://closure.wiki/modules — 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://closure.wiki/modules/uniequip_002_mcnist — 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://closure.wiki/operations — 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://closure.wiki/operations/act21mini_01 — 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://closure.wiki/operators — 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://closure.wiki/operators/mechanist — 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://closure.wiki/operators?art=e2 — 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://closure.wiki/outfits — 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://closure.wiki/outfits/char_4198_christ@epoque%2356 — 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://closure.wiki/story — 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://closure.wiki/story/main_0 — 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://closure.wiki/summons — 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://closure.wiki/summons/token_10000_silent_healrb — 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 Hero/LCP image is lazy-loaded (loading=lazy delays LCP)

Rule images.no_lazy_lcp_candidate · Performance · 21 occurrence(s)

  • https://closure.wiki/ — the likely hero/LCP image (is7.danca86t.png) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/avatars — the likely hero/LCP image (avatar_dyn_01.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/avatars?page=2 — the likely hero/LCP image (avatar_activity_rl1_2.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/enemies — the likely hero/LCP image (enemy_10193_ubhh.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/enemies?page=2 — the likely hero/LCP image (enemy_2147_shophm.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/gallery — the likely hero/LCP image (bg_0_babel.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/items — the likely hero/LCP image (exp_player.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/items?page=2 — the likely hero/LCP image (act9d0_token_dogtag.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/medals — the likely hero/LCP image (medal_activity_act2break_10.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/medals?page=2 — the likely hero/LCP image (medal_story_hadiya_1.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/modules — the likely hero/LCP image (uniequip_002_mcnist.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/modules?page=2 — the likely hero/LCP image (uniequip_002_tecno.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/operations — the likely hero/LCP image (act21mini_01.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/operations?page=2 — the likely hero/LCP image (act2break_03.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/operators — the likely hero/LCP image (char_4230_mcnist_1.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/operators?art=e2 — the likely hero/LCP image (char_4230_mcnist_2.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/operators?page=2 — the likely hero/LCP image (char_4198_christ_1.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/outfits — the likely hero/LCP image (char_4198_christ_epoque%2356.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/outfits?page=2 — the likely hero/LCP image (char_4010_etlchi_winter%235.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/story — the likely hero/LCP image (main_0.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://closure.wiki/summons — the likely hero/LCP image (token_10070_aphris_pc.webp) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.

warning Title likely truncated in SERP (too wide)

Rule title.too_long · Titles · 1 occurrence(s)

Notices (21 rules)

notice No llms.txt for AI agents

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

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

notice Canonical points to a different URL

Rule canonical.non_self · Canonical · 2 occurrence(s)

notice Low text-to-HTML ratio

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

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

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

  • https://closure.wiki/ — this page reads as very difficult (Flesch Reading Ease 28, 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://closure.wiki/about — this page reads as very difficult (Flesch Reading Ease 21, 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://closure.wiki/avatars — this page reads as very difficult (Flesch Reading Ease -4, 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://closure.wiki/avatars/avatar_dyn_01 — this page reads as very difficult (Flesch Reading Ease -8, 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://closure.wiki/enemies — this page reads as very difficult (Flesch Reading Ease -15, 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://closure.wiki/enemies/enemy_10193_ubhh — this page reads as very difficult (Flesch Reading Ease 14, 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://closure.wiki/enemies?page=2 — this page reads as very difficult (Flesch Reading Ease -44, 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://closure.wiki/integrated-strategies-7 — this page reads as very difficult (Flesch Reading Ease -133, 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://closure.wiki/items — this page reads as very difficult (Flesch Reading Ease -36, 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://closure.wiki/items/5001 — 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://closure.wiki/medals — this page reads as very difficult (Flesch Reading Ease -45, 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://closure.wiki/medals/medal_activity_act2break_10 — this page reads as very difficult (Flesch Reading Ease 12, 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://closure.wiki/modules — this page reads as very difficult (Flesch Reading Ease 0, 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://closure.wiki/modules/uniequip_002_mcnist — this page reads as very difficult (Flesch Reading Ease -39, 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://closure.wiki/operations — this page reads as very difficult (Flesch Reading Ease -36, 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://closure.wiki/operations/act21mini_01 — this page reads as very difficult (Flesch Reading Ease -236, 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://closure.wiki/operators — this page reads as very difficult (Flesch Reading Ease -8, 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://closure.wiki/operators?art=e2 — this page reads as very difficult (Flesch Reading Ease -8, 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://closure.wiki/operators?page=2 — this page reads as very difficult (Flesch Reading Ease 1, 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://closure.wiki/outfits — this page reads as very difficult (Flesch Reading Ease 17, 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://closure.wiki/outfits/char_4198_christ@epoque%2356 — this page reads as difficult (Flesch Reading Ease 35, 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://closure.wiki/story — this page reads as very difficult (Flesch Reading Ease -56, 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://closure.wiki/story/main_0 — this page reads as very difficult (Flesch Reading Ease 16, 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://closure.wiki/summons — this page reads as very difficult (Flesch Reading Ease -18, 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://closure.wiki/summons/token_10000_silent_healrb — this page reads as very difficult (Flesch Reading Ease -16, 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 · 13 occurrence(s)

  • https://closure.wiki/avatars — meta description shared by 13 pages: https://closure.wiki/gallery, https://closure.wiki/operators, https://closure.wiki/enemies
  • https://closure.wiki/enemies — meta description shared by 13 pages: https://closure.wiki/gallery, https://closure.wiki/operators, https://closure.wiki/operations
  • https://closure.wiki/gallery — meta description shared by 13 pages: https://closure.wiki/operators, https://closure.wiki/enemies, https://closure.wiki/operations
  • https://closure.wiki/items — meta description shared by 13 pages: https://closure.wiki/gallery, https://closure.wiki/operators, https://closure.wiki/enemies
  • https://closure.wiki/medals — meta description shared by 13 pages: https://closure.wiki/gallery, https://closure.wiki/operators, https://closure.wiki/enemies
  • https://closure.wiki/modules — meta description shared by 13 pages: https://closure.wiki/gallery, https://closure.wiki/operators, https://closure.wiki/enemies
  • https://closure.wiki/operations — meta description shared by 13 pages: https://closure.wiki/gallery, https://closure.wiki/operators, https://closure.wiki/enemies
  • https://closure.wiki/operators — meta description shared by 13 pages: https://closure.wiki/gallery, https://closure.wiki/enemies, https://closure.wiki/operations
  • https://closure.wiki/outfits — meta description shared by 13 pages: https://closure.wiki/gallery, https://closure.wiki/operators, https://closure.wiki/enemies
  • https://closure.wiki/story — meta description shared by 13 pages: https://closure.wiki/gallery, https://closure.wiki/operators, https://closure.wiki/enemies
  • https://closure.wiki/story/main_0 — meta description shared by 13 pages: https://closure.wiki/gallery, https://closure.wiki/operators, https://closure.wiki/enemies
  • https://closure.wiki/story/main_0/1 — meta description shared by 13 pages: https://closure.wiki/gallery, https://closure.wiki/operators, https://closure.wiki/enemies
  • https://closure.wiki/summons — meta description shared by 13 pages: https://closure.wiki/gallery, https://closure.wiki/operators, https://closure.wiki/enemies

notice Likely hero image lacks fetchpriority=high

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

  • https://closure.wiki/avatars/avatar_dyn_01 — the likely hero/LCP image (avatar_dyn_01.webp) 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://closure.wiki/enemies/enemy_10193_ubhh — the likely hero/LCP image (enemy_10193_ubhh.webp) 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://closure.wiki/integrated-strategies-7 — the likely hero/LCP image (is7.danca86t.png) 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://closure.wiki/items/5001 — the likely hero/LCP image (exp_player.webp) 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://closure.wiki/medals/medal_activity_act2break_10 — the likely hero/LCP image (medal_activity_act2break_10.webp) 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://closure.wiki/modules/uniequip_002_mcnist — the likely hero/LCP image (uniequip_002_mcnist.webp) 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://closure.wiki/operations/act21mini_01 — the likely hero/LCP image (act21mini_01.webp) 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://closure.wiki/operators/aphrissa — the likely hero/LCP image (char_4229_aphris.webp) 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://closure.wiki/operators/botani — the likely hero/LCP image (char_4223_botany.webp) 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://closure.wiki/operators/closure — the likely hero/LCP image (char_4228_closur.webp) 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://closure.wiki/operators/crackborne — the likely hero/LCP image (char_4225_tanya.webp) 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://closure.wiki/operators/gallus — the likely hero/LCP image (char_4227_gallus.webp) 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://closure.wiki/operators/kaltsitesperanta — the likely hero/LCP image (char_1052_kalts2.webp) 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://closure.wiki/operators/mechanist — the likely hero/LCP image (char_4230_mcnist.webp) 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://closure.wiki/operators/pedro — the likely hero/LCP image (char_4234_pedro.webp) 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://closure.wiki/operators/rhodes-island-recon — the likely hero/LCP image (char_4215_buddy.webp) 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://closure.wiki/operators/ripresa — the likely hero/LCP image (char_4031_liesel.webp) 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://closure.wiki/operators/ukusik — the likely hero/LCP image (char_4224_turdus.webp) 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://closure.wiki/operators/vij — the likely hero/LCP image (char_4226_veen.webp) 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://closure.wiki/operators/violet-mizutsune-orchid — the likely hero/LCP image (char_1048_orchd2.webp) 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://closure.wiki/operators/zima-the-raging-tide — the likely hero/LCP image (char_1051_headb2.webp) 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://closure.wiki/operators/zinogre-s-catapult — the likely hero/LCP image (char_1049_catap2.webp) 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://closure.wiki/outfits/char_4198_christ@epoque%2356 — the likely hero/LCP image (char_4198_christ_epoque%2356.webp) 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://closure.wiki/story/main_0/1 — the likely hero/LCP image (bg_0_babel.webp) 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://closure.wiki/summons/token_10000_silent_healrb — the likely hero/LCP image (token_10000_silent_healrb.webp) 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 · 50 occurrence(s)

notice Meta description too long

Rule meta_desc.too_long · Meta Description · 1 occurrence(s)

notice Meta description too short

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

notice Missing Open Graph tags

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

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

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

  • https://closure.wiki/gallery — the page has 4267 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://closure.wiki/integrated-strategies-7 — the page has 3658 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://closure.wiki/operations/act21mini_01 — the page has 5083 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://closure.wiki/operators/aphrissa — the page has 6478 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://closure.wiki/operators/bellone — the page has 7947 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://closure.wiki/operators/botani — the page has 5397 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://closure.wiki/operators/closure — the page has 6441 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://closure.wiki/operators/crackborne — the page has 5410 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://closure.wiki/operators/gallus — the page has 2841 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://closure.wiki/operators/kaltsitesperanta — the page has 5972 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://closure.wiki/operators/mechanist — the page has 6692 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://closure.wiki/operators/pedro — the page has 4928 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://closure.wiki/operators/rhodes-island-recon — the page has 3174 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://closure.wiki/operators/ripresa — the page has 5239 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://closure.wiki/operators/taraxacum — the page has 5030 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://closure.wiki/operators/ukusik — the page has 5314 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://closure.wiki/operators/vij — the page has 6225 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://closure.wiki/operators/violet-mizutsune-orchid — the page has 6819 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://closure.wiki/operators/zima-the-raging-tide — the page has 6476 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://closure.wiki/operators/zinogre-s-catapult — the page has 6141 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 · 50 occurrence(s)

  • https://closure.wiki/ — 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://closure.wiki/about — 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://closure.wiki/avatars — 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://closure.wiki/avatars/avatar_dyn_01 — 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://closure.wiki/enemies — 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://closure.wiki/enemies/enemy_10193_ubhh — 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://closure.wiki/gallery — 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://closure.wiki/integrated-strategies-7 — 3 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://closure.wiki/items — 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://closure.wiki/items/5001 — 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://closure.wiki/medals — 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://closure.wiki/medals/medal_activity_act2break_10 — 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://closure.wiki/modules — 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://closure.wiki/modules/uniequip_002_mcnist — 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://closure.wiki/operations — 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://closure.wiki/operations/act21mini_01 — 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://closure.wiki/operators — 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://closure.wiki/operators/mechanist — 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://closure.wiki/operators?art=e2 — 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://closure.wiki/outfits — 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://closure.wiki/outfits/char_4198_christ@epoque%2356 — 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://closure.wiki/story — 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://closure.wiki/story/main_0 — 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://closure.wiki/summons — 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://closure.wiki/summons/token_10000_silent_healrb — 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.

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

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

  • https://closure.wiki/ — 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://closure.wiki/about — 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://closure.wiki/avatars — 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://closure.wiki/avatars/avatar_dyn_01 — 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://closure.wiki/enemies — 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://closure.wiki/enemies/enemy_10193_ubhh — 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://closure.wiki/gallery — 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://closure.wiki/integrated-strategies-7 — 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://closure.wiki/items — 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://closure.wiki/items/5001 — 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://closure.wiki/medals — 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://closure.wiki/medals/medal_activity_act2break_10 — 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://closure.wiki/modules — 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://closure.wiki/modules/uniequip_002_mcnist — 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://closure.wiki/operations — 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://closure.wiki/operations/act21mini_01 — 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://closure.wiki/operators — 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://closure.wiki/operators/mechanist — 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://closure.wiki/operators?art=e2 — 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://closure.wiki/outfits — 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://closure.wiki/outfits/char_4198_christ@epoque%2356 — 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://closure.wiki/story — 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://closure.wiki/story/main_0 — 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://closure.wiki/summons — 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://closure.wiki/summons/token_10000_silent_healrb — 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 · 50 occurrence(s)

  • https://closure.wiki/ — 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://closure.wiki/about — 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://closure.wiki/avatars — 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://closure.wiki/avatars/avatar_dyn_01 — 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://closure.wiki/enemies — 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://closure.wiki/enemies/enemy_10193_ubhh — 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://closure.wiki/gallery — 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://closure.wiki/integrated-strategies-7 — 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://closure.wiki/items — 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://closure.wiki/items/5001 — 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://closure.wiki/medals — 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://closure.wiki/medals/medal_activity_act2break_10 — 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://closure.wiki/modules — 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://closure.wiki/modules/uniequip_002_mcnist — 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://closure.wiki/operations — 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://closure.wiki/operations/act21mini_01 — 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://closure.wiki/operators — 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://closure.wiki/operators/mechanist — 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://closure.wiki/operators?art=e2 — 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://closure.wiki/outfits — 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://closure.wiki/outfits/char_4198_christ@epoque%2356 — 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://closure.wiki/story — 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://closure.wiki/story/main_0 — 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://closure.wiki/summons — 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://closure.wiki/summons/token_10000_silent_healrb — 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 · 3 occurrence(s)

notice No structured data detected

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

notice Missing recommended security headers

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

notice Indexable page not listed in sitemap

Rule sitemap.orphan_not_listed · Sitemap · 2 occurrence(s)

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

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

  • https://closure.wiki/ — the <title> and the H1 are identical — differentiate them to cover more query variation

notice Title is very short

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

notice Underscores in URL path (prefer hyphens)

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

Pages (showing 50 of 50)
URLStatusIndexableWordsIn-links
https://closure.wiki/
Closure Wiki		 200 yes 195 50
https://closure.wiki/about
About - Closure Wiki		 200 yes 195 50
https://closure.wiki/avatars
Avatars - Closure Wiki		 200 yes 536 50
https://closure.wiki/enemies
Enemies - Closure Wiki		 200 yes 493 50
https://closure.wiki/gallery
Gallery - Closure Wiki		 200 yes 1942 50
https://closure.wiki/integrated-strategies-7
Integrated Strategies #7: The Black Flow of the Drowning Seekers - Closure Wiki		 200 yes 1816 50
https://closure.wiki/items
Items - Closure Wiki		 200 yes 456 50
https://closure.wiki/medals
Medals - Closure Wiki		 200 yes 547 50
https://closure.wiki/modules
Modules - Closure Wiki		 200 yes 473 50
https://closure.wiki/operations
Operations - Closure Wiki		 200 yes 515 50
https://closure.wiki/operators
Operators - Closure Wiki		 200 yes 252 50
https://closure.wiki/outfits
Outfits - Closure Wiki		 200 yes 275 50
https://closure.wiki/story
Story Transcripts - Closure Wiki		 200 yes 567 50
https://closure.wiki/summons
Summons - Closure Wiki		 200 yes 324 50
https://closure.wiki/story/main_0
Evil Time Part 1 - Closure Wiki		 200 yes 150 2
https://closure.wiki/summons/token_10000_silent_healrb
Medic Drone - Closure Wiki		 200 yes 1159 1
https://closure.wiki/avatars/avatar_dyn_01
'Organization' - Closure Wiki		 200 yes 186 1
https://closure.wiki/avatars?page=2
Avatars - Closure Wiki		 200 yes 526 1
https://closure.wiki/enemies/enemy_10193_ubhh
撬棍巡逻者 - Closure Wiki		 200 yes 778 1
https://closure.wiki/enemies?page=2
Enemies - Closure Wiki		 200 yes 510 1
https://closure.wiki/items/5001
EXP - Closure Wiki		 200 yes 221 1
https://closure.wiki/items?page=2
Items - Closure Wiki		 200 yes 394 1
https://closure.wiki/medals/medal_activity_act2break_10
巫术之夜魄力奖章 - Closure Wiki		 200 yes 200 1
https://closure.wiki/medals?page=2
Medals - Closure Wiki		 200 yes 592 1
https://closure.wiki/modules/uniequip_002_mcnist
SO-A: 机械师特勤证章 - Closure Wiki		 200 yes 1097 1
https://closure.wiki/modules?page=2
Modules - Closure Wiki		 200 yes 492 1
https://closure.wiki/operations/act21mini_01
BD-1: 消耗品 - Closure Wiki		 200 yes 10129 1
https://closure.wiki/operations?page=2
Operations - Closure Wiki		 200 yes 518 1
https://closure.wiki/outfits/char_4198_christ@epoque%2356
底绒舞会 - Closure Wiki		 200 yes 236 1
https://closure.wiki/outfits?page=2
Outfits - Closure Wiki		 200 yes 326 1
https://closure.wiki/operators/aphrissa
Aphrissa - Closure Wiki		 200 yes 9692 2
https://closure.wiki/operators/bellone
Bellone - Closure Wiki		 200 yes 11960 2
https://closure.wiki/operators/botani
Ботани - Closure Wiki		 200 yes 8467 2
https://closure.wiki/operators/closure
Closure - Closure Wiki		 200 yes 10298 2
https://closure.wiki/operators/crackborne
Crackborne - Closure Wiki		 200 yes 8315 2
https://closure.wiki/operators/gallus
GALLUS² - Closure Wiki		 200 yes 3750 2
https://closure.wiki/operators/kaltsitesperanta
Kal'tsit·Esperanta - Closure Wiki		 200 yes 8987 2
https://closure.wiki/operators/mechanist
Mechanist - Closure Wiki		 200 yes 10349 2
https://closure.wiki/operators/pedro
Pedro - Closure Wiki		 200 yes 7325 2
https://closure.wiki/operators/rhodes-island-recon
Rhodes Island Recon - Closure Wiki		 200 yes 4258 2
https://closure.wiki/operators/ripresa
Ripresa - Closure Wiki		 200 yes 8083 2
https://closure.wiki/operators/taraxacum
Taraxacum - Closure Wiki		 200 yes 14278 2
https://closure.wiki/operators/ukusik
Укусик - Closure Wiki		 200 yes 8304 2
https://closure.wiki/operators/vij
Вий - Closure Wiki		 200 yes 9576 2
https://closure.wiki/operators/violet-mizutsune-orchid
Violet Mizutsune Orchid - Closure Wiki		 200 yes 10298 2
https://closure.wiki/operators/zima-the-raging-tide
Zima the Raging Tide - Closure Wiki		 200 yes 9859 2
https://closure.wiki/operators/zinogre-s-catapult
Zinogre S Catapult - Closure Wiki		 200 yes 9103 2
https://closure.wiki/operators?art=e2
Operators - Closure Wiki		 200 yes 252 1
https://closure.wiki/operators?page=2
Operators - Closure Wiki		 200 yes 224 1
https://closure.wiki/story/main_0/1
Prologue, Part 1 - Closure Wiki		 200 yes 1011 1

Audit your own site — free

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

Scan your site →