Tools & Wizards About Us
wtfqrcodes.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wtfqrcodes.com

WTF QR CODES

Page Load Speed

1.2 sec in total

First Response

35 ms

Resources Loaded

571 ms

Page Rendered

639 ms

wtfqrcodes.com screenshot

About Website

Visit wtfqrcodes.com now to see the best up-to-date WTF QR CODES content for United States and also check out these interesting facts you probably never knew about wtfqrcodes.com

Celebrating the ridiculousness that is QR codes. Curated by @brad_frost and @cvilly.

Visit wtfqrcodes.com

Key Findings

We analyzed Wtfqrcodes.com page load time and found that the first response time was 35 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

wtfqrcodes.com performance score

0

Network Requests Diagram

wtfqrcodes.com

35 ms

pre_tumblelog.js

6 ms

tumblelog_post_message_queue.js

12 ms

stylesheet.css

11 ms

tweets.js

243 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Wtfqrcodes.com, 22% (8 requests) were made to Assets.tumblr.com and 14% (5 requests) were made to 36.media.tumblr.com. The less responsive or slowest element that took the longest time to load (403 ms) relates to the external source 36.media.tumblr.com.

Page Optimization Overview & Recommendations

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

Content Size

1.5 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 49.3 kB

  • Original 59.5 kB
  • After minification 47.3 kB
  • After compression 10.2 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 12.3 kB, which is 21% 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 49.3 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 16.3 kB

  • Original 856.9 kB
  • After minification 840.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. WTF QR CODES images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 348.3 kB

  • Original 537.6 kB
  • After minification 537.6 kB
  • After compression 189.3 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 348.3 kB or 65% of the original size.

CSS Optimization

-59%

Potential reduce by 384 B

  • Original 655 B
  • After minification 655 B
  • After compression 271 B

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. Wtfqrcodes.com needs all CSS files to be minified and compressed as it can save up to 384 B or 59% of the original size.

Requests Breakdown

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

Requests Now

35

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WTF QR CODES. 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

wtfqrcodes.com

wtfqrcodes.com

35 ms

pre_tumblelog.js

pre_tumblelog.js

6 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

12 ms

stylesheet.css

stylesheet.css

11 ms

tweets.js

tweets.js

243 ms

index.js

index.js

23 ms

qr2.png

qr2.png

14 ms

tumblr_nfbm9zqHll1rp7p0go1_500.jpg

tumblr_nfbm9zqHll1rp7p0go1_500.jpg

35 ms

tumblr_nf5owg7EMe1rp7p0go1_500.jpg

tumblr_nf5owg7EMe1rp7p0go1_500.jpg

11 ms

tumblr_mvltf6EL8H1rp7p0go1_500.jpg

tumblr_mvltf6EL8H1rp7p0go1_500.jpg

137 ms

avatar_8d6acb72082a_64.png

avatar_8d6acb72082a_64.png

7 ms

ga.js

ga.js

7 ms

widgets.js

widgets.js

79 ms

tumblr_mu4zzcGmwt1rp7p0go1_500.jpg

tumblr_mu4zzcGmwt1rp7p0go1_500.jpg

215 ms

tumblr_mutmzoC0ji1rp7p0go1_500.jpg

tumblr_mutmzoC0ji1rp7p0go1_500.jpg

403 ms

tumblr_mvuo8d8OL81rp7p0go1_500.jpg

tumblr_mvuo8d8OL81rp7p0go1_500.jpg

30 ms

tumblr_mvspg7oK2l1rp7p0go1_500.jpg

tumblr_mvspg7oK2l1rp7p0go1_500.jpg

31 ms

tumblr_msivmgk0yw1rp7p0go1_500.jpg

tumblr_msivmgk0yw1rp7p0go1_500.jpg

32 ms

tumblr_mvde6r0M411rp7p0go1_500.jpg

tumblr_mvde6r0M411rp7p0go1_500.jpg

28 ms

tumblr_mvsq1k5mmy1rp7p0go1_500.jpg

tumblr_mvsq1k5mmy1rp7p0go1_500.jpg

28 ms

qr2.png

qr2.png

28 ms

__utm.gif

__utm.gif

10 ms

impixu

impixu

114 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

166 ms

impixu

impixu

65 ms

analytics.html

analytics.html

68 ms

login_check.html

login_check.html

5 ms

avatar_8d6acb72082a_40.png

avatar_8d6acb72082a_40.png

87 ms

iframe_logo.png

iframe_logo.png

20 ms

rapid-3.36.js

rapid-3.36.js

34 ms

rapidworker-1.2.js

rapidworker-1.2.js

33 ms

ga.js

ga.js

53 ms

analytics.js

analytics.js

35 ms

cs.js

cs.js

64 ms

__utm.gif

__utm.gif

10 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

43 ms

cedexis.radar.js

cedexis.radar.js

3 ms

SEO Factors

wtfqrcodes.com SEO score

0

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

wtfqrcodes.com

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