Tools & Wizards About Us
whynogod.wordpress.com screenshot

Report Summary

  • 82

    Performance

    Renders faster than
    87% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

whynogod.wordpress.com

Why there is no god | Responses to common theist arguments

Page Load Speed

3.9 sec in total

First Response

8 ms

Resources Loaded

783 ms

Page Rendered

3.1 sec

whynogod.wordpress.com screenshot

About Website

Visit whynogod.wordpress.com now to see the best up-to-date Whyno God Wordpress content for United States and also check out these interesting facts you probably never knew about whynogod.wordpress.com

This page presents concise rebuttals to the most common arguments and claims made by theists. It also includes relevant links to additional resources. A small number of points deal specifically with C...

Visit whynogod.wordpress.com

Key Findings

We analyzed Whynogod.wordpress.com page load time and found that the first response time was 8 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

whynogod.wordpress.com performance score

82

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

whynogod.wordpress.com

8 ms

whynogod.wordpress.com

27 ms

style.css

90 ms

jetpack-likes.css

90 ms

88 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 33% of them (16 requests) were addressed to the original Whynogod.wordpress.com, 16% (8 requests) were made to S0.wp.com and 12% (6 requests) were made to S2.wp.com. The less responsive or slowest element that took the longest time to load (538 ms) belongs to the original domain Whynogod.wordpress.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 188.5 kB (14%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whynogod.wordpress.com main page is 1.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. 65% of websites need less resources to load. Images take 969.4 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 187.2 kB

  • Original 253.6 kB
  • After minification 248.1 kB
  • After compression 66.3 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 187.2 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 232 B

  • Original 969.4 kB
  • After minification 969.2 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. Whyno God Wordpress images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 682 B

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

-1%

Potential reduce by 317 B

  • Original 52.1 kB
  • After minification 52.1 kB
  • After compression 51.7 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. Whynogod.wordpress.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (36%)

Requests Now

44

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whynogod.wordpress.com

whynogod.wordpress.com

8 ms

whynogod.wordpress.com

whynogod.wordpress.com

27 ms

style.css

style.css

90 ms

jetpack-likes.css

jetpack-likes.css

90 ms

88 ms

89 ms

88 ms

85 ms

verbum-comments.css

verbum-comments.css

102 ms

block-editor.css

block-editor.css

108 ms

103 ms

98 ms

105 ms

100 ms

99 ms

w.js

w.js

100 ms

search.png

search.png

53 ms

btn_donate_lg.gif

btn_donate_lg.gif

219 ms

100507-prayer-vs-work.png

100507-prayer-vs-work.png

62 ms

master.html

master.html

11 ms

g.gif

g.gif

40 ms

sogk1.jpg

sogk1.jpg

144 ms

n579307211_608281_6645.jpg

n579307211_608281_6645.jpg

145 ms

d4hbs.png

d4hbs.png

538 ms

9th7q.jpg

9th7q.jpg

187 ms

spirals2.jpg

spirals2.jpg

186 ms

creationists_fear_reality.jpg

creationists_fear_reality.jpg

144 ms

nosticiest.png

nosticiest.png

234 ms

vs1od.jpg

vs1od.jpg

235 ms

capture.jpg

capture.jpg

241 ms

1248811308523.jpg

1248811308523.jpg

303 ms

priests-salute.jpg

priests-salute.jpg

273 ms

2007-01-15-science-vs-faith.png

2007-01-15-science-vs-faith.png

413 ms

d5wah.jpg

d5wah.jpg

329 ms

comment-arrow.png

comment-arrow.png

19 ms

wpcom-gray-white.png

wpcom-gray-white.png

19 ms

g.gif

g.gif

36 ms

g.gif

g.gif

37 ms

8xL1A.jpg

8xL1A.jpg

33 ms

unholy_trinity3.jpg

unholy_trinity3.jpg

220 ms

rlt-proxy.js

rlt-proxy.js

28 ms

27 ms

QhG4I.jpg

QhG4I.jpg

111 ms

8xL1A.jpg

8xL1A.jpg

27 ms

x-click-but21.gif

x-click-but21.gif

48 ms

Noticons.svg

Noticons.svg

9 ms

BaABdRAi2AAAA

BaABdRAi2AAAA

1 ms

actionbar.css

actionbar.css

2 ms

actionbar.js

actionbar.js

15 ms

Accessibility Review

whynogod.wordpress.com accessibility score

94

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

whynogod.wordpress.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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

whynogod.wordpress.com SEO score

91

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

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 Whynogod.wordpress.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 Whynogod.wordpress.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

whynogod.wordpress.com

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