Tools & Wizards About Us
waterfrontchurch.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

waterfrontchurch.com

Waterfront Community Church | Reaching People, Touching Lives

Page Load Speed

3.2 sec in total

First Response

78 ms

Resources Loaded

2.3 sec

Page Rendered

828 ms

waterfrontchurch.com screenshot

About Website

Click here to check amazing Waterfront Church content. Otherwise, check out these important facts you probably never knew about waterfrontchurch.com

Our congregation in Swansea, South Wales consists of all age groups, with a contemporary approach to both worship and community activities.

Visit waterfrontchurch.com

Key Findings

We analyzed Waterfrontchurch.com page load time and found that the first response time was 78 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

waterfrontchurch.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value1,230 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

waterfrontchurch.com

78 ms

www.waterfrontchurch.org

209 ms

www.waterfrontchurch.org

509 ms

styles-c38b1060.css

198 ms

leaflet.css

24 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Waterfrontchurch.com, 34% (16 requests) were made to Waterfrontchurch.org and 15% (7 requests) were made to A.tile.openstreetmap.org. The less responsive or slowest element that took the longest time to load (695 ms) relates to the external source Waterfrontchurch.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 801.7 kB (20%)

Content Size

3.9 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Waterfrontchurch.com main page is 3.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. 45% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 35.6 kB

  • Original 43.7 kB
  • After minification 38.3 kB
  • After compression 8.1 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 5.4 kB, which is 12% 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 35.6 kB or 82% of the original size.

Image Optimization

-13%

Potential reduce by 389.4 kB

  • Original 3.1 MB
  • After minification 2.7 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. Obviously, Waterfront Church needs image optimization as it can save up to 389.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-45%

Potential reduce by 300.7 kB

  • Original 671.3 kB
  • After minification 671.3 kB
  • After compression 370.6 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 300.7 kB or 45% of the original size.

CSS Optimization

-59%

Potential reduce by 75.9 kB

  • Original 129.3 kB
  • After minification 129.3 kB
  • After compression 53.4 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. Waterfrontchurch.com needs all CSS files to be minified and compressed as it can save up to 75.9 kB or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (26%)

Requests Now

43

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Waterfront Church. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

waterfrontchurch.com

waterfrontchurch.com

78 ms

www.waterfrontchurch.org

www.waterfrontchurch.org

209 ms

www.waterfrontchurch.org

www.waterfrontchurch.org

509 ms

styles-c38b1060.css

styles-c38b1060.css

198 ms

leaflet.css

leaflet.css

24 ms

wk-styles-5d609fb5.css

wk-styles-5d609fb5.css

378 ms

jquery.min.js

jquery.min.js

470 ms

jquery-noconflict.js

jquery-noconflict.js

298 ms

jquery-migrate.min.js

jquery-migrate.min.js

297 ms

api.js

api.js

55 ms

analytics.js

analytics.js

33 ms

scripts-88633808.js

scripts-88633808.js

690 ms

leaflet.js

leaflet.js

30 ms

map.min.js

map.min.js

294 ms

uikit2-c2782add.js

uikit2-c2782add.js

576 ms

wk-scripts-1ccc5a55.js

wk-scripts-1ccc5a55.js

495 ms

recaptcha__en.js

recaptcha__en.js

23 ms

collect

collect

86 ms

5439.png

5439.png

53 ms

5438.png

5438.png

44 ms

5439.png

5439.png

48 ms

marker-icon.png

marker-icon.png

33 ms

5438.png

5438.png

48 ms

5440.png

5440.png

50 ms

5438.png

5438.png

53 ms

5440.png

5440.png

52 ms

5439.png

5439.png

52 ms

5439.png

5439.png

51 ms

5440.png

5440.png

29 ms

5438.png

5438.png

39 ms

5439.png

5439.png

46 ms

5438.png

5438.png

39 ms

5440.png

5440.png

37 ms

5440.png

5440.png

45 ms

marker-shadow.png

marker-shadow.png

23 ms

waterfront-community-church-a1a5a27e.png

waterfront-community-church-a1a5a27e.png

122 ms

hendy-web-logo.png

hendy-web-logo.png

216 ms

5439.png

5439.png

38 ms

5440.png

5440.png

37 ms

5439.png

5439.png

38 ms

5440.png

5440.png

43 ms

5438.png

5438.png

37 ms

5438.png

5438.png

36 ms

font-2c0bdc24.woff

font-2c0bdc24.woff

115 ms

mainchurch-75685bae.jpeg

mainchurch-75685bae.jpeg

695 ms

welcome-e30620ac.png

welcome-e30620ac.png

400 ms

js

js

58 ms

Accessibility Review

waterfrontchurch.com accessibility score

84

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

waterfrontchurch.com 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

SEO Factors

waterfrontchurch.com SEO score

92

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

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

    EN

  • Encoding

    UTF-8

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

waterfrontchurch.com

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