Fandom.com Site Title

Fandom

Fandom.com Meta Description

The entertainment site where fans come first. Your daily source for all things TV, movies, and games, including Star Wars, Fallout, Marvel, DC and more.

Fandom.com Test Results

Fandom.com Mobile Performance: 13/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Reduce unused JavaScript. Potential savings of 449 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn more.
Defer offscreen images. Potential savings of 115 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Serve images in next-gen formats. Potential savings of 128 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Efficiently encode images. Potential savings of 95 KiB
Optimized images load faster and consume less cellular data. Learn more.
Reduce unused CSS. Potential savings of 31 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn more.
Minify JavaScript. Potential savings of 10 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
Avoid serving legacy JavaScript to modern browsers. Potential savings of 45 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn More
Eliminate render-blocking resources. Potential savings of 150 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Minimize main-thread work
22.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Reduce the impact of third-party code
Third-party code blocked the main thread for 3,490 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Avoid an excessive DOM size
3,283 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Reduce JavaScript execution time
12.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Serve static assets with an efficient cache policy
39 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid enormous network payloads
Total size was 2,869 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Avoid large layout shifts
4 elements found
These DOM elements contribute most to the CLS of the page.
Avoid long main-thread tasks
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Avoid chaining critical requests
2 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Keep request counts low and transfer sizes small
218 requests • 2,869 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
User Timing marks and measures
6 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Fandom.com Mobile SEO: 85/100
Quick overview:
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Tap targets are not sized appropriately
98% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a valid `rel=canonical`
Canonical links suggest which URL to show in search results. Learn more. Multiple conflicting URLs (https://www.fandom.com/, https://www.fandom.com/topics/home-page)
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.

Fandom.com Mobile Best Practices: 67/100
Quick overview:
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Includes front-end JavaScript libraries with known security vulnerabilities
2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead. Learn more
Fandom.com Mobile Progressive Web App: 75/100
Quick overview:
PWA Optimized
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: Manifest does not have a PNG icon of at least 512px, Manifest does not have `background_color`.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more.
Fandom.com Mobile Accessibility: 73/100
Quick overview:
Names and labels
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.
Links do not have a discernible name
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 more.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Similar sites
Similar tests
www.fandom.com
www.fandom.net
www.fandom.org
www.fandom.info
www.fandom.biz
www.fandom.us
www.fandom.mobi
www.andom.com
www.fandom.com
www.candom.com
www.fcandom.com
www.cfandom.com
www.dandom.com
www.fdandom.com
www.dfandom.com
www.random.com
www.frandom.com
www.rfandom.com
www.tandom.com
www.ftandom.com
www.tfandom.com
www.gandom.com
www.fgandom.com
www.gfandom.com
www.vandom.com
www.fvandom.com
www.vfandom.com
www.fndom.com
www.fqndom.com
www.faqndom.com
www.fqandom.com
www.fwndom.com
www.fawndom.com
www.fwandom.com
www.fsndom.com
www.fasndom.com
www.fsandom.com
www.fzndom.com
www.fazndom.com
www.fzandom.com
www.fadom.com
www.fabdom.com
www.fanbdom.com
www.fabndom.com
www.fahdom.com
www.fanhdom.com
www.fahndom.com
www.fajdom.com
www.fanjdom.com
www.fajndom.com
www.famdom.com
www.fanmdom.com
www.famndom.com
www.fanom.com
www.fanxom.com
www.fandxom.com
www.fanxdom.com
www.fansom.com
www.fandsom.com
www.fansdom.com
www.faneom.com
www.fandeom.com
www.fanedom.com
www.fanrom.com
www.fandrom.com
www.fanrdom.com
www.fanfom.com
www.fandfom.com
www.fanfdom.com
www.fancom.com
www.fandcom.com
www.fancdom.com
www.fandm.com
www.fandim.com
www.fandoim.com
www.fandiom.com
www.fandkm.com
www.fandokm.com
www.fandkom.com
www.fandlm.com
www.fandolm.com
www.fandlom.com
www.fandpm.com
www.fandopm.com
www.fandpom.com
www.fando.com
www.fandon.com
www.fandomn.com
www.fandonm.com
www.fandoj.com
www.fandomj.com
www.fandojm.com
www.fandok.com
www.fandomk.com
www.fandom.con
Last Tested: