Tools & Wizards About Us
churchinphoenix.org screenshot

Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

churchinphoenix.org

THE CHURCH IN PHOENIX - Lovers of Jesus affiliated with local churches, Watchman Nee, Witness Lee (Splash Page)

Page Load Speed

681 ms in total

First Response

31 ms

Resources Loaded

576 ms

Page Rendered

74 ms

churchinphoenix.org screenshot

About Website

Visit churchinphoenix.org now to see the best up-to-date CHURCH In PHOENIX content and also check out these interesting facts you probably never knew about churchinphoenix.org

A local church, the church in Phoenix, enjoys Christ and recommends the ministry of Witness Lee, Watchman Nee.

Visit churchinphoenix.org

Key Findings

We analyzed Churchinphoenix.org page load time and found that the first response time was 31 ms and then it took 650 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

churchinphoenix.org performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value1.7 s

99/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

churchinphoenix.org

31 ms

churchinphoenix.org

15 ms

templatestyle.css

204 ms

button_welcome.gif

56 ms

button_welcome2.gif

207 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that all of those requests were addressed to Churchinphoenix.org and no external sources were called. The less responsive or slowest element that took the longest time to load (321 ms) belongs to the original domain Churchinphoenix.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 6.8 kB (38%)

Content Size

18.0 kB

After Optimization

11.1 kB

  • HTML
  • Images

In fact, the total size of Churchinphoenix.org main page is 18.0 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 9.5 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 6.8 kB

  • Original 8.4 kB
  • After minification 6.5 kB
  • After compression 1.6 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. This page needs HTML code to be minified as it can gain 1.9 kB, which is 23% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 6.8 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 9.5 kB
  • After minification 9.5 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. CHURCH In PHOENIX images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 15 (75%)

Requests Now

20

After Optimization

5

  • Images

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CHURCH In PHOENIX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Network Requests Diagram

churchinphoenix.org

churchinphoenix.org

31 ms

churchinphoenix.org

churchinphoenix.org

15 ms

templatestyle.css

templatestyle.css

204 ms

button_welcome.gif

button_welcome.gif

56 ms

button_welcome2.gif

button_welcome2.gif

207 ms

button_beliefs.gif

button_beliefs.gif

209 ms

button_beliefs2.gif

button_beliefs2.gif

208 ms

button_history.gif

button_history.gif

210 ms

button_history2.gif

button_history2.gif

208 ms

button_test.gif

button_test.gif

109 ms

button_test2.gif

button_test2.gif

163 ms

button_contact.gif

button_contact.gif

217 ms

button_contact2.gif

button_contact2.gif

260 ms

top_left.gif

top_left.gif

260 ms

top_middle.gif

top_middle.gif

260 ms

button_top.gif

button_top.gif

263 ms

button_bottom.gif

button_bottom.gif

261 ms

space.gif

space.gif

269 ms

banner_title.gif

banner_title.gif

313 ms

middle_left.gif

middle_left.gif

312 ms

middle_splash.jpg

middle_splash.jpg

312 ms

middle_right.gif

middle_right.gif

321 ms

bottom.gif

bottom.gif

315 ms

Accessibility Review

churchinphoenix.org accessibility score

58

Accessibility Issues

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

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

churchinphoenix.org best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

churchinphoenix.org SEO score

67

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

Image elements do not have [alt] attributes

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

churchinphoenix.org

Open Graph description is not detected on the main page of CHURCH In PHOENIX. 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: