Online.church Site Title

Launch Your Online Ministry for Free | Church Online Platform

Online.church Meta Description

The Church Online Platform is a free tool to help you launch an engaging online ministry. Explore features built by the Church, for the Church to help you engage your attenders and lead to next steps.

Online.church Test Results

Online.church Mobile Performance: 40/100
Quick overview:
Max Potential First Input Delay
550 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Time to Interactive
9.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
First Meaningful Paint
2.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Final Screenshot
The last screenshot captured of the pageload.

2355707901248

Script Treemap Data
Used for treemap app
Diagnostics
Collection of useful page vitals.
Network Requests
Lists the network requests that were made during page load.
Network Round Trip Times
130 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
Server Backend Latencies
340 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Metrics
Collects all available metrics.

Online.church Mobile SEO: 100/100
Quick overview:

Online.church Mobile Best Practices: 68/100
Quick overview:
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
General
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Online.church Mobile PWA: 75/100
Quick overview:
PWA Optimized
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more about splash screens. Failures: Manifest does not have a PNG icon of at least 512px.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn about maskable manifest icons.
Online.church Mobile Accessibility: 72/100
Quick overview:
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.
Elements with `role="dialog"` or `role="alertdialog"` do not have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
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.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Audio and video
These are opportunities to provide alternative content for audio and video. This may improve the experience for users with hearing or vision impairments.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Similar tests
www.online.com
www.online.net
www.online.org
www.online.info
www.online.biz
www.online.us
www.online.mobi
www.nline.church
www.online.church
www.inline.church
www.oinline.church
www.ionline.church
www.knline.church
www.oknline.church
www.konline.church
www.lnline.church
www.olnline.church
www.lonline.church
www.pnline.church
www.opnline.church
www.ponline.church
www.oline.church
www.obline.church
www.onbline.church
www.obnline.church
www.ohline.church
www.onhline.church
www.ohnline.church
www.ojline.church
www.onjline.church
www.ojnline.church
www.omline.church
www.onmline.church
www.omnline.church
www.onine.church
www.onpine.church
www.onlpine.church
www.onpline.church
www.onoine.church
www.onloine.church
www.onoline.church
www.onkine.church
www.onlkine.church
www.onkline.church
www.onlne.church
www.onlune.church
www.onliune.church
www.onluine.church
www.onljne.church
www.onlijne.church
www.onljine.church
www.onlkne.church
www.onlikne.church
www.onlone.church
www.onlione.church
www.onlie.church
www.onlibe.church
www.onlinbe.church
www.onlibne.church
www.onlihe.church
www.onlinhe.church
www.onlihne.church
www.onlije.church
www.onlinje.church
www.onlime.church
www.onlinme.church
www.onlimne.church
www.onlin.church
www.onlinw.church
www.onlinew.church
www.onlinwe.church
www.onlins.church
www.onlines.church
www.onlinse.church
www.onlind.church
www.onlined.church
www.onlinde.church
www.onlinr.church
www.onliner.church
www.onlinre.church
Last Tested: