Tools & Wizards About Us
viz.wtf screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

viz.wtf

WTF Visualizations

Page Load Speed

1.9 sec in total

First Response

313 ms

Resources Loaded

869 ms

Page Rendered

736 ms

viz.wtf screenshot

About Website

Welcome to viz.wtf homepage info - get ready to check Viz best content for United States right away, or after learning these important things about viz.wtf

Visualizations that make no sense. For a discussion of what is wrong with a particular visualization, tweet at us @WTFViz. Submit a WTFViz you found.

Visit viz.wtf

Key Findings

We analyzed Viz.wtf page load time and found that the first response time was 313 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

viz.wtf performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.8 s

44/100

10%

Network Requests Diagram

viz.wtf

313 ms

pre_tumblelog.js

51 ms

index.build.css

50 ms

main-min.css

54 ms

bilmur.min.js

80 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Viz.wtf, 32% (13 requests) were made to Assets.tumblr.com and 27% (11 requests) were made to 64.media.tumblr.com. The less responsive or slowest element that took the longest time to load (313 ms) belongs to the original domain Viz.wtf.

Page Optimization Overview & Recommendations

Page size can be reduced by 142.9 kB (28%)

Content Size

504.4 kB

After Optimization

361.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Viz.wtf main page is 504.4 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. 60% of websites need less resources to load. Images take 262.7 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 142.7 kB

  • Original 164.2 kB
  • After minification 120.3 kB
  • After compression 21.5 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. This page needs HTML code to be minified as it can gain 43.8 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 142.7 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 84 B

  • Original 262.7 kB
  • After minification 262.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. Viz images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 94 B

  • Original 65.2 kB
  • After minification 65.2 kB
  • After compression 65.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 46 B

  • Original 12.4 kB
  • After minification 12.4 kB
  • After compression 12.3 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. Viz.wtf has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (31%)

Requests Now

36

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

viz.wtf

viz.wtf

313 ms

pre_tumblelog.js

pre_tumblelog.js

51 ms

index.build.css

index.build.css

50 ms

main-min.css

main-min.css

54 ms

bilmur.min.js

bilmur.min.js

80 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

53 ms

jquery.min.js

jquery.min.js

104 ms

main-min.js

main-min.js

81 ms

index.build.js

index.build.js

91 ms

avatar_f5ee00afedf6_128.pnj

avatar_f5ee00afedf6_128.pnj

252 ms

like_iframe.html

like_iframe.html

23 ms

16fbaf109180423cab2b9410f50027fd7a20fd2b.jpg

16fbaf109180423cab2b9410f50027fd7a20fd2b.jpg

260 ms

tumblr_r4qzdiAeIt1sgh0voo1_1280.jpg

tumblr_r4qzdiAeIt1sgh0voo1_1280.jpg

243 ms

31f900605f048c6c44887a3ead66b5b7ddc2e0df.png

31f900605f048c6c44887a3ead66b5b7ddc2e0df.png

258 ms

c4ef54bbf4df92f7ab215eaa92bf4fa09b439ae5.jpg

c4ef54bbf4df92f7ab215eaa92bf4fa09b439ae5.jpg

242 ms

029c38699bf84c503569097fde0d067cc421fed7.jpg

029c38699bf84c503569097fde0d067cc421fed7.jpg

242 ms

tumblr_r2bz20IDxh1sgh0voo1_640.png

tumblr_r2bz20IDxh1sgh0voo1_640.png

267 ms

tumblr_r0kektEJbr1sgh0voo1_1280.png

tumblr_r0kektEJbr1sgh0voo1_1280.png

260 ms

ae291ea59201c16a9130b5f719400c75318cd5ad.jpg

ae291ea59201c16a9130b5f719400c75318cd5ad.jpg

288 ms

tumblr_r0ixbf4h4E1sgh0voo1_1280.jpg

tumblr_r0ixbf4h4E1sgh0voo1_1280.jpg

288 ms

tumblr_qz6iessFp81sgh0voo1_1280.png

tumblr_qz6iessFp81sgh0voo1_1280.png

293 ms

tumblr_static_interferogram.jpg

tumblr_static_interferogram.jpg

295 ms

analytics.js

analytics.js

230 ms

impixu

impixu

250 ms

g.gif

g.gif

162 ms

impixu

impixu

123 ms

analytics.html

analytics.html

75 ms

AAAAEAAAAAAADqwABAAAAAAAAAAAAAAAAAAAACgAAAAAAAAAAAAAAAAIAAAAEAABVBAAA1QQAAIAEAAEEBAAA1QQAAQAAAAAAAAoAFAAeAFgAggC8ANYBIAE8AAAAAQAAAAoAMwADAAAAAAACAAAAAAAAAAAAAAAAAAAAAAAAAA4ArgABAAAAAAABAAwAAAABAAAAAAACAAcAjQABAAAAAAADAAwARQABAAAAAAAEAAwAogABAAAAAAAFAAsAJAABAAAAAAAGAAwAaQABAAAAAAAKABoAxgADAAEECQABABgADAADAAEECQACAA4AlAADAAEECQADABgAUQADAAEECQAEABgArgADAAEECQAFABYALwADAAEECQAGABgAdQADAAEECQAKADQA4G9wdGljYS1pY29ucwBvAHAAdABpAGMAYQAtAGkAYwBvAG4Ac1ZlcnNpb24gMS4wAFYAZQByAHMAaQBvAG4AIAAxAC4AMG9wdGljYS1pY29ucwBvAHAAdABpAGMAYQAtAGkAYwBvAG4Ac29wdGljYS1pY29ucwBvAHAAdABpAGMAYQAtAGkAYwBvAG4Ac1JlZ3VsYXIAUgBlAGcAdQBsAGEAcm9wdGljYS1pY29ucwBvAHAAdABpAGMAYQAtAGkAYwBvAG4Ac0ZvbnQgZ2VuZXJhdGVkIGJ5IEljb01vb24uAEYAbwBuAHQAIABnAGUAbgBlAHIAYQB0AGUAZAAgAGIAeQAgAEkAYwBvAE0AbwBvAG4ALgAAAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=

AAAAEAAAAAAADqwABAAAAAAAAAAAAAAAAAAAACgAAAAAAAAAAAAAAAAIAAAAEAABVBAAA1QQAAIAEAAEEBAAA1QQAAQAAAAAAAAoAFAAeAFgAggC8ANYBIAE8AAAAAQAAAAoAMwADAAAAAAACAAAAAAAAAAAAAAAAAAAAAAAAAA4ArgABAAAAAAABAAwAAAABAAAAAAACAAcAjQABAAAAAAADAAwARQABAAAAAAAEAAwAogABAAAAAAAFAAsAJAABAAAAAAAGAAwAaQABAAAAAAAKABoAxgADAAEECQABABgADAADAAEECQACAA4AlAADAAEECQADABgAUQADAAEECQAEABgArgADAAEECQAFABYALwADAAEECQAGABgAdQADAAEECQAKADQA4G9wdGljYS1pY29ucwBvAHAAdABpAGMAYQAtAGkAYwBvAG4Ac1ZlcnNpb24gMS4wAFYAZQByAHMAaQBvAG4AIAAxAC4AMG9wdGljYS1pY29ucwBvAHAAdABpAGMAYQAtAGkAYwBvAG4Ac29wdGljYS1pY29ucwBvAHAAdABpAGMAYQAtAGkAYwBvAG4Ac1JlZ3VsYXIAUgBlAGcAdQBsAGEAcm9wdGljYS1pY29ucwBvAHAAdABpAGMAYQAtAGkAYwBvAG4Ac0ZvbnQgZ2VuZXJhdGVkIGJ5IEljb01vb24uAEYAbwBuAHQAIABnAGUAbgBlAHIAYQB0AGUAZAAgAGIAeQAgAEkAYwBvAE0AbwBvAG4ALgAAAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=

7 ms

Gibson-Regular-webfont.woff

Gibson-Regular-webfont.woff

75 ms

Gibson-SemiBold-webfont.woff

Gibson-SemiBold-webfont.woff

77 ms

login_check.html

login_check.html

31 ms

g.gif

g.gif

54 ms

consent

consent

70 ms

collect

collect

17 ms

js

js

64 ms

cs.js

cs.js

5 ms

header.build.js

header.build.js

2 ms

exceptions.js

exceptions.js

3 ms

index.build.js

index.build.js

8 ms

cdn.json

cdn.json

26 ms

g.gif

g.gif

5 ms

Accessibility Review

viz.wtf accessibility score

61

Accessibility Issues

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.

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

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

viz.wtf 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

SEO Factors

viz.wtf SEO score

88

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Viz.wtf can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Viz.wtf 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

viz.wtf

Open Graph data is detected on the main page of Viz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: