Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
cdn.cookielaw.org/scripttemplates/202510.1.0/otBannerSdk.js	86400.0 s	123.3 KiB
static.wikia.nocookie.net/silversurfer/prod/latest/sdk.js	10800.0 s	32.4 KiB
static.wikia.nocookie.net/silversurfer/prod/latest/pathfinder.js	10800.0 s	31.1 KiB
/scripts/bundle/65568.js?sid=ed1edc0e-ce73-462e-8cc4-fe04...	3600.0 s	20.9 KiB
/fandom-ae-assets/odyssey/identity-engine/production/main.js	86400.0 s	27.4 KiB
www.fandom.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?	14400.0 s	12.1 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/...	14400.0 s	12.0 KiB
script.wikia.nocookie.net/fandom-ae-assets/odyssey/host/production/main.js	86400.0 s	16.6 KiB
/logos/67a90ba4-3081-4d74-98ab-8ed228a512fa/dea70a1b-c82d...	86400.0 s	11.9 KiB
static.wikia.nocookie.net/silversurfer/prod/latest/sdk-cross-domain.js	10800.0 s	6.5 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
cdn.brandmetrics.com/tag/dd830904-53f5-42f0-9d96-967434572877/fandom.com.js	3600.0 s	4.3 KiB
/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c124171768917...	86400.0 s	6.9 KiB
sb.scorecardresearch.com/internal-cs/default/beacon.js	86400.0 s	6.8 KiB
script.crazyegg.com/pages/scripts/0129/6552.js	300.0 s	2.7 KiB
/__cb3778051113870605/resources-ucp/mw143/dist/scripts/pa...	43200.0 s	4.5 KiB
rules.quantcount.com/rules-p-8bG6eLqkH6Avk.js	3600.0 s	1.6 KiB
/__cb3778051113870605/resources-ucp/mw143/dist/scripts/dt...	43200.0 s	2.2 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg	86400.0 s	2.5 KiB
/c.js?siteid=ed1edc0e-ce73-462e-8cc4-fe0421bcd00f&toploc=...	0.0 ms	289 B
cdn.cookielaw.org/logos/static/ot_close.svg	86400.0 s	603 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV

nodeLabel: body.mainpage > div.main-container > div.fandom-community-header__background

path: 1,HTML,1,BODY,4,DIV,2,DIV

selector: body.mainpage > div.main-container > div.fandom-community-header__background

snippet: <div class="fandom-community-header__background cover header " style="--image-ratio:0.5625">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
/load.php?lang=en&modules=ext.fandom.ArticleInterlang.css...	43.3 KiB	123 ms
/load.php?lang=en&modules=site.styles&only=styles&skin=fa...	6.9 KiB
/load.php?articles=MediaWiki:Mainpage.css\|MediaWiki:Badge...	7.3 KiB

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
CommunityProgrHub-Header `div.fandom_programming > figure.mw-halign-center > a > img.mw-file-element`	/central/images/2/27/CommunityProgrHub-Header.png/revisio...	13.8 KiB	10.5 KiB
MainPageCCHeader `div.mainpageccheader > figure.mw-halign-center > span > img.mw-file-element`	/central/images/7/75/MainPageCCHeader.png/revision/latest...	23.5 KiB	5.7 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 30 ms 55.4 KiB

URL	Transfer Size	Est Savings
/load.php?lang=en&modules=ext.fandom.ArticleInterlang.css...	43.0 KiB	35.8 KiB
	22.3 KiB	19.6 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 263.3 KiB

URL	Transfer Size	Est Savings
/load.php?lang=en&modules=ext.fandom.HighlightToAction.js...	212.7 KiB	111.1 KiB
cdn.cookielaw.org/scripttemplates/202510.1.0/otBannerSdk.js	123.2 KiB	64.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-N6XD44P	137.3 KiB	58.9 KiB
/pages/versioned/common-scripts/4ce8c7df8d425cc5046457682...	55.1 KiB	28.5 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 557 ms

URL	Time Spent
wikia.com/	311 ms
community.fandom.com/	245 ms
community.fandom.com/wiki/Community_Central	0.0 ms

●Time to Interactive 1.4 s

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 50 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,383 KiB

●User Timing marks and measures 12 user timings

●JavaScript execution time 0.6 s

●Minimizes main-thread work 1.5 s

●Avoid long main-thread tasks 1 long task found

●Avoid non-composited animations 2 animated elements found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 140 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 30 ms

●Avoid large layout shifts 6 layout shifts found

○INP breakdown

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
EXPLORE `nav.fandom-community-header__local-navigation > ul.wds-tabs > li.wds-dropdown > div.wds-tabs__tab-label`
GET STARTED WITH FANDOM `nav.fandom-community-header__local-navigation > ul.wds-tabs > li.wds-dropdown > div.wds-tabs__tab-label`
I NEED HELP `nav.fandom-community-header__local-navigation > ul.wds-tabs > li.wds-dropdown > div.wds-tabs__tab-label`
I WANT TO LEARN `nav.fandom-community-header__local-navigation > ul.wds-tabs > li.wds-dropdown > div.wds-tabs__tab-label`
AROUND FANDOM `nav.fandom-community-header__local-navigation > ul.wds-tabs > li.wds-dropdown > div.wds-tabs__tab-label`
English `div.page-header__top > div.page-header__languages > div.wds-dropdown > div.wds-dropdown__toggle`
Categories `main.page__main > div.page-footer > div.wds-collapsible-panel > header.wds-collapsible-panel__header`
Languages `main.page__main > div.page-footer > div.wds-collapsible-panel > header.wds-collapsible-panel__header`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Introducing "Collections" on Fandom (Beta) `div.blog-info > div.details > div.title > a`
Introducing the Animal Crossing: New Horizons Game Companion on Fandom `div.blog-info > div.details > div.title > a`
Learning, Listening, and Localizing: Reflections from Our AI Translation Pilot `div.blog-info > div.details > div.title > a`
Internationalization Experiment: Latest Updates `div.blog-info > div.details > div.title > a`
Community Partnerships September Update: Gaming Highlights `div.blog-info > div.details > div.title > a`
Community Partnerships Update: Paid Partnerships and Community Benefits `div.blog-info > div.details > div.title > a`
Our Third Annual Transparency Report `div.blog-info > div.details > div.title > a`
Across Fandoms: A Lookback On 2025 Events `div.blog-info > div.details > div.title > a`
Signing up `div.faq-list > ul > li > a`
Changing your preferences `div.faq-list > ul > li > a`
Managing your account `div.faq-list > ul > li > a`
Updating your profile `div.faq-list > ul > li > a.mw-redirect`
Notifications `div.faq-list > ul > li > a`
Creating a wiki `div.faq-list > ul > li > a`
Administrators' how-to guide `div.faq-list > ul > li > a`
Common mistakes `div.faq-list > ul > li > a`
More on Getting Started `div.faq-section > div.faq-list > div.mainpage-more > a`
Editing a page `div.faq-list > ul > li > a`
Creating a new page `div.faq-list > ul > li > a`
Uploading photos `div.faq-list > ul > li > a`
Adding videos `div.faq-list > ul > li > a`
Inserting links `div.faq-list > ul > li > a`
Adding categories `div.faq-list > ul > li > a`
Dealing with templates `div.faq-list > ul > li > a`
Using wikitext `div.faq-list > ul > li > a`
More on Contributing `div.faq-section > div.faq-list > div.mainpage-more > a`
Using the theme designer `div.faq-list > ul > li > a.mw-redirect`
Changing the background image `div.faq-list > ul > li > a`
Uploading a new favicon `div.faq-list > ul > li > a`
Using colors `div.faq-list > ul > li > a`
Updating the wiki navigation `div.faq-list > ul > li > a`
Customization policy `div.faq-list > ul > li > a.mw-redirect`
Adding and updating tables `div.faq-list > ul > li > a`
Working with infoboxes `div.faq-list > ul > li > a`
Complete Customization Tips `div.faq-section > div.faq-list > div.mainpage-more > a`
Copyright complaints `div.faq-list > ul > li > a.external`
Enabling new wiki features `div.faq-list > ul > li > a.mw-redirect`
Enabling extensions `div.faq-list > ul > li > a`
Protecting a page `div.faq-list > ul > li > a.mw-disambig`
Navigating the admin dashboard `div.faq-list > ul > li > a`
Working with special pages `div.faq-list > ul > li > a`
Blocking users `div.faq-list > ul > li > a`
Handling conflict `div.faq-list > ul > li > a`
Community Management Tips `div.faq-section > div.faq-list > div.mainpage-more > a`
All Frequently Asked Questions `div.lcs-container > div#mainpage-faq > div.mainpage-more > a`
20 Apr 2026 `div.blog-info > div.details > div.created > span.timestamp`
Technical Updates: April 20, 2026 `div.blog-info > div.details > div.title > a`
7 Apr 2026 `div.blog-info > div.details > div.created > span.timestamp`
Technical Updates: April 7, 2026 `div.blog-info > div.details > div.title > a`
31 Mar 2026 `div.blog-info > div.details > div.created > span.timestamp`
Trans Day of Visibility 2026 `div.blog-info > div.details > div.title > a`
31 Mar 2026 `div.blog-info > div.details > div.created > span.timestamp`
Trans Day of Visibility 2026 `div.blog-info > div.details > div.title > a`
15 Apr 2025 `div.blog-info > div.details > div.created > span.timestamp`
Introducing the Admin Code of Conduct `div.blog-info > div.details > div.title > a`
18 Sep 2024 `div.blog-info > div.details > div.created > span.timestamp`
Fandom Publishes New Policy Regarding Offensive Language `div.blog-info > div.details > div.title > a`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
community discussions `div > div > p > a`
staff blog posts `div > div > p > a`
help pages `div > div > p > a`
Getting Started With Contributing to Wikis `div.mainpage-box > div.contributing-for-newcomers > div.advice-card > a`
Visit page `div.mainpage-box > div.contributing-for-newcomers > div.advice-card > a.text`
Go directly to the contribution mode `div.mainpage-box > div.contributing-for-newcomers > div.advice-card > a.text`
CC-BY-SA `main.page__main > div.page-footer > div.license-description > a`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Getting Started `div#mainpage-faq > div.faqs > div.faq-section > h4`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.highlight__actions > div.highlight__d-flex > div.highlight__action > a `div.highlight__actions > div.highlight__d-flex > div.highlight__action > a`
div.highlight__actions > div.highlight__d-flex > div.highlight__action > a `div.highlight__actions > div.highlight__d-flex > div.highlight__action > a`
div.highlight__actions > div.highlight__d-flex > div.highlight__action > a `div.highlight__actions > div.highlight__d-flex > div.highlight__action > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy Policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`[accesskey]` values are unique

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
SharedStorage	community.fandom.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	community.fandom.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	community.fandom.com/cdn-cgi/challenge-platform/scripts/jsd/main.js

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
services.fandom.com/active-data-management-service/profiles?cb=1776798759390	`Failed to load resource: the server responded with a status of 400 ()`
services.fandom.com/galactus-user-profile/profiles/txoT2kNMmN	`Failed to load resource: the server responded with a status of 404 ()`
static.wikia.nocookie.net/silversurfer/prod/latest/sdk.js	`logErrorEvent [object Object]`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Map URL
/load.php?lang=en&modules=ext.fandom.HighlightToAction.js...	/load.php?lang=en&modules=ext.fandom.HighlightToAction.js...
/fandom-ae-assets/odyssey/identity-engine/production/main.js	/fandom-ae-assets/odyssey/identity-engine/production/main...
/load.php?lang=en&modules=sitenoticeVisibility-CPygwrNm.j...	/load.php?lang=en&modules=sitenoticeVisibility-CPygwrNm.j...
/load.php?lang=en&modules=mediawiki.template%7Cmediawiki....	/load.php?lang=en&modules=mediawiki.template%7Cmediawiki....
/load.php?lang=en&modules=ext.visualEditor.core.utils.par...	/load.php?lang=en&modules=ext.visualEditor.core.utils.par...
/load.php?lang=en&modules=ext.fandom.ImportJs%2Csite&skin...	/load.php?lang=en&modules=ext.fandom.ImportJs%2Csite&skin...
/load.php?lang=en&modules=AuthModal-BMITjg9x.js%7CCreateP...	/load.php?lang=en&modules=AuthModal-BMITjg9x.js%7CCreateP...
/load.php?cb=20260330140938&lang=en&modules=startup&only=...	/load.php?cb=20260330140938&lang=en&modules=startup&only=...
static.wikia.nocookie.net/silversurfer/prod/latest/sdk.js	static.wikia.nocookie.net/silversurfer/prod/latest/sdk.js.map
static.wikia.nocookie.net/silversurfer/prod/latest/pathfinder.js	static.wikia.nocookie.net/silversurfer/prod/latest/pathfinder.js.map
script.wikia.nocookie.net/fandom-ae-assets/odyssey/host/production/main.js	script.wikia.nocookie.net/fandom-ae-assets/odyssey/host/production/main.js.map

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
community.fandom.com/wiki/Community_Central:Staff_Blog/Product_Updates	Read more
community.fandom.com/wiki/Community_Central:Staff_Blog/Experiments_and_Tweaks	Read more
community.fandom.com/wiki/Community_Central:Staff_Blog/Community_Partnerships	Read more
community.fandom.com/wiki/Community_Central:Staff_Blog/Community_Updates	Read more
community.fandom.com/wiki/Community_Central:Staff_Blog/Technical_Updates	Read more
/wiki/Community_Central:Staff_Blog/Diversity,_Equality_an...	Read more
community.fandom.com/wiki/Community_Central:Staff_Blog/Policy_Updates	Read more

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid