Tools & Wizards About Us
phasefatale.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

phasefatale.com

Tumblr

Page Load Speed

7.6 sec in total

First Response

119 ms

Resources Loaded

4.6 sec

Page Rendered

2.9 sec

phasefatale.com screenshot

About Website

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

Tumblr. Pure effervescent enrichment. Old internet energy. Home of the Reblogs. All the art you never knew you needed. All the fandoms you could wish for. Enough memes to knock out a moderately-sized ...

Visit phasefatale.com

Key Findings

We analyzed Phasefatale.com page load time and found that the first response time was 119 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

phasefatale.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

76/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

94/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value13,930 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value27.0 s

0/100

10%

Network Requests Diagram

phasefatale.com

119 ms

pre_tumblelog.js

64 ms

index.build.css

69 ms

tumblrautopagernopage.js

79 ms

tumblelog_post_message_queue.js

70 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Phasefatale.com, 22% (13 requests) were made to I1.sndcdn.com and 19% (11 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source 64.media.tumblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 451.2 kB (44%)

Content Size

1.0 MB

After Optimization

572.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phasefatale.com main page is 1.0 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 434.7 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 29.8 kB

  • Original 39.8 kB
  • After minification 39.3 kB
  • After compression 9.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 29.8 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 434.7 kB
  • After minification 434.7 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. Phasefatale images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 138.3 kB

  • Original 214.7 kB
  • After minification 213.7 kB
  • After compression 76.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 138.3 kB or 64% of the original size.

CSS Optimization

-85%

Potential reduce by 283.0 kB

  • Original 334.6 kB
  • After minification 334.2 kB
  • After compression 51.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. Phasefatale.com needs all CSS files to be minified and compressed as it can save up to 283.0 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

53

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phasefatale.com

phasefatale.com

119 ms

pre_tumblelog.js

pre_tumblelog.js

64 ms

index.build.css

index.build.css

69 ms

tumblrautopagernopage.js

tumblrautopagernopage.js

79 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

70 ms

stylesheet.css

stylesheet.css

70 ms

index.build.js

index.build.js

78 ms

408 ms

400 ms

742 ms

741 ms

740 ms

tcRg5KfYJBM

tcRg5KfYJBM

298 ms

dbad6cf85e66f0cd47973db436c0f33cf12ddad3.png

dbad6cf85e66f0cd47973db436c0f33cf12ddad3.png

2487 ms

737 ms

736 ms

impixu

impixu

278 ms

g.gif

g.gif

250 ms

df4127049418fc986cac23e7a6ea99738aa19d0b.jpg

df4127049418fc986cac23e7a6ea99738aa19d0b.jpg

633 ms

impixu

impixu

169 ms

analytics.html

analytics.html

68 ms

login_check.html

login_check.html

51 ms

cs.js

cs.js

195 ms

consent

consent

211 ms

www-player.css

www-player.css

35 ms

www-embed-player.js

www-embed-player.js

90 ms

base.js

base.js

118 ms

fetch-polyfill.js

fetch-polyfill.js

88 ms

widget-507e991-c375d55c.js

widget-507e991-c375d55c.js

567 ms

visual-single-sound-d890ecf-c375d55c.js

visual-single-sound-d890ecf-c375d55c.js

525 ms

header.build.js

header.build.js

347 ms

exceptions.js

exceptions.js

359 ms

index.build.js

index.build.js

429 ms

visual-multi-sounds-e46091c-c375d55c.js

visual-multi-sounds-e46091c-c375d55c.js

521 ms

ad_status.js

ad_status.js

395 ms

IrvWYL9cMQDdQTlUfy4EmSWPiDUBB4ig0nZVQdwez_Q.js

IrvWYL9cMQDdQTlUfy4EmSWPiDUBB4ig0nZVQdwez_Q.js

1442 ms

embed.js

embed.js

195 ms

cdn.json

cdn.json

162 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

1208 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

1221 ms

g.gif

g.gif

69 ms

id

id

1523 ms

logo-200x120-a1591e.png

logo-200x120-a1591e.png

481 ms

artworks-6TlcgJcIomJQ3abV-7YOcyQ-t500x500.jpg

artworks-6TlcgJcIomJQ3abV-7YOcyQ-t500x500.jpg

365 ms

artworks-mwG0N5iL2o6veYBM-ETPeaA-t500x500.png

artworks-mwG0N5iL2o6veYBM-ETPeaA-t500x500.png

165 ms

artworks-000667352446-bm89x7-t500x500.jpg

artworks-000667352446-bm89x7-t500x500.jpg

170 ms

artworks-000679264834-rkf5h6-t500x500.jpg

artworks-000679264834-rkf5h6-t500x500.jpg

308 ms

artworks-OzouKBKEPcAOZsJB-EyfnbA-t500x500.jpg

artworks-OzouKBKEPcAOZsJB-EyfnbA-t500x500.jpg

303 ms

1148497756

1148497756

852 ms

artworks-0amNJtcxdZhbEQjw-ij83uw-tiny.jpg

artworks-0amNJtcxdZhbEQjw-ij83uw-tiny.jpg

304 ms

artworks-0amNJtcxdZhbEQjw-ij83uw-t500x500.jpg

artworks-0amNJtcxdZhbEQjw-ij83uw-t500x500.jpg

309 ms

artworks-Paff0oN7Sd5nTX7o-95cMqg-t500x500.jpg

artworks-Paff0oN7Sd5nTX7o-95cMqg-t500x500.jpg

70 ms

QD+AP8BAAEBAQIBAwEEAQUBBgEHAQgBCQEKAQsBDAENAQ4BDwEQAREBEgEeARMBFAEVAAEAIQAWABcAGgAbABwAHQAfACMAKAApACoAKwAsAC0ALgAvADAAMQA0ADUANgCZAJoAmwCcAKwAswC0ALwAzQDRANIA2wABAAAAAQAIAAIASAAhABoAGwAcAB0AHwAjACgAKQAqACsALAAtAC4ALwAwADEANAA1ADYAmQCaAJsAnACsALMAtAC8ANEA0gDbABYAFwDNAAIAAgD4ARUAAAEcAR4AHgAA

QD+AP8BAAEBAQIBAwEEAQUBBgEHAQgBCQEKAQsBDAENAQ4BDwEQAREBEgEeARMBFAEVAAEAIQAWABcAGgAbABwAHQAfACMAKAApACoAKwAsAC0ALgAvADAAMQA0ADUANgCZAJoAmwCcAKwAswC0ALwAzQDRANIA2wABAAAAAQAIAAIASAAhABoAGwAcAB0AHwAjACgAKQAqACsALAAtAC4ALwAwADEANAA1ADYAmQCaAJsAnACsALMAtAC8ANEA0gDbABYAFwDNAAIAAgD4ARUAAAEcAR4AHgAA

62 ms

artworks-6TlcgJcIomJQ3abV-7YOcyQ-t500x500.jpg

artworks-6TlcgJcIomJQ3abV-7YOcyQ-t500x500.jpg

48 ms

artworks-mwG0N5iL2o6veYBM-ETPeaA-t500x500.png

artworks-mwG0N5iL2o6veYBM-ETPeaA-t500x500.png

175 ms

artworks-000667352446-bm89x7-t500x500.jpg

artworks-000667352446-bm89x7-t500x500.jpg

172 ms

artworks-000679264834-rkf5h6-t500x500.jpg

artworks-000679264834-rkf5h6-t500x500.jpg

168 ms

artworks-OzouKBKEPcAOZsJB-EyfnbA-t500x500.jpg

artworks-OzouKBKEPcAOZsJB-EyfnbA-t500x500.jpg

222 ms

Accessibility Review

phasefatale.com accessibility score

93

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

<frame> or <iframe> elements do not have a title

Best Practices

phasefatale.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

phasefatale.com SEO score

64

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

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

phasefatale.com

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