Tools & Wizards About Us
debunker.com screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

debunker.com

The Debunker's Domain, by Robert Sheaffer. Skeptical resources on UFOs, the "paranormal," feminist "scholarship"

Page Load Speed

2.5 sec in total

First Response

172 ms

Resources Loaded

1.9 sec

Page Rendered

443 ms

debunker.com screenshot

About Website

Click here to check amazing Debunker content for United States. Otherwise, check out these important facts you probably never knew about debunker.com

The Debunker's Domain by Robert Sheaffer. Skeptical resources on many subjects, including UFOs, paranormal claims, so-called feminist 'scholarship'

Visit debunker.com

Key Findings

We analyzed Debunker.com page load time and found that the first response time was 172 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

debunker.com performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

96/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value650 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

debunker.com

172 ms

show_ads.js

40 ms

counter.js

39 ms

stone3.jpg

294 ms

flagwave.gif

292 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 27% of them (10 requests) were addressed to the original Debunker.com, 16% (6 requests) were made to Pagead2.googlesyndication.com and 16% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (444 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 17.2 kB (10%)

Content Size

173.0 kB

After Optimization

155.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Debunker.com main page is 173.0 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. Javascripts take 106.8 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 14.3 kB

  • Original 21.5 kB
  • After minification 21.2 kB
  • After compression 7.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. 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 14.3 kB or 67% of the original size.

Image Optimization

-5%

Potential reduce by 2.4 kB

  • Original 44.7 kB
  • After minification 42.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. Debunker images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 400 B

  • Original 106.8 kB
  • After minification 106.8 kB
  • After compression 106.4 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.

Requests Breakdown

Number of requests can be reduced by 13 (38%)

Requests Now

34

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

debunker.com

debunker.com

172 ms

show_ads.js

show_ads.js

40 ms

counter.js

counter.js

39 ms

stone3.jpg

stone3.jpg

294 ms

flagwave.gif

flagwave.gif

292 ms

Cover2.jpg

Cover2.jpg

296 ms

alum.png

alum.png

293 ms

bomb.gif

bomb.gif

292 ms

amazon_logo.png

amazon_logo.png

293 ms

skeptic-ring.png

skeptic-ring.png

293 ms

evolve1.gif

evolve1.gif

296 ms

NoAliens.gif

NoAliens.gif

296 ms

show_ads_impl.js

show_ads_impl.js

237 ms

x-click-butcc-donate.gif

x-click-butcc-donate.gif

255 ms

t.php

t.php

351 ms

adsbygoogle.js

adsbygoogle.js

101 ms

cookie.js

cookie.js

148 ms

integrator.js

integrator.js

173 ms

ads

ads

444 ms

sodar

sodar

88 ms

zrt_lookup.html

zrt_lookup.html

44 ms

sodar2.js

sodar2.js

179 ms

runner.html

runner.html

35 ms

aframe

aframe

57 ms

lNPcL4AZZQ8z9NJpy71wtXJu_aTy2V1-RO76Pd5QcdQ.js

lNPcL4AZZQ8z9NJpy71wtXJu_aTy2V1-RO76Pd5QcdQ.js

24 ms

load_preloaded_resource.js

load_preloaded_resource.js

30 ms

abg_lite.js

abg_lite.js

27 ms

window_focus.js

window_focus.js

69 ms

qs_click_protection.js

qs_click_protection.js

69 ms

rx_lidar.js

rx_lidar.js

146 ms

042791247ab671b2831aa311d6583330.js

042791247ab671b2831aa311d6583330.js

131 ms

icon.png

icon.png

66 ms

s

s

31 ms

css

css

49 ms

activeview

activeview

38 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

167 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

168 ms

Accessibility Review

debunker.com accessibility score

58

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

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

debunker.com best practices score

67

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

General

Impact

Issue

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

debunker.com SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Debunker.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 Debunker.com main page’s claimed encoding is windows-1252. 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

debunker.com

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