Tools & Wizards About Us
logicallyfallacious.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

logicallyfallacious.com

Logically Fallacious

Page Load Speed

1.5 sec in total

First Response

31 ms

Resources Loaded

1.3 sec

Page Rendered

124 ms

logicallyfallacious.com screenshot

About Website

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

The Ultimate Collection of Over 300 Logical Fallacies, by Bo Bennett, PhD. Browse or search over 300 fallacies or post your fallacy-related question.

Visit logicallyfallacious.com

Key Findings

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

Performance Metrics

logicallyfallacious.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value2,230 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

Network Requests Diagram

logicallyfallacious.com

31 ms

www.logicallyfallacious.com

253 ms

css

37 ms

icon

56 ms

wwwlogicallyfallaciouscom.bootstrap.min.css

19 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 68% of them (32 requests) were addressed to the original Logicallyfallacious.com, 11% (5 requests) were made to Youtube.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (650 ms) relates to the external source Cdn.jsdelivr.net.

Page Optimization Overview & Recommendations

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

Content Size

257.1 kB

After Optimization

230.6 kB

  • HTML
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 23.8 kB

  • Original 31.9 kB
  • After minification 29.7 kB
  • After compression 8.1 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 23.8 kB or 75% of the original size.

JavaScript Optimization

-2%

Potential reduce by 2.6 kB

  • Original 165.7 kB
  • After minification 165.7 kB
  • After compression 163.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 59.4 kB
  • After minification 59.4 kB
  • After compression 59.4 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. Logicallyfallacious.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

15

After Optimization

5

  • AJAX
  • JavaScript
  • CSS

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

Network Requests Diagram

logicallyfallacious.com

logicallyfallacious.com

31 ms

www.logicallyfallacious.com

www.logicallyfallacious.com

253 ms

css

css

37 ms

icon

icon

56 ms

wwwlogicallyfallaciouscom.bootstrap.min.css

wwwlogicallyfallaciouscom.bootstrap.min.css

19 ms

font-awesome.min.css

font-awesome.min.css

20 ms

animate.min.css

animate.min.css

19 ms

ionicons.min.css

ionicons.min.css

19 ms

owl.carousel.min.css

owl.carousel.min.css

20 ms

lightbox.min.css

lightbox.min.css

25 ms

jquery-ui.min.css

jquery-ui.min.css

30 ms

plyr.css

plyr.css

48 ms

wwwlogicallyfallaciouscom.style.css

wwwlogicallyfallaciouscom.style.css

32 ms

sharethis.js

sharethis.js

35 ms

party.min.js

party.min.js

650 ms

websitelogo.png

websitelogo.png

29 ms

jquery.min.js

jquery.min.js

29 ms

jquery-migrate.min.js

jquery-migrate.min.js

27 ms

jquery-ui.min.js

jquery-ui.min.js

30 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

36 ms

plyr.js

plyr.js

68 ms

easing.min.js

easing.min.js

36 ms

hoverIntent.js

hoverIntent.js

36 ms

superfish.min.js

superfish.min.js

37 ms

mobile-nav.js

mobile-nav.js

37 ms

wow.min.js

wow.min.js

38 ms

waypoints.min.js

waypoints.min.js

43 ms

counterup.min.js

counterup.min.js

43 ms

owl.carousel.min.js

owl.carousel.min.js

44 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

45 ms

lightbox.min.js

lightbox.min.js

43 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

45 ms

main.js

main.js

49 ms

mainbookimage_20200102161405Wc002.jpg

mainbookimage_20200102161405Wc002.jpg

7 ms

websitelogo_1.png

websitelogo_1.png

6 ms

font

font

26 ms

mainbookimage_20200102161405Wc002.jpg

mainbookimage_20200102161405Wc002.jpg

22 ms

loading.html

loading.html

19 ms

6RZHRU5wizs

6RZHRU5wizs

91 ms

websitelogo_1.png

websitelogo_1.png

20 ms

www-player.css

www-player.css

9 ms

www-embed-player.js

www-embed-player.js

25 ms

base.js

base.js

47 ms

ad_status.js

ad_status.js

136 ms

UGQVitqvNAyiBGv0viNtzUaV8WFuiqpxfryNFNBa68Y.js

UGQVitqvNAyiBGv0viNtzUaV8WFuiqpxfryNFNBa68Y.js

89 ms

embed.js

embed.js

29 ms

id

id

22 ms

Accessibility Review

logicallyfallacious.com accessibility score

55

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

logicallyfallacious.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

logicallyfallacious.com SEO score

80

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Logicallyfallacious.com 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 Logicallyfallacious.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

logicallyfallacious.com

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