Tools & Wizards About Us
shop.fandom.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

shop.fandom.com

Fandom

Page Load Speed

1.5 sec in total

First Response

29 ms

Resources Loaded

688 ms

Page Rendered

796 ms

shop.fandom.com screenshot

About Website

Click here to check amazing Shop Fandom content for United States. Otherwise, check out these important facts you probably never knew about shop.fandom.com

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.

Visit shop.fandom.com

Key Findings

We analyzed Shop.fandom.com page load time and found that the first response time was 29 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

shop.fandom.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value3,760 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.06

98/100

15%

TTI (Time to Interactive)

Value31.1 s

0/100

10%

Network Requests Diagram

www.fandom.com

29 ms

gpt.js

161 ms

css

92 ms

common.css

12 ms

news-and-stories.css

68 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Shop.fandom.com, 6% (5 requests) were made to Fandom.com and 6% (5 requests) were made to Community.fandom.com. The less responsive or slowest element that took the longest time to load (354 ms) relates to the external source Static.wikia.nocookie.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 473.8 kB (10%)

Content Size

4.8 MB

After Optimization

4.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Shop.fandom.com main page is 4.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 84.3 kB

  • Original 104.8 kB
  • After minification 97.9 kB
  • After compression 20.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 84.3 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 89.3 kB

  • Original 4.0 MB
  • After minification 3.9 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Shop Fandom images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 167.3 kB

  • Original 577.6 kB
  • After minification 577.6 kB
  • After compression 410.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 167.3 kB or 29% of the original size.

CSS Optimization

-77%

Potential reduce by 133.0 kB

  • Original 171.9 kB
  • After minification 171.7 kB
  • After compression 38.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Shop.fandom.com needs all CSS files to be minified and compressed as it can save up to 133.0 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (30%)

Requests Now

71

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shop Fandom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.fandom.com

www.fandom.com

29 ms

gpt.js

gpt.js

161 ms

css

css

92 ms

common.css

common.css

12 ms

news-and-stories.css

news-and-stories.css

68 ms

common.en.js

common.en.js

60 ms

news-and-stories.en.js

news-and-stories.en.js

58 ms

analytics.js

analytics.js

112 ms

ext.fandom.GlobalComponents.GlobalComponentsTheme.light.css

ext.fandom.GlobalComponents.GlobalComponentsTheme.light.css

115 ms

ext.fandom.GlobalComponents.GlobalNavigationTheme.light.css

ext.fandom.GlobalComponents.GlobalNavigationTheme.light.css

123 ms

globalNavigation.css

globalNavigation.css

268 ms

globalFooter.css

globalFooter.css

123 ms

mobileGlobalNavigation.css

mobileGlobalNavigation.css

121 ms

loader

loader

113 ms

sdk.js

sdk.js

127 ms

pathfinder.js

pathfinder.js

129 ms

analytics.js

analytics.js

31 ms

gtm.js

gtm.js

99 ms

6a181c72-e8bf-419b-b4db-18fd56a0eb60

6a181c72-e8bf-419b-b4db-18fd56a0eb60

30 ms

800

800

33 ms

800

800

281 ms

800

800

36 ms

800

800

41 ms

800

800

88 ms

800

800

87 ms

800

800

88 ms

800

800

88 ms

800

800

89 ms

800

800

90 ms

800

800

90 ms

800

800

91 ms

800

800

91 ms

800

800

92 ms

800

800

160 ms

800

800

187 ms

f986bbe3-d988-415a-be90-95912d7a7bdc

f986bbe3-d988-415a-be90-95912d7a7bdc

354 ms

6c42ce6a-b205-41f5-82c6-5011721932e7

6c42ce6a-b205-41f5-82c6-5011721932e7

277 ms

464fc70a-5090-490b-b47e-0759e89c263f

464fc70a-5090-490b-b47e-0759e89c263f

277 ms

f7bb9d33-4f9a-4faa-88fe-2a0bd8138668

f7bb9d33-4f9a-4faa-88fe-2a0bd8138668

237 ms

analytics.js

analytics.js

9 ms

pubads_impl.js

pubads_impl.js

210 ms

index.js

index.js

150 ms

8082.js

8082.js

220 ms

0dfbc1cb-6311-45e0-8b74-fc965ca9afc7

0dfbc1cb-6311-45e0-8b74-fc965ca9afc7

108 ms

1e17bced-251e-4c43-b3ac-ed39ee07cb94

1e17bced-251e-4c43-b3ac-ed39ee07cb94

107 ms

400

400

108 ms

400

400

253 ms

400

400

252 ms

400

400

106 ms

400

400

191 ms

400

400

191 ms

400

400

171 ms

400

400

328 ms

400

400

170 ms

400

400

172 ms

400

400

188 ms

400

400

255 ms

400

400

189 ms

400

400

190 ms

400

400

190 ms

400

400

190 ms

400

400

191 ms

400

400

192 ms

400

400

193 ms

400

400

215 ms

400

400

221 ms

400

400

221 ms

a1b620c0-0b7c-478f-ae53-3ddc8870ccdf

a1b620c0-0b7c-478f-ae53-3ddc8870ccdf

227 ms

643f0817-5bc1-414f-ac2a-936539ae3b20

643f0817-5bc1-414f-ac2a-936539ae3b20

225 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4i1Uw.woff

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4i1Uw.woff

137 ms

font

font

160 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYi1Uw.woff

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYi1Uw.woff

164 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-1Uw.woff

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-1Uw.woff

164 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-1Uw.woff

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-1Uw.woff

162 ms

136431902

136431902

113 ms

www.fandom.com.json

www.fandom.com.json

25 ms

84a07e3a698688683d493761c9786bde.js

84a07e3a698688683d493761c9786bde.js

28 ms

Accessibility Review

shop.fandom.com accessibility score

77

Accessibility Issues

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.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

shop.fandom.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

shop.fandom.com SEO score

91

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shop.fandom.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Shop.fandom.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

shop.fandom.com

Open Graph data is detected on the main page of Shop Fandom. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: