Tools & Wizards About Us
radiance.church screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

radiance.church

Radiance Church - Home

Page Load Speed

2.2 sec in total

First Response

275 ms

Resources Loaded

1.7 sec

Page Rendered

236 ms

radiance.church screenshot

About Website

Click here to check amazing Radiance content. Otherwise, check out these important facts you probably never knew about radiance.church

We are an authentic community, passionately following Jesus!

Visit radiance.church

Key Findings

We analyzed Radiance.church page load time and found that the first response time was 275 ms and then it took 1.9 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

radiance.church performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value15.6 s

0/100

10%

TBT (Total Blocking Time)

Value7,500 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value58.0 s

0/100

10%

Network Requests Diagram

radiance.church

275 ms

radiance.church

478 ms

jquery.min.js

52 ms

website.min.css

43 ms

website.min.js

61 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Radiance.church, 29% (9 requests) were made to Assets2.snappages.site and 29% (9 requests) were made to Dashboard.static.subsplash.com. The less responsive or slowest element that took the longest time to load (478 ms) belongs to the original domain Radiance.church.

Page Optimization Overview & Recommendations

Page size can be reduced by 38.1 kB (3%)

Content Size

1.3 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Radiance.church 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. 50% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 21.6 kB

  • Original 30.2 kB
  • After minification 29.9 kB
  • After compression 8.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 21.6 kB or 71% of the original size.

Image Optimization

-13%

Potential reduce by 16.3 kB

  • Original 124.8 kB
  • After minification 108.4 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. Obviously, Radiance needs image optimization as it can save up to 16.3 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 146 B

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 1.1 MB

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 41 B

  • Original 91.8 kB
  • After minification 91.7 kB
  • After compression 91.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. Radiance.church has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (71%)

Requests Now

17

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Radiance. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

radiance.church

radiance.church

275 ms

radiance.church

radiance.church

478 ms

jquery.min.js

jquery.min.js

52 ms

website.min.css

website.min.css

43 ms

website.min.js

website.min.js

61 ms

style1729636785.css

style1729636785.css

42 ms

fa-brands-400.ttf

fa-brands-400.ttf

60 ms

fa-brands-400.woff2

fa-brands-400.woff2

58 ms

fa-regular-400.ttf

fa-regular-400.ttf

56 ms

fa-regular-400.woff2

fa-regular-400.woff2

57 ms

fa-solid-900.ttf

fa-solid-900.ttf

88 ms

fa-solid-900.woff2

fa-solid-900.woff2

82 ms

all.min.css

all.min.css

84 ms

hqk1yln.css

hqk1yln.css

89 ms

*

*

285 ms

p.css

p.css

21 ms

web-client-581faf330e112285e8bedded7c4e280f.css

web-client-581faf330e112285e8bedded7c4e280f.css

115 ms

vendor-e82f3a8bdd1598a097c6207a6019410c.js

vendor-e82f3a8bdd1598a097c6207a6019410c.js

123 ms

chunk.345.a10469c1b70565a7e815.js

chunk.345.a10469c1b70565a7e815.js

347 ms

chunk.143.794c79c2d5d2f640dd84.js

chunk.143.794c79c2d5d2f640dd84.js

80 ms

web-client-a8af6c07020aa4b1e98150b7c545b4ef.js

web-client-a8af6c07020aa4b1e98150b7c545b4ef.js

122 ms

analytics.js

analytics.js

37 ms

48 ms

image.jpg

image.jpg

40 ms

image.jpg

image.jpg

10 ms

ProximaNova-Sbold-webfont-bba11955959ea56cb0c1ae3d3b9b9b2a.woff

ProximaNova-Sbold-webfont-bba11955959ea56cb0c1ae3d3b9b9b2a.woff

259 ms

ProximaNova-Bold-webfont-0988922e8ed380689ca54855833342c9.woff

ProximaNova-Bold-webfont-0988922e8ed380689ca54855833342c9.woff

276 ms

ProximaNova-ExtraBold-webfont-b5afb0b6e2896cbe7ba8b2658d44da58.woff

ProximaNova-ExtraBold-webfont-b5afb0b6e2896cbe7ba8b2658d44da58.woff

257 ms

ProximaNova-Reg-webfont-5d0e746af028be8766181f227b3e87d1.woff

ProximaNova-Reg-webfont-5d0e746af028be8766181f227b3e87d1.woff

269 ms

ProximaNova-Light-webfont-01593b54d9e1069e75813fbd5b81d2dd.woff

ProximaNova-Light-webfont-01593b54d9e1069e75813fbd5b81d2dd.woff

282 ms

proximanova-thin-webfont-91a681efaf81cd7941866a196ad9b2b9.woff

proximanova-thin-webfont-91a681efaf81cd7941866a196ad9b2b9.woff

271 ms

Accessibility Review

radiance.church accessibility score

66

Accessibility Issues

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

Form elements do not have associated labels

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

radiance.church best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

radiance.church SEO score

85

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

Links do not have descriptive text

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

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 Radiance.church 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 Radiance.church 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

radiance.church

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