Tools & Wizards About Us
puritanchurch.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

puritanchurch.com

Puritan Reformed Presbyterian Church: A Westminster Confessional Church

Page Load Speed

3.3 sec in total

First Response

605 ms

Resources Loaded

2.2 sec

Page Rendered

500 ms

puritanchurch.com screenshot

About Website

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

Looking for a reformed church in San Diego? Puritan Reformed Presbyterian Church of San Diego is evangelical, conservative and biblically based.

Visit puritanchurch.com

Key Findings

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

Performance Metrics

puritanchurch.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value16.8 s

0/100

25%

SI (Speed Index)

Value13.7 s

2/100

10%

TBT (Total Blocking Time)

Value1,630 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

Network Requests Diagram

puritanchurch.com

605 ms

global.css

35 ms

frontend.min.css

69 ms

select2.min.css

107 ms

iconfonts.css

104 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 88% of them (75 requests) were addressed to the original Puritanchurch.com, 5% (4 requests) were made to Maps.googleapis.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (714 ms) belongs to the original domain Puritanchurch.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 382.8 kB (10%)

Content Size

4.0 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Puritanchurch.com main page is 4.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 188.9 kB

  • Original 222.7 kB
  • After minification 215.9 kB
  • After compression 33.9 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 188.9 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 92 B

  • Original 2.9 MB
  • After minification 2.9 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. Puritan Church images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 189.3 kB

  • Original 631.6 kB
  • After minification 631.0 kB
  • After compression 442.3 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 189.3 kB or 30% of the original size.

CSS Optimization

-2%

Potential reduce by 4.5 kB

  • Original 223.9 kB
  • After minification 223.8 kB
  • After compression 219.3 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. Puritanchurch.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 66 (85%)

Requests Now

78

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Puritan 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 37 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

puritanchurch.com

puritanchurch.com

605 ms

global.css

global.css

35 ms

frontend.min.css

frontend.min.css

69 ms

select2.min.css

select2.min.css

107 ms

iconfonts.css

iconfonts.css

104 ms

frontend.min.css

frontend.min.css

171 ms

tooltip.css

tooltip.css

109 ms

tooltipster-sideTip-shadow.min.css

tooltipster-sideTip-shadow.min.css

108 ms

featherlight.css

featherlight.css

107 ms

lity.min.css

lity.min.css

137 ms

mec-general-calendar.css

mec-general-calendar.css

142 ms

style.min.css

style.min.css

137 ms

blocks.style.build.css

blocks.style.build.css

142 ms

blocks.style.build.css

blocks.style.build.css

142 ms

yui3.css

yui3.css

191 ms

fl-slideshow.min.css

fl-slideshow.min.css

192 ms

all.min.css

all.min.css

194 ms

animate.css

animate.css

200 ms

jquery.bxslider.css

jquery.bxslider.css

203 ms

style.css

style.css

204 ms

7-layout.css

7-layout.css

239 ms

refsites_post_types-public.css

refsites_post_types-public.css

206 ms

wp-livestream-public.css

wp-livestream-public.css

208 ms

frontend.css

frontend.css

210 ms

7c505db22c02d0d9951ec9b54dd9c7eb-layout-bundle.css

7c505db22c02d0d9951ec9b54dd9c7eb-layout-bundle.css

211 ms

dashicons.min.css

dashicons.min.css

235 ms

style.css

style.css

255 ms

style.css

style.css

255 ms

css2

css2

35 ms

main.min.css

main.min.css

274 ms

beaver.min.css

beaver.min.css

255 ms

wpforms.min.css

wpforms.min.css

269 ms

css

css

59 ms

js

js

65 ms

jquery.min.js

jquery.min.js

271 ms

jquery-migrate.min.js

jquery-migrate.min.js

272 ms

mec-general-calendar.js

mec-general-calendar.js

308 ms

frontend.js

frontend.js

322 ms

events.js

events.js

307 ms

refsites_post_types-public.js

refsites_post_types-public.js

319 ms

wp-livestream-public.js

wp-livestream-public.js

279 ms

jquery.cookie.js

jquery.cookie.js

259 ms

core.min.js

core.min.js

408 ms

datepicker.min.js

datepicker.min.js

409 ms

jquery.typewatch.js

jquery.typewatch.js

408 ms

featherlight.js

featherlight.js

407 ms

select2.full.min.js

select2.full.min.js

408 ms

tooltip.js

tooltip.js

379 ms

lity.min.js

lity.min.js

378 ms

colorbrightness.min.js

colorbrightness.min.js

378 ms

owl.carousel.min.js

owl.carousel.min.js

378 ms

yui3.min.js

yui3.min.js

387 ms

fl-slideshow.min.js

fl-slideshow.min.js

331 ms

jquery.imagesloaded.min.js

jquery.imagesloaded.min.js

327 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

324 ms

jquery.easing.min.js

jquery.easing.min.js

326 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

324 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

324 ms

js_cookie.js

js_cookie.js

323 ms

7-layout.js

7-layout.js

321 ms

frontend.js

frontend.js

651 ms

6da2195b22ae2fc933c4ce96a52e1c7b-layout-bundle.js

6da2195b22ae2fc933c4ce96a52e1c7b-layout-bundle.js

644 ms

frontend-custom-form.js

frontend-custom-form.js

644 ms

main.js

main.js

622 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

605 ms

place

place

466 ms

prpc-logo-white-large.png

prpc-logo-white-large.png

458 ms

Grant-Van-Leuven-DSC_0814-scaled.jpg

Grant-Van-Leuven-DSC_0814-scaled.jpg

683 ms

rm-background2.png

rm-background2.png

714 ms

IMG_2437-scaled.jpeg

IMG_2437-scaled.jpeg

696 ms

prpc-old-paths-wall.jpg

prpc-old-paths-wall.jpg

587 ms

font

font

464 ms

fa-solid-900.woff

fa-solid-900.woff

463 ms

fa-regular-400.woff

fa-regular-400.woff

462 ms

icomoon.ttf

icomoon.ttf

464 ms

Simple-Line-Icons.woff

Simple-Line-Icons.woff

465 ms

Simple-Line-Icons.ttf

Simple-Line-Icons.ttf

465 ms

reftagger.js

reftagger.js

659 ms

bx_loader.gif

bx_loader.gif

157 ms

js

js

129 ms

Grant-Van-Leuven-DSC_0761-scaled-landscape.jpg

Grant-Van-Leuven-DSC_0761-scaled-landscape.jpg

338 ms

search.js

search.js

36 ms

geometry.js

geometry.js

36 ms

main.js

main.js

36 ms

Rainbow-Steeple.jpeg

Rainbow-Steeple.jpeg

41 ms

Accessibility Review

puritanchurch.com accessibility score

94

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

puritanchurch.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

puritanchurch.com SEO score

83

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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    EN

  • Encoding

    UTF-8

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

puritanchurch.com

Open Graph data is detected on the main page of Puritan Church. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: