Tools & Wizards About Us
teamfandom.com screenshot

Report Summary

  • 85

    Performance

    Renders faster than
    88% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

teamfandom.com

teamfandom.com

Page Load Speed

357 ms in total

First Response

49 ms

Resources Loaded

181 ms

Page Rendered

127 ms

teamfandom.com screenshot

About Website

Click here to check amazing Teamfandom content. Otherwise, check out these important facts you probably never knew about teamfandom.com

Visit teamfandom.com

Key Findings

We analyzed Teamfandom.com page load time and found that the first response time was 49 ms and then it took 308 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

teamfandom.com performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.063

97/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

teamfandom.com

49 ms

script.js

43 ms

UX.4.43.0.js

45 ms

script.js

54 ms

scc-c2.min.js

10 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that 20% of them (1 request) were addressed to the original Teamfandom.com, 80% (4 requests) were made to Img1.wsimg.com. The less responsive or slowest element that took the longest time to load (54 ms) relates to the external source Img1.wsimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 362.5 kB (71%)

Content Size

511.8 kB

After Optimization

149.3 kB

  • HTML
  • JavaScript

In fact, the total size of Teamfandom.com main page is 511.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 443.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 57.8 kB

  • Original 68.6 kB
  • After minification 68.6 kB
  • After compression 10.8 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 57.8 kB or 84% of the original size.

JavaScript Optimization

-69%

Potential reduce by 304.7 kB

  • Original 443.2 kB
  • After minification 443.2 kB
  • After compression 138.5 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 304.7 kB or 69% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (75%)

Requests Now

4

After Optimization

1

  • JavaScript

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

Network Requests Diagram

teamfandom.com

teamfandom.com

49 ms

script.js

script.js

43 ms

UX.4.43.0.js

UX.4.43.0.js

45 ms

script.js

script.js

54 ms

scc-c2.min.js

scc-c2.min.js

10 ms

Accessibility Review

teamfandom.com accessibility score

99

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

teamfandom.com best practices score

92

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

Page has valid source maps

SEO Factors

teamfandom.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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 Teamfandom.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 Teamfandom.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

teamfandom.com

Open Graph description is not detected on the main page of Teamfandom. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: