Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

talkorigins.org

TalkOrigins Archive: Exploring the Creation/Evolution Controversy

Page Load Speed

758 ms in total

First Response

186 ms

Resources Loaded

465 ms

Page Rendered

107 ms

talkorigins.org screenshot

About Website

Visit talkorigins.org now to see the best up-to-date Talk Origins content for United States and also check out these interesting facts you probably never knew about talkorigins.org

Explores creation/evolution/intelligent design, gives the evidence for evolution, and tells what's wrong with intelligent design & other forms of creationism.

Visit talkorigins.org

Key Findings

We analyzed Talkorigins.org page load time and found that the first response time was 186 ms and then it took 572 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

talkorigins.org performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

100/100

25%

SI (Speed Index)

Value0.9 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.9 s

100/100

10%

Network Requests Diagram

talkorigins.org

186 ms

menu.css

42 ms

TOtools.js

81 ms

title.jpg

191 ms

new.gif

41 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that all of those requests were addressed to Talkorigins.org and no external sources were called. The less responsive or slowest element that took the longest time to load (191 ms) belongs to the original domain Talkorigins.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 14.1 kB (17%)

Content Size

84.6 kB

After Optimization

70.5 kB

In fact, the total size of Talkorigins.org main page is 84.6 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 66.3 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 5.9 kB

  • Original 8.5 kB
  • After minification 7.1 kB
  • After compression 2.6 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 1.4 kB, which is 17% 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 5.9 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 25 B

  • Original 66.3 kB
  • After minification 66.3 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. Talk Origins images are well optimized though.

JavaScript Optimization

-88%

Potential reduce by 6.0 kB

  • Original 6.8 kB
  • After minification 2.4 kB
  • After compression 823 B

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 6.0 kB or 88% of the original size.

CSS Optimization

-73%

Potential reduce by 2.2 kB

  • Original 3.0 kB
  • After minification 1.7 kB
  • After compression 789 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. Talkorigins.org needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 73% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Talk Origins. According to our analytics all requests are already optimized.

Accessibility Review

talkorigins.org accessibility score

100

Accessibility Issues

Best Practices

talkorigins.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

talkorigins.org SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Talkorigins.org 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 Talkorigins.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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