Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

1.9 sec in total

First Response

421 ms

Resources Loaded

869 ms

Page Rendered

564 ms

versusfacts.com screenshot

About Website

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

Visit versusfacts.com

Key Findings

We analyzed Versusfacts.com page load time and found that the first response time was 421 ms and then it took 1.4 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

versusfacts.com performance score

0

Network Requests Diagram

versusfacts.com

421 ms

sand__custom_theme_titan.css

242 ms

css

32 ms

jquery.min.js

36 ms

jquery-migrate-1.2.1.min.js

13 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Versusfacts.com, 65% (20 requests) were made to Img-cdn.likes.com and 16% (5 requests) were made to O.mlv-cdn.com. The less responsive or slowest element that took the longest time to load (421 ms) belongs to the original domain Versusfacts.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 169.7 kB (7%)

Content Size

2.3 MB

After Optimization

2.2 MB

In fact, the total size of Versusfacts.com main page is 2.3 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. 75% 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 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 45.3 kB

  • Original 57.3 kB
  • After minification 57.0 kB
  • After compression 12.0 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 45.3 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 124.2 kB

  • Original 2.2 MB
  • After minification 2.1 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. Versusfacts images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 27 B

  • Original 50.5 kB
  • After minification 50.5 kB
  • After compression 50.5 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

-49%

Potential reduce by 159 B

  • Original 323 B
  • After minification 247 B
  • After compression 164 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. Versusfacts.com needs all CSS files to be minified and compressed as it can save up to 159 B or 49% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (10%)

Requests Now

30

After Optimization

27

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

SEO Factors

versusfacts.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Versusfacts.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Versusfacts.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 Versusfacts. 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: