Se.church Site Title

You’re in the Right Place! | Southeast Christian Church

Se.church Meta Description

We want you here. If you’re new to church or just new to Southeast, we’re glad you found us. Check out our locations and join us.

Se.church Test Results

Se.church Mobile Performance: 55/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid multiple page redirects
Est savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Largest Contentful Paint image was lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.
Serve images in next-gen formats
Est savings of 535 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Reduce unused JavaScript
Est savings of 226 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Defer offscreen images
Est savings of 336 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Reduce unused CSS
Est savings of 14 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Largest Contentful Paint element
26,040 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Properly size images
Est savings of 374 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Eliminate render-blocking resources
Est savings of 4,550 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Serve static assets with an efficient cache policy
17 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Efficiently encode images
Est savings of 57 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Avoid enormous network payloads
Total size was 4,830 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Avoid serving legacy JavaScript to modern browsers
Est savings of 1 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Render blocking requests
Est savings of 4,620 ms
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Network dependency tree
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Improve image delivery
Est savings of 1,325 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Use efficient cache lifetimes
Est savings of 273 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Document request latency
Est savings of 500 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Time to Interactive
26.4 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.
Font display
Est savings of 40 ms
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Se.church Mobile SEO: 92/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
3 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Se.church Mobile Best Practices: 76/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.
General
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
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Se.church Mobile Accessibility: 92/100
Quick overview:
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.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
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 sites
Similar tests
www.se.com
www.se.net
www.se.org
www.se.info
www.se.biz
www.se.us
www.se.mobi
www.e.church
www.se.church
www.we.church
www.swe.church
www.wse.church
www.ee.church
www.see.church
www.ese.church
www.de.church
www.sde.church
www.dse.church
www.ze.church
www.sze.church
www.zse.church
www.xe.church
www.sxe.church
www.xse.church
www.ae.church
www.sae.church
www.ase.church
www.s.church
www.sw.church
www.sew.church
www.ss.church
www.ses.church
www.sse.church
www.sd.church
www.sed.church
www.sr.church
www.ser.church
www.sre.church
Last Tested: