Tools & Wizards About Us
shop.fandom.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

shop.fandom.com

Fandom

Page Load Speed

10 sec in total

First Response

110 ms

Resources Loaded

3.4 sec

Page Rendered

6.5 sec

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 110 ms and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

shop.fandom.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

61/100

25%

SI (Speed Index)

Value23.9 s

0/100

10%

TBT (Total Blocking Time)

Value51,460 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.078

95/100

15%

TTI (Time to Interactive)

Value64.7 s

0/100

10%

Network Requests Diagram

www.fandom.com

110 ms

css

986 ms

common.css

23 ms

news-and-stories.css

450 ms

common.en.js

873 ms

Our browser made a total of 71 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, 7% (5 requests) were made to Fandom.com and 7% (5 requests) were made to Community.fandom.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Static.wikia.nocookie.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 369.6 kB (6%)

Content Size

5.8 MB

After Optimization

5.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Shop.fandom.com main page is 5.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 5.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 86.8 kB

  • Original 106.4 kB
  • After minification 99.3 kB
  • After compression 19.7 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 86.8 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 242.3 kB

  • Original 5.4 MB
  • After minification 5.2 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

-17%

Potential reduce by 40.4 kB

  • Original 235.2 kB
  • After minification 235.2 kB
  • After compression 194.7 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 40.4 kB or 17% of the original size.

CSS Optimization

-0%

Potential reduce by 134 B

  • Original 35.8 kB
  • After minification 35.8 kB
  • After compression 35.6 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (23%)

Requests Now

65

After Optimization

50

  • Images
  • JavaScript
  • CSS

The browser has sent 65 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 9 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

110 ms

css

css

986 ms

common.css

common.css

23 ms

news-and-stories.css

news-and-stories.css

450 ms

common.en.js

common.en.js

873 ms

news-and-stories.en.js

news-and-stories.en.js

792 ms

analytics.js

analytics.js

1074 ms

ext.fandom.GlobalComponents.GlobalComponentsTheme.light.css

ext.fandom.GlobalComponents.GlobalComponentsTheme.light.css

1091 ms

ext.fandom.GlobalComponents.GlobalNavigationTheme.light.css

ext.fandom.GlobalComponents.GlobalNavigationTheme.light.css

1152 ms

globalNavigation.css

globalNavigation.css

1150 ms

globalFooter.css

globalFooter.css

1232 ms

mobileGlobalNavigation.css

mobileGlobalNavigation.css

1231 ms

loader

loader

1136 ms

sdk.js

sdk.js

1135 ms

pathfinder.js

pathfinder.js

1136 ms

analytics.js

analytics.js

247 ms

gtm.js

gtm.js

1179 ms

c8710a5e-97c6-4245-8195-9179cc91d2f2

c8710a5e-97c6-4245-8195-9179cc91d2f2

875 ms

800

800

1257 ms

800

800

874 ms

800

800

1053 ms

800

800

1276 ms

800

800

1053 ms

800

800

1114 ms

800

800

1110 ms

800

800

1246 ms

800

800

1255 ms

800

800

1264 ms

800

800

1262 ms

800

800

1273 ms

800

800

1272 ms

800

800

1269 ms

800

800

1271 ms

800

800

1270 ms

f986bbe3-d988-415a-be90-95912d7a7bdc

f986bbe3-d988-415a-be90-95912d7a7bdc

1291 ms

ff185fe4-8356-4b6b-ad48-621b95a82a1d

ff185fe4-8356-4b6b-ad48-621b95a82a1d

1269 ms

f3fc9271-3d5e-4c73-9afc-e6a9f6154ff1

f3fc9271-3d5e-4c73-9afc-e6a9f6154ff1

1280 ms

3f46912f-45a8-47f0-ac9d-6dca02c3a5ca

3f46912f-45a8-47f0-ac9d-6dca02c3a5ca

1280 ms

6e8f2e52-ab5a-427f-a836-ab57168161ec

6e8f2e52-ab5a-427f-a836-ab57168161ec

1293 ms

analytics.js

analytics.js

654 ms

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

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

1018 ms

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

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

1016 ms

400

400

1049 ms

400

400

1383 ms

400

400

1285 ms

400

400

595 ms

400

400

753 ms

400

400

751 ms

400

400

1228 ms

400

400

1360 ms

400

400

1041 ms

400

400

1111 ms

400

400

1277 ms

400

400

1471 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4i1UE80V4ftkw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4i1UE80V4ftkw.ttf

534 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYi1UE80V4ftkw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYi1UE80V4ftkw.ttf

705 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYi1UE80V4ftkw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYi1UE80V4ftkw.ttf

802 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-1UE80V4ftkw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-1UE80V4ftkw.ttf

907 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-1UE80V4ftkw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-1UE80V4ftkw.ttf

1030 ms

400

400

784 ms

400

400

800 ms

400

400

787 ms

400

400

687 ms

400

400

686 ms

400

400

690 ms

400

400

867 ms

400

400

812 ms

400

400

824 ms

400

400

679 ms

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

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

657 ms

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

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

649 ms

Accessibility Review

shop.fandom.com accessibility score

78

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

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

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: