Tools & Wizards About Us
debatelive.org screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

debatelive.org

Page Load Speed

2.3 sec in total

First Response

233 ms

Resources Loaded

1.7 sec

Page Rendered

359 ms

debatelive.org screenshot

About Website

Click here to check amazing Debatelive content. Otherwise, check out these important facts you probably never knew about debatelive.org

February 4, 2016, is the two-year anniversary of Ken Ham’s debate with Bill Nye

Visit debatelive.org

Key Findings

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

Performance Metrics

debatelive.org performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.9 s

100/100

25%

SI (Speed Index)

Value3.7 s

86/100

10%

TBT (Total Blocking Time)

Value2,840 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.068

96/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

233 ms

jtip.css

98 ms

jquery-ui.aig.min.css

164 ms

default.css

123 ms

css

160 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Debatelive.org, 10% (7 requests) were made to Fonts.googleapis.com and 8% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (872 ms) relates to the external source Api.reftagger.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (68%)

Content Size

1.9 MB

After Optimization

609.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Debatelive.org main page is 1.9 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. 70% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 114.2 kB

  • Original 151.9 kB
  • After minification 150.3 kB
  • After compression 37.7 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 114.2 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 1.5 kB

  • Original 230.2 kB
  • After minification 228.7 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. Debatelive images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 751.2 kB

  • Original 1.0 MB
  • After minification 806.6 kB
  • After compression 249.1 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 751.2 kB or 75% of the original size.

CSS Optimization

-82%

Potential reduce by 422.6 kB

  • Original 516.9 kB
  • After minification 515.3 kB
  • After compression 94.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. Debatelive.org needs all CSS files to be minified and compressed as it can save up to 422.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (56%)

Requests Now

63

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

233 ms

jtip.css

jtip.css

98 ms

jquery-ui.aig.min.css

jquery-ui.aig.min.css

164 ms

default.css

default.css

123 ms

css

css

160 ms

overlay.css

overlay.css

118 ms

dialog.css

dialog.css

164 ms

plusone.js

plusone.js

145 ms

all.js

all.js

296 ms

jquery.min.js

jquery.min.js

133 ms

jquery-ui.min.js

jquery-ui.min.js

176 ms

underscore-min.js

underscore-min.js

67 ms

json2.min.js

json2.min.js

108 ms

backbone-min.js

backbone-min.js

115 ms

jquery.ui.touch-punch.min.js

jquery.ui.touch-punch.min.js

116 ms

gigya.js

gigya.js

212 ms

ace.js

ace.js

213 ms

default.min.js

default.min.js

116 ms

css

css

59 ms

css

css

75 ms

css

css

78 ms

css

css

76 ms

css

css

77 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

12 ms

handshake.jpg

handshake.jpg

70 ms

bill-nye-ken-ham-debate.jpg

bill-nye-ken-ham-debate.jpg

12 ms

10-2-267.png

10-2-267.png

10 ms

90-2-058.png

90-2-058.png

39 ms

30-9-460.png

30-9-460.png

47 ms

30-9-468.png

30-9-468.png

38 ms

40-1-452.png

40-1-452.png

39 ms

10-4-402.png

10-4-402.png

41 ms

90-2-163.png

90-2-163.png

43 ms

90-2-164.png

90-2-164.png

41 ms

98-0-017.png

98-0-017.png

41 ms

90-7-550.png

90-7-550.png

44 ms

AiG11Logo.svg

AiG11Logo.svg

44 ms

banner-debate-answers.jpg

banner-debate-answers.jpg

60 ms

98-0-017.png

98-0-017.png

55 ms

472 ms

z6kgvhG3AkI

z6kgvhG3AkI

449 ms

xd_arbiter.php

xd_arbiter.php

770 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

423 ms

nj47mAZe0mYUIySgfn0wpQ.ttf

nj47mAZe0mYUIySgfn0wpQ.ttf

440 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

551 ms

aig.woff

aig.woff

388 ms

2HG_tEPiQ4Z6795cGfdivKCWcynf_cDxXwCLxiixG1c.ttf

2HG_tEPiQ4Z6795cGfdivKCWcynf_cDxXwCLxiixG1c.ttf

551 ms

collector.min.js

collector.min.js

512 ms

analytics.js

analytics.js

363 ms

webfont.js

webfont.js

224 ms

RefTagger.js

RefTagger.js

872 ms

loader0.js

loader0.js

554 ms

222 ms

widgets.js

widgets.js

298 ms

216 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

244 ms

www-embed-player.js

www-embed-player.js

267 ms

sso.htm

sso.htm

83 ms

css

css

172 ms

xd_arbiter.php

xd_arbiter.php

229 ms

ec.js

ec.js

132 ms

collect

collect

158 ms

collect

collect

96 ms

Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js

Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js

74 ms

ad_status.js

ad_status.js

73 ms

collect

collect

33 ms

collect

collect

33 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

15 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

19 ms

2776-763-10-5369.js

2776-763-10-5369.js

30 ms

c

c

224 ms

Accessibility Review

debatelive.org accessibility score

63

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

debatelive.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

debatelive.org SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

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 Debatelive.org 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 Debatelive.org 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

debatelive.org

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