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.3 sec in total

First Response

218 ms

Resources Loaded

1.8 sec

Page Rendered

311 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 218 ms and then it took 2.1 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)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value46.3 s

0/100

25%

SI (Speed Index)

Value17.7 s

0/100

10%

TBT (Total Blocking Time)

Value6,020 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.434

22/100

15%

TTI (Time to Interactive)

Value72.2 s

0/100

10%

Network Requests Diagram

newlifecity.church

218 ms

newlifecity.church

487 ms

jquery.min.js

96 ms

website.min.css

77 ms

website.min.js

100 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 73.4 kB (5%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Newlifecity.church main page is 1.6 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 28.5 kB

  • Original 39.9 kB
  • After minification 39.4 kB
  • After compression 11.4 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.5 kB or 71% of the original size.

Image Optimization

-4%

Potential reduce by 12.8 kB

  • Original 343.9 kB
  • After minification 331.1 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

-3%

Potential reduce by 32.1 kB

  • 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 29 B

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

Requests Breakdown

Number of requests can be reduced by 14 (58%)

Requests Now

24

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 24 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

newlifecity.church

newlifecity.church

218 ms

newlifecity.church

newlifecity.church

487 ms

jquery.min.js

jquery.min.js

96 ms

website.min.css

website.min.css

77 ms

website.min.js

website.min.js

100 ms

style1725504768.css

style1725504768.css

93 ms

fa-brands-400.ttf

fa-brands-400.ttf

98 ms

fa-brands-400.woff2

fa-brands-400.woff2

96 ms

fa-regular-400.ttf

fa-regular-400.ttf

92 ms

fa-regular-400.woff2

fa-regular-400.woff2

89 ms

fa-solid-900.ttf

fa-solid-900.ttf

104 ms

fa-solid-900.woff2

fa-solid-900.woff2

105 ms

all.min.css

all.min.css

99 ms

hqk1yln.css

hqk1yln.css

96 ms

js

js

121 ms

js

js

200 ms

p.css

p.css

62 ms

10225928_500x200_500.png

10225928_500x200_500.png

330 ms

+49fm56d

+49fm56d

286 ms

11600724_2925x4096_500.jpg

11600724_2925x4096_500.jpg

384 ms

15360241_4928x3264_500.jpg

15360241_4928x3264_500.jpg

389 ms

15360272_1537x2305_500.JPG

15360272_1537x2305_500.JPG

499 ms

15360292_8007x5341_500.jpeg

15360292_8007x5341_500.jpeg

431 ms

web-client-581faf330e112285e8bedded7c4e280f.css

web-client-581faf330e112285e8bedded7c4e280f.css

339 ms

blur.jpg

blur.jpg

61 ms

vendor-e82f3a8bdd1598a097c6207a6019410c.js

vendor-e82f3a8bdd1598a097c6207a6019410c.js

364 ms

chunk.345.a10469c1b70565a7e815.js

chunk.345.a10469c1b70565a7e815.js

499 ms

chunk.143.794c79c2d5d2f640dd84.js

chunk.143.794c79c2d5d2f640dd84.js

92 ms

web-client-a8af6c07020aa4b1e98150b7c545b4ef.js

web-client-a8af6c07020aa4b1e98150b7c545b4ef.js

362 ms

analytics.js

analytics.js

57 ms

64 ms

image.jpg

image.jpg

65 ms

image.jpg

image.jpg

11 ms

ProximaNova-Sbold-webfont-bba11955959ea56cb0c1ae3d3b9b9b2a.woff

ProximaNova-Sbold-webfont-bba11955959ea56cb0c1ae3d3b9b9b2a.woff

275 ms

ProximaNova-Bold-webfont-0988922e8ed380689ca54855833342c9.woff

ProximaNova-Bold-webfont-0988922e8ed380689ca54855833342c9.woff

278 ms

ProximaNova-ExtraBold-webfont-b5afb0b6e2896cbe7ba8b2658d44da58.woff

ProximaNova-ExtraBold-webfont-b5afb0b6e2896cbe7ba8b2658d44da58.woff

78 ms

ProximaNova-Reg-webfont-5d0e746af028be8766181f227b3e87d1.woff

ProximaNova-Reg-webfont-5d0e746af028be8766181f227b3e87d1.woff

290 ms

ProximaNova-Light-webfont-01593b54d9e1069e75813fbd5b81d2dd.woff

ProximaNova-Light-webfont-01593b54d9e1069e75813fbd5b81d2dd.woff

81 ms

proximanova-thin-webfont-91a681efaf81cd7941866a196ad9b2b9.woff

proximanova-thin-webfont-91a681efaf81cd7941866a196ad9b2b9.woff

311 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: