Tools & Wizards About Us
blakes7.fandom.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

blakes7.fandom.com

Blake's 7 Wiki | Blakes 7 Wiki | Fandom

Page Load Speed

1.3 sec in total

First Response

95 ms

Resources Loaded

1.1 sec

Page Rendered

176 ms

blakes7.fandom.com screenshot

About Website

Visit blakes7.fandom.com now to see the best up-to-date Blake S 7 Fandom content for United States and also check out these interesting facts you probably never knew about blakes7.fandom.com

Visit blakes7.fandom.com

Key Findings

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

Performance Metrics

blakes7.fandom.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

98/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value8,130 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.048

99/100

15%

TTI (Time to Interactive)

Value42.6 s

0/100

10%

Network Requests Diagram

Blake%27s_7_Wiki

95 ms

load.php

156 ms

load.php

326 ms

load.php

99 ms

wikia.php

123 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 50% of them (11 requests) were addressed to the original Blakes7.fandom.com, 36% (8 requests) were made to Static.wikia.nocookie.net and 5% (1 request) were made to Services.fandom.com. The less responsive or slowest element that took the longest time to load (494 ms) relates to the external source Static.wikia.nocookie.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 107.4 kB (46%)

Content Size

234.2 kB

After Optimization

126.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Blakes7.fandom.com main page is 234.2 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. 25% of websites need less resources to load. HTML takes 132.5 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 96.6 kB

  • Original 132.5 kB
  • After minification 125.7 kB
  • After compression 35.9 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 96.6 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 24.6 kB
  • After minification 24.6 kB

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. Blake S 7 Fandom images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 10.7 kB

  • Original 77.2 kB
  • After minification 77.2 kB
  • After compression 66.4 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 10.7 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (62%)

Requests Now

21

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blake S 7 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 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Blake%27s_7_Wiki

Blake%27s_7_Wiki

95 ms

load.php

load.php

156 ms

load.php

load.php

326 ms

load.php

load.php

99 ms

wikia.php

wikia.php

123 ms

sdk.js

sdk.js

48 ms

pathfinder.js

pathfinder.js

50 ms

loader

loader

40 ms

scout.js

scout.js

39 ms

load.php

load.php

145 ms

css

css

28 ms

36

36

494 ms

180

180

166 ms

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

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

165 ms

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

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

166 ms

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

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

169 ms

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

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

174 ms

load.php

load.php

78 ms

load.php

load.php

78 ms

load.php

load.php

209 ms

load.php

load.php

265 ms

load.php

load.php

184 ms

Accessibility Review

blakes7.fandom.com accessibility score

79

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

Form elements do not have associated labels

Best Practices

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

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

SEO Factors

blakes7.fandom.com SEO score

76

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

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

blakes7.fandom.com

Open Graph description is not detected on the main page of Blake S 7 Fandom. 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: