Tools & Wizards About Us
rebirth-of-the-urban-immortal-cultivator.fandom.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

rebirth-of-the-urban-immortal-cultivator.fandom.com

Rebirth of the Urban Immortal Cultivator Wiki | Fandom

Page Load Speed

660 ms in total

First Response

26 ms

Resources Loaded

393 ms

Page Rendered

241 ms

rebirth-of-the-urban-immortal-cultivator.fandom.com screenshot

About Website

Click here to check amazing Rebirth Of The Urban Immortal Cultivator Fandom content for United States. Otherwise, check out these important facts you probably never knew about rebirth-of-the-urban-immortal-cultivator.fandom.com

Visit rebirth-of-the-urban-immortal-cultivator.fandom.com

Key Findings

We analyzed Rebirth-of-the-urban-immortal-cultivator.fandom.com page load time and found that the first response time was 26 ms and then it took 634 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

rebirth-of-the-urban-immortal-cultivator.fandom.com performance score

51

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)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value9,790 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value42.6 s

0/100

10%

Network Requests Diagram

Rebirth_of_the_Urban_Immortal_Cultivator_Wiki

26 ms

load.php

130 ms

load.php

344 ms

wikia.php

111 ms

sdk.js

38 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 25% of them (4 requests) were addressed to the original Rebirth-of-the-urban-immortal-cultivator.fandom.com, 63% (10 requests) were made to Static.wikia.nocookie.net and 6% (1 request) were made to Services.fandom.com. The less responsive or slowest element that took the longest time to load (344 ms) belongs to the original domain Rebirth-of-the-urban-immortal-cultivator.fandom.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 167.3 kB (43%)

Content Size

390.6 kB

After Optimization

223.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Rebirth-of-the-urban-immortal-cultivator.fandom.com main page is 390.6 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. 20% of websites need less resources to load. HTML takes 198.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 154.7 kB

  • Original 198.2 kB
  • After minification 181.5 kB
  • After compression 43.4 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 154.7 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 4.9 kB

  • Original 125.0 kB
  • After minification 120.1 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. Rebirth Of The Urban Immortal Cultivator Fandom images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 7.6 kB

  • Original 67.4 kB
  • After minification 67.4 kB
  • After compression 59.8 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 7.6 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (27%)

Requests Now

15

After Optimization

11

  • Images
  • JavaScript
  • CSS

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rebirth Of The Urban Immortal Cultivator 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 5 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

Rebirth_of_the_Urban_Immortal_Cultivator_Wiki

Rebirth_of_the_Urban_Immortal_Cultivator_Wiki

26 ms

load.php

load.php

130 ms

load.php

load.php

344 ms

wikia.php

wikia.php

111 ms

sdk.js

sdk.js

38 ms

pathfinder.js

pathfinder.js

39 ms

loader

loader

26 ms

scout.js

scout.js

31 ms

36

36

34 ms

latest

latest

4 ms

250

250

156 ms

250

250

7 ms

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

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

13 ms

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

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

16 ms

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

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

17 ms

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

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

18 ms

Accessibility Review

rebirth-of-the-urban-immortal-cultivator.fandom.com accessibility score

85

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

Best Practices

rebirth-of-the-urban-immortal-cultivator.fandom.com best practices score

83

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

SEO Factors

rebirth-of-the-urban-immortal-cultivator.fandom.com SEO score

79

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

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 Rebirth-of-the-urban-immortal-cultivator.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 Rebirth-of-the-urban-immortal-cultivator.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

rebirth-of-the-urban-immortal-cultivator.fandom.com

Open Graph description is not detected on the main page of Rebirth Of The Urban Immortal Cultivator 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: