Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

lifenz.org

A Church To Call Home - LIFE

Page Load Speed

5.2 sec in total

First Response

1.3 sec

Resources Loaded

3 sec

Page Rendered

864 ms

About Website

Welcome to lifenz.org homepage info - get ready to check LIFE Nz best content for New Zealand right away, or after learning these important things about lifenz.org

We see church as a place to call home. An open door, that extends to everyone who desires to discover and develop a real relationship with a loving and grace-filled God.

Visit lifenz.org

Key Findings

We analyzed Lifenz.org page load time and found that the first response time was 1.3 sec 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

lifenz.org performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value930 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.262

47/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

Network Requests Diagram

lifenz.org

1314 ms

twemoji.js

345 ms

wp-emoji.js

357 ms

site.css

364 ms

jquery.js

62 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 23% of them (13 requests) were addressed to the original Lifenz.org, 32% (18 requests) were made to Res.cloudinary.com and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Lifenz.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 83.0 kB (4%)

Content Size

1.9 MB

After Optimization

1.9 MB

In fact, the total size of Lifenz.org main page is 1.9 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. 60% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 50.9 kB

  • Original 65.2 kB
  • After minification 65.1 kB
  • After compression 14.2 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 50.9 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 16.6 kB

  • Original 1.5 MB
  • After minification 1.4 MB

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. LIFE Nz images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 15.5 kB

  • Original 372.6 kB
  • After minification 372.6 kB
  • After compression 357.1 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 5 B

  • Original 49.5 kB
  • After minification 49.5 kB
  • After compression 49.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. Lifenz.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (50%)

Requests Now

48

After Optimization

24

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

Accessibility Review

lifenz.org accessibility score

80

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

lifenz.org 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

Page has valid source maps

SEO Factors

lifenz.org SEO score

85

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifenz.org 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 Lifenz.org 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

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