Tools & Wizards About Us
newlifecity.church screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

newlifecity.church

New Life CityChurch - A Downtown Kansas City Church - Home

Page Load Speed

2.2 sec in total

First Response

206 ms

Resources Loaded

1.6 sec

Page Rendered

332 ms

newlifecity.church screenshot

About Website

Welcome to newlifecity.church homepage info - get ready to check New Life City best content right away, or after learning these important things about newlifecity.church

We are a Downtown Kansas City church, ministering in and to the center of the city, a network of neighbors, people from across the metro worship with us and serve where they live, work and play

Visit newlifecity.church

Key Findings

We analyzed Newlifecity.church page load time and found that the first response time was 206 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

newlifecity.church performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value24.5 s

0/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value6,050 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.483

17/100

15%

TTI (Time to Interactive)

Value62.1 s

0/100

10%

Network Requests Diagram

newlifecity.church

206 ms

newlifecity.church

535 ms

jquery.min.js

58 ms

website.min.css

60 ms

website.min.js

72 ms

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

Page Optimization Overview & Recommendations

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

Content Size

1.4 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Newlifecity.church main page is 1.4 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. Javascripts take 990.1 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 28.2 kB

  • Original 40.0 kB
  • After minification 39.5 kB
  • After compression 11.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 28.2 kB or 71% of the original size.

Image Optimization

-4%

Potential reduce by 12.6 kB

  • Original 308.2 kB
  • After minification 295.6 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. New Life City images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 447 B

  • Original 990.1 kB
  • After minification 990.1 kB
  • After compression 989.6 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 27 B

  • Original 89.0 kB
  • After minification 89.0 kB
  • After compression 89.0 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. Newlifecity.church has all CSS files already compressed.

Requests Breakdown

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

Requests Now

23

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

newlifecity.church

newlifecity.church

206 ms

newlifecity.church

newlifecity.church

535 ms

jquery.min.js

jquery.min.js

58 ms

website.min.css

website.min.css

60 ms

website.min.js

website.min.js

72 ms

style1692146160.css

style1692146160.css

68 ms

fa-brands-400.ttf

fa-brands-400.ttf

73 ms

fa-brands-400.woff2

fa-brands-400.woff2

71 ms

fa-regular-400.ttf

fa-regular-400.ttf

68 ms

fa-regular-400.woff2

fa-regular-400.woff2

68 ms

fa-solid-900.ttf

fa-solid-900.ttf

84 ms

fa-solid-900.woff2

fa-solid-900.woff2

81 ms

all.min.css

all.min.css

73 ms

js

js

138 ms

10225928_500x200_500.png

10225928_500x200_500.png

302 ms

*recent

*recent

329 ms

11600724_2925x4096_500.jpg

11600724_2925x4096_500.jpg

397 ms

11587634_1280x720_500.jpg

11587634_1280x720_500.jpg

461 ms

11587639_1537x2305_500.JPG

11587639_1537x2305_500.JPG

508 ms

10350795_2304x1536_500.JPG

10350795_2304x1536_500.JPG

408 ms

38 ms

68 ms

web-client-bb9aca65428ae8f3eb46a7fdb912682c.css

web-client-bb9aca65428ae8f3eb46a7fdb912682c.css

155 ms

blur.jpg

blur.jpg

69 ms

image.jpg

image.jpg

75 ms

vendor-9d17d536fd7112143f70ea8fb39ab337.js

vendor-9d17d536fd7112143f70ea8fb39ab337.js

180 ms

chunk.695.07e104dbf78548f8c5b7.js

chunk.695.07e104dbf78548f8c5b7.js

395 ms

chunk.143.6be5ee910e9f37070e33.js

chunk.143.6be5ee910e9f37070e33.js

255 ms

web-client-b326da7930d78c8bfcfd00ef64789928.js

web-client-b326da7930d78c8bfcfd00ef64789928.js

177 ms

analytics.js

analytics.js

61 ms

68 ms

image.jpg

image.jpg

17 ms

ProximaNova-Sbold-webfont-bba11955959ea56cb0c1ae3d3b9b9b2a.woff

ProximaNova-Sbold-webfont-bba11955959ea56cb0c1ae3d3b9b9b2a.woff

272 ms

ProximaNova-Bold-webfont-0988922e8ed380689ca54855833342c9.woff

ProximaNova-Bold-webfont-0988922e8ed380689ca54855833342c9.woff

260 ms

ProximaNova-ExtraBold-webfont-b5afb0b6e2896cbe7ba8b2658d44da58.woff

ProximaNova-ExtraBold-webfont-b5afb0b6e2896cbe7ba8b2658d44da58.woff

268 ms

ProximaNova-Reg-webfont-5d0e746af028be8766181f227b3e87d1.woff

ProximaNova-Reg-webfont-5d0e746af028be8766181f227b3e87d1.woff

299 ms

ProximaNova-Light-webfont-01593b54d9e1069e75813fbd5b81d2dd.woff

ProximaNova-Light-webfont-01593b54d9e1069e75813fbd5b81d2dd.woff

274 ms

proximanova-thin-webfont-91a681efaf81cd7941866a196ad9b2b9.woff

proximanova-thin-webfont-91a681efaf81cd7941866a196ad9b2b9.woff

288 ms

Accessibility Review

newlifecity.church accessibility score

55

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

newlifecity.church SEO score

79

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

High

Image elements do not have [alt] attributes

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

newlifecity.church

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