Tools & Wizards About Us
cogmessenger.org screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    79% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

cogmessenger.org

COGMessenger - Fulfill Your DestinyCOGMessenger | Fulfill Your Destiny

Page Load Speed

4.9 sec in total

First Response

156 ms

Resources Loaded

3.8 sec

Page Rendered

971 ms

cogmessenger.org screenshot

About Website

Visit cogmessenger.org now to see the best up-to-date COGMessenger content and also check out these interesting facts you probably never knew about cogmessenger.org

Messenger Church of God (cogmessenger) home page. Insights into God's plan for mankind and how you can fulfill your God given destiny!

Visit cogmessenger.org

Key Findings

We analyzed Cogmessenger.org page load time and found that the first response time was 156 ms and then it took 4.8 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

cogmessenger.org performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

24/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value140 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

Network Requests Diagram

cogmessenger.org

156 ms

167 ms

style.css

81 ms

sfm_style.css

284 ms

sfm_widgetStyle.css

364 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 70% of them (45 requests) were addressed to the original Cogmessenger.org, 8% (5 requests) were made to Api.pinterest.com and 8% (5 requests) were made to Pixel.wp.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source I0.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 29.4 kB (19%)

Content Size

157.6 kB

After Optimization

128.2 kB

  • Images
  • JavaScript
  • CSS

In fact, the total size of Cogmessenger.org main page is 157.6 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. 45% of websites need less resources to load. CSS take 96.6 kB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Image Optimization

-3%

Potential reduce by 780 B

  • Original 27.8 kB
  • After minification 27.0 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. COGMessenger images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 4.5 kB

  • Original 33.3 kB
  • After minification 33.3 kB
  • After compression 28.7 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 4.5 kB or 14% of the original size.

CSS Optimization

-25%

Potential reduce by 24.0 kB

  • Original 96.6 kB
  • After minification 96.6 kB
  • After compression 72.5 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. Cogmessenger.org needs all CSS files to be minified and compressed as it can save up to 24.0 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (72%)

Requests Now

60

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cogmessenger.org

cogmessenger.org

156 ms

167 ms

style.css

style.css

81 ms

sfm_style.css

sfm_style.css

284 ms

sfm_widgetStyle.css

sfm_widgetStyle.css

364 ms

prettyPhoto.css

prettyPhoto.css

366 ms

wp-video-lightbox.css

wp-video-lightbox.css

364 ms

style.min.css

style.min.css

441 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

703 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

363 ms

sfsi-style.css

sfsi-style.css

572 ms

trp-floater-language-switcher.css

trp-floater-language-switcher.css

426 ms

trp-language-switcher.css

trp-language-switcher.css

436 ms

blocks.css

blocks.css

435 ms

social-logos.min.css

social-logos.min.css

497 ms

jetpack.css

jetpack.css

581 ms

jquery.min.js

jquery.min.js

652 ms

jquery-migrate.min.js

jquery-migrate.min.js

506 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

578 ms

video-lightbox.js

video-lightbox.js

600 ms

jquery.slick.contact.1.3.2.js

jquery.slick.contact.1.3.2.js

640 ms

trp-language-cookie.js

trp-language-cookie.js

650 ms

skin.php

skin.php

662 ms

form.css

form.css

650 ms

counter.js

counter.js

54 ms

photon.min.js

photon.min.js

985 ms

core.min.js

core.min.js

1002 ms

modernizr.custom.min.js

modernizr.custom.min.js

1000 ms

custom.js

custom.js

1001 ms

sharing.min.js

sharing.min.js

1003 ms

e-202240.js

e-202240.js

40 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

765 ms

icon_Follow_en_US.png

icon_Follow_en_US.png

565 ms

PIA16884_hires_cropped_1_w_text_7.jpg

PIA16884_hires_cropped_1_w_text_7.jpg

806 ms

search.png

search.png

296 ms

en_US.svg

en_US.svg

278 ms

en_US_Tweet.svg

en_US_Tweet.svg

285 ms

gab_image.png

gab_image.png

285 ms

rss.png

rss.png

277 ms

default_rss.png

default_rss.png

374 ms

default_email.png

default_email.png

391 ms

default_fb.png

default_fb.png

389 ms

default_twitter.png

default_twitter.png

389 ms

en_US.png

en_US.png

388 ms

fr_FR.png

fr_FR.png

494 ms

MM_4-21-cover.png

MM_4-21-cover.png

1385 ms

PositiveSSL_tl_trans.png

PositiveSSL_tl_trans.png

286 ms

nNLGlOfl1OzZ1Yksrf7NTe3mN+KAIu1M6sZ2Ten4tSOXV2YmrnejTFF63+6YO55nCh1tdxy0X5xieS3dIKs955QVFcUfQjyYFwAA

nNLGlOfl1OzZ1Yksrf7NTe3mN+KAIu1M6sZ2Ten4tSOXV2YmrnejTFF63+6YO55nCh1tdxy0X5xieS3dIKs955QVFcUfQjyYFwAA

2 ms

social-logos.eot

social-logos.eot

348 ms

reftagger.js

reftagger.js

412 ms

t.php

t.php

275 ms

count.json

count.json

227 ms

g.gif

g.gif

217 ms

count.json

count.json

225 ms

count.json

count.json

225 ms

count.json

count.json

236 ms

count.json

count.json

214 ms

g.gif

g.gif

192 ms

g.gif

g.gif

187 ms

g.gif

g.gif

186 ms

g.gif

g.gif

185 ms

trp-ald-ajax.php

trp-ald-ajax.php

326 ms

bg_input.png

bg_input.png

249 ms

log

log

65 ms

Accessibility Review

cogmessenger.org accessibility score

71

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.

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 IDs are not unique

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

cogmessenger.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

cogmessenger.org SEO score

82

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

    N/A

  • Encoding

    N/A

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

cogmessenger.org

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