Tools & Wizards About Us
amazinggracelutheran.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

amazinggracelutheran.com

Amazing Grace Lutheran Church - Myrtle Beach Lutheran Church :

Page Load Speed

7.4 sec in total

First Response

414 ms

Resources Loaded

6.6 sec

Page Rendered

373 ms

amazinggracelutheran.com screenshot

About Website

Welcome to amazinggracelutheran.com homepage info - get ready to check Amazing Grace Lutheran best content right away, or after learning these important things about amazinggracelutheran.com

Amazing Grace Lutheran Church, in Myrtle Beach, has been proclaiming the good news that God was in Christ reconciling the world to himself.

Visit amazinggracelutheran.com

Key Findings

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

Performance Metrics

amazinggracelutheran.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

amazinggracelutheran.com

414 ms

autoptimize_92e3a47c162544fafcea916542b69f08.css

239 ms

autoptimize_8a2aa7fca9adbab70234ae2f71409ef6.css

169 ms

wp-polyfill-inert.min.js

176 ms

regenerator-runtime.min.js

175 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 81% of them (78 requests) were addressed to the original Amazinggracelutheran.com, 8% (8 requests) were made to Use.typekit.net and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Amazinggracelutheran.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (17%)

Content Size

9.1 MB

After Optimization

7.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 53.6 kB

  • Original 70.2 kB
  • After minification 69.7 kB
  • After compression 16.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. 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 53.6 kB or 76% of the original size.

Image Optimization

-9%

Potential reduce by 737.4 kB

  • Original 7.9 MB
  • After minification 7.1 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. Amazing Grace Lutheran images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 750.9 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 385.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 750.9 kB or 66% of the original size.

CSS Optimization

-0%

Potential reduce by 194 B

  • Original 50.7 kB
  • After minification 50.7 kB
  • After compression 50.5 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. Amazinggracelutheran.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 63 (72%)

Requests Now

87

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

amazinggracelutheran.com

amazinggracelutheran.com

414 ms

autoptimize_92e3a47c162544fafcea916542b69f08.css

autoptimize_92e3a47c162544fafcea916542b69f08.css

239 ms

autoptimize_8a2aa7fca9adbab70234ae2f71409ef6.css

autoptimize_8a2aa7fca9adbab70234ae2f71409ef6.css

169 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

176 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

175 ms

wp-polyfill.min.js

wp-polyfill.min.js

482 ms

hooks.min.js

hooks.min.js

224 ms

w.js

w.js

43 ms

md5.js

md5.js

231 ms

util.js

util.js

233 ms

jquery.min.js

jquery.min.js

465 ms

jquery-migrate.min.js

jquery-migrate.min.js

281 ms

public.min.js

public.min.js

403 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

295 ms

add-to-cart.min.js

add-to-cart.min.js

294 ms

js.cookie.min.js

js.cookie.min.js

335 ms

woocommerce.min.js

woocommerce.min.js

351 ms

js

js

91 ms

custom-woocommerce.css

custom-woocommerce.css

2167 ms

aos.css

aos.css

62 ms

aos.js

aos.js

82 ms

1afd45f158.js

1afd45f158.js

87 ms

hrq6mbg.css

hrq6mbg.css

1790 ms

js

js

122 ms

comment-reply.min.js

comment-reply.min.js

342 ms

accordion-custom.js

accordion-custom.js

535 ms

accordion.js

accordion.js

399 ms

jquery_cookie.js

jquery_cookie.js

413 ms

sourcebuster.min.js

sourcebuster.min.js

534 ms

order-attribution.min.js

order-attribution.min.js

535 ms

react.min.js

react.min.js

534 ms

deprecated.min.js

deprecated.min.js

591 ms

dom.min.js

dom.min.js

592 ms

react-dom.min.js

react-dom.min.js

710 ms

escape-html.min.js

escape-html.min.js

594 ms

element.min.js

element.min.js

591 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

605 ms

i18n.min.js

i18n.min.js

606 ms

keycodes.min.js

keycodes.min.js

607 ms

priority-queue.min.js

priority-queue.min.js

605 ms

compose.min.js

compose.min.js

712 ms

private-apis.min.js

private-apis.min.js

658 ms

redux-routine.min.js

redux-routine.min.js

658 ms

data.min.js

data.min.js

550 ms

lodash.min.js

lodash.min.js

775 ms

wc-blocks-registry.js

wc-blocks-registry.js

599 ms

url.min.js

url.min.js

604 ms

api-fetch.min.js

api-fetch.min.js

600 ms

wc-settings.js

wc-settings.js

594 ms

data-controls.min.js

data-controls.min.js

602 ms

html-entities.min.js

html-entities.min.js

568 ms

notices.min.js

notices.min.js

602 ms

wc-blocks-middleware.js

wc-blocks-middleware.js

588 ms

wc-blocks-data.js

wc-blocks-data.js

713 ms

dom-ready.min.js

dom-ready.min.js

569 ms

a11y.min.js

a11y.min.js

586 ms

primitives.min.js

primitives.min.js

547 ms

warning.min.js

warning.min.js

562 ms

blocks-components.js

blocks-components.js

708 ms

blocks-checkout.js

blocks-checkout.js

646 ms

order-attribution-blocks.min.js

order-attribution-blocks.min.js

539 ms

g.gif

g.gif

138 ms

global.js

global.js

443 ms

jquery.accessible-menu.js

jquery.accessible-menu.js

478 ms

jquery.royalslider.min.js

jquery.royalslider.min.js

538 ms

p.css

p.css

47 ms

autoptimize_645e25746732f92ab8912b8a07744c57.css

autoptimize_645e25746732f92ab8912b8a07744c57.css

85 ms

analytics.js

analytics.js

56 ms

logo.jpg

logo.jpg

183 ms

bg-new.jpg

bg-new.jpg

284 ms

bg-event.jpg

bg-event.jpg

302 ms

bg-upcoming.jpg

bg-upcoming.jpg

287 ms

bg-member.jpg

bg-member.jpg

222 ms

d

d

126 ms

d

d

270 ms

d

d

324 ms

d

d

372 ms

d

d

562 ms

d

d

796 ms

d

d

942 ms

bg-enews.jpg

bg-enews.jpg

154 ms

collect

collect

40 ms

icomoon.svg

icomoon.svg

121 ms

grab.png

grab.png

83 ms

Epiphany-2024.png

Epiphany-2024.png

451 ms

Helping-the-Hurting2.png

Helping-the-Hurting2.png

1961 ms

Kids-GROW.png

Kids-GROW.png

783 ms

Service-Invite.png

Service-Invite.png

878 ms

Mornings-with-Mommy2.png

Mornings-with-Mommy2.png

680 ms

preloader-white.gif

preloader-white.gif

124 ms

rs-universal.png

rs-universal.png

179 ms

Epiphany-2024-V.png

Epiphany-2024-V.png

529 ms

Helping-the-Hurting-V.png

Helping-the-Hurting-V.png

620 ms

Kids-GROW1.png

Kids-GROW1.png

647 ms

Service-Invite-Vertical.png

Service-Invite-Vertical.png

788 ms

Mornings-with-Mommy-Vertical1.png

Mornings-with-Mommy-Vertical1.png

766 ms

Accessibility Review

amazinggracelutheran.com accessibility score

82

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

amazinggracelutheran.com best practices score

75

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

amazinggracelutheran.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Amazinggracelutheran.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 Amazinggracelutheran.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

amazinggracelutheran.com

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