Report Summary

  • 91

    Performance

    Renders faster than
    91% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

communionware.com

Communion pottery by Debra Ocepek. Ocepek Pottery from Ohio, USA hand-crafted communion ware. Clay Eucharist vessels for church. Spirit Pottery Christ...

Page Load Speed

389 ms in total

First Response

44 ms

Resources Loaded

153 ms

Page Rendered

192 ms

communionware.com screenshot

About Website

Welcome to communionware.com homepage info - get ready to check Communion Ware best content right away, or after learning these important things about communionware.com

Communion pottery by Debra Ocepek. Ocepek Pottery in Ohio, USA hand-crafted communion pottery. Wheel-thrown stoneware eucharist clay vessels for church. Spirit Pottery Ceramic communion set, Lenten Po...

Visit communionware.com

Key Findings

We analyzed Communionware.com page load time and found that the first response time was 44 ms and then it took 345 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

communionware.com performance score

91

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

98/100

25%

SI (Speed Index)

Value1.1 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.267

46/100

15%

TTI (Time to Interactive)

Value1.1 s

100/100

10%

Network Requests Diagram

communionware.com

44 ms

communionware.com

68 ms

bricks01.jpg

8 ms

wheel1a.jpg

8 ms

stickynotefreeshp2.jpg

9 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 11.3 kB (5%)

Content Size

206.1 kB

After Optimization

194.8 kB

In fact, the total size of Communionware.com main page is 206.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 197.7 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 5.9 kB

  • Original 8.4 kB
  • After minification 8.3 kB
  • After compression 2.5 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 5.9 kB or 70% of the original size.

Image Optimization

-3%

Potential reduce by 5.5 kB

  • Original 197.7 kB
  • After minification 192.3 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. Communion Ware images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

15

After Optimization

15

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Communion Ware. According to our analytics all requests are already optimized.

Accessibility Review

communionware.com accessibility score

90

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

communionware.com SEO score

99

Search Engine Optimization Advices

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Communionware.com 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 Communionware.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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