Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

2.9 sec in total

First Response

68 ms

Resources Loaded

2 sec

Page Rendered

897 ms

weirdlyawesome.com screenshot

About Website

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

It's going to get weird if we have anything to do with it. Which we do.

Visit weirdlyawesome.com

Key Findings

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

Performance Metrics

weirdlyawesome.com performance score

0

Network Requests Diagram

www.weirdlyawesome.com

68 ms

pre_tumblelog.js

15 ms

reset.css

17 ms

css

25 ms

css

37 ms

Our browser made a total of 171 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Weirdlyawesome.com, 20% (34 requests) were made to Assets.weirdlyawesome.com and 12% (20 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source 49.media.tumblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (31%)

Content Size

5.0 MB

After Optimization

3.5 MB

In fact, the total size of Weirdlyawesome.com main page is 5.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. 85% 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 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 179.1 kB

  • Original 200.5 kB
  • After minification 146.6 kB
  • After compression 21.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. This page needs HTML code to be minified as it can gain 53.9 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 179.1 kB or 89% of the original size.

Image Optimization

-12%

Potential reduce by 417.6 kB

  • Original 3.4 MB
  • After minification 3.0 MB

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. Obviously, Weirdlyawesome needs image optimization as it can save up to 417.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 790.6 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 438.9 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 790.6 kB or 64% of the original size.

CSS Optimization

-82%

Potential reduce by 145.7 kB

  • Original 178.1 kB
  • After minification 144.6 kB
  • After compression 32.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. Weirdlyawesome.com needs all CSS files to be minified and compressed as it can save up to 145.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (39%)

Requests Now

151

After Optimization

92

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

SEO Factors

weirdlyawesome.com SEO score

0

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 Weirdlyawesome.com 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 Weirdlyawesome.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

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