Tools & Wizards About Us
plymouth-church.net screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

plymouth-church.net

Page Load Speed

2.2 sec in total

First Response

153 ms

Resources Loaded

1.5 sec

Page Rendered

584 ms

plymouth-church.net screenshot

About Website

Visit plymouth-church.net now to see the best up-to-date Plymouth Church content for United States and also check out these interesting facts you probably never knew about plymouth-church.net

Visit plymouth-church.net

Key Findings

We analyzed Plymouth-church.net page load time and found that the first response time was 153 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

plymouth-church.net performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value15.7 s

0/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value5,290 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.054

98/100

15%

TTI (Time to Interactive)

Value22.3 s

1/100

10%

Network Requests Diagram

plymouth-church.net

153 ms

www.plymouth-church.net

86 ms

select2.min.css

15 ms

iconfonts.css

18 ms

frontend.min.css

47 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 75% of them (68 requests) were addressed to the original Plymouth-church.net, 9% (8 requests) were made to Google.com and 7% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (430 ms) belongs to the original domain Plymouth-church.net.

Page Optimization Overview & Recommendations

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

Content Size

2.2 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Plymouth-church.net main page is 2.2 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. Only a small number of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 70.0 kB

  • Original 85.6 kB
  • After minification 81.5 kB
  • After compression 15.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 70.0 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-16%

Potential reduce by 122.1 kB

  • Original 755.0 kB
  • After minification 755.0 kB
  • After compression 632.9 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 122.1 kB or 16% of the original size.

CSS Optimization

-14%

Potential reduce by 35.4 kB

  • Original 245.9 kB
  • After minification 245.5 kB
  • After compression 210.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. Plymouth-church.net needs all CSS files to be minified and compressed as it can save up to 35.4 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (83%)

Requests Now

78

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

plymouth-church.net

plymouth-church.net

153 ms

www.plymouth-church.net

www.plymouth-church.net

86 ms

select2.min.css

select2.min.css

15 ms

iconfonts.css

iconfonts.css

18 ms

frontend.min.css

frontend.min.css

47 ms

tooltip.css

tooltip.css

45 ms

tooltipster-sideTip-shadow.min.css

tooltipster-sideTip-shadow.min.css

44 ms

featherlight.css

featherlight.css

43 ms

lity.min.css

lity.min.css

40 ms

mec-general-calendar.css

mec-general-calendar.css

40 ms

style.min.css

style.min.css

82 ms

style.css

style.css

78 ms

style.css

style.css

82 ms

style.css

style.css

77 ms

styles.css

styles.css

78 ms

staff-directory.css

staff-directory.css

79 ms

lity.min.css

lity.min.css

93 ms

styles.min.css

styles.min.css

93 ms

bootstrap-select.min.css

bootstrap-select.min.css

89 ms

bootstrap-datepicker.min.css

bootstrap-datepicker.min.css

90 ms

slick.css

slick.css

87 ms

generic-no-float.min.css

generic-no-float.min.css

91 ms

dflip.min.css

dflip.min.css

120 ms

jquery.min.js

jquery.min.js

125 ms

jquery-migrate.min.js

jquery-migrate.min.js

116 ms

mec-general-calendar.js

mec-general-calendar.js

125 ms

tooltip.js

tooltip.js

123 ms

frontend.js

frontend.js

118 ms

events.js

events.js

125 ms

snap.svg-min.js

snap.svg-min.js

130 ms

js

js

140 ms

api.js

api.js

129 ms

core.min.js

core.min.js

129 ms

datepicker.min.js

datepicker.min.js

128 ms

jquery.typewatch.js

jquery.typewatch.js

128 ms

featherlight.js

featherlight.js

129 ms

select2.full.min.js

select2.full.min.js

128 ms

lity.min.js

lity.min.js

137 ms

colorbrightness.min.js

colorbrightness.min.js

129 ms

api.js

api.js

138 ms

popper.min.js

popper.min.js

122 ms

api.js

api.js

156 ms

owl.carousel.min.js

owl.carousel.min.js

135 ms

index.js

index.js

134 ms

index.js

index.js

126 ms

gtm4wp-contact-form-7-tracker.js

gtm4wp-contact-form-7-tracker.js

105 ms

bootstrap.min.js

bootstrap.min.js

105 ms

lity.min.js

lity.min.js

109 ms

bootstrap-select.min.js

bootstrap-select.min.js

110 ms

bootstrap-datepicker.min.js

bootstrap-datepicker.min.js

107 ms

slick.min.js

slick.min.js

72 ms

wpo.js

wpo.js

74 ms

wpo-settings.js

wpo-settings.js

72 ms

wpo-utility.js

wpo-utility.js

74 ms

wpo-snap-svg.js

wpo-snap-svg.js

76 ms

wpo-lazy-loader.js

wpo-lazy-loader.js

71 ms

wpo-common.js

wpo-common.js

69 ms

dflip.min.js

dflip.min.js

67 ms

wp-polyfill.min.js

wp-polyfill.min.js

64 ms

index.js

index.js

65 ms

css2

css2

63 ms

css2

css2

78 ms

gtm.js

gtm.js

199 ms

logo.svg

logo.svg

187 ms

recaptcha__en.js

recaptcha__en.js

288 ms

RED2-11-e1609177505336.jpg

RED2-11-e1609177505336.jpg

221 ms

hero_swoop.svg

hero_swoop.svg

179 ms

Don-Olsen-DSC_1619.jpg

Don-Olsen-DSC_1619.jpg

219 ms

united-nations-covid-19-response-g4z85Zc-ZqI-unsplash.jpg

united-nations-covid-19-response-g4z85Zc-ZqI-unsplash.jpg

181 ms

alexander-dummer-UH-xs-FizTk-unsplash.jpg

alexander-dummer-UH-xs-FizTk-unsplash.jpg

190 ms

Don-Olsen-DSC_6324b.jpg

Don-Olsen-DSC_6324b.jpg

219 ms

footer_border.svg

footer_border.svg

185 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

95 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCP.ttf

403 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf

403 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf

404 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf

403 ms

o-0FIpksx3QOlH0.ttf

o-0FIpksx3QOlH0.ttf

405 ms

fa-light-300.woff

fa-light-300.woff

30 ms

fa-regular-400.woff

fa-regular-400.woff

30 ms

fa-solid-900.woff

fa-solid-900.woff

26 ms

fa-brands-400.woff

fa-brands-400.woff

25 ms

anchor

anchor

146 ms

anchor

anchor

140 ms

ajax-loader.gif

ajax-loader.gif

430 ms

styles__ltr.css

styles__ltr.css

48 ms

recaptcha__en.js

recaptcha__en.js

51 ms

81IjrRH91DAKpIx-VEJHPdpf7wiRaH8tg-uktu3LK4I.js

81IjrRH91DAKpIx-VEJHPdpf7wiRaH8tg-uktu3LK4I.js

126 ms

webworker.js

webworker.js

116 ms

LdkrfvGznG7C1HMIvZeXpqeQHj2pK-25iJPmRAnKECo.js

LdkrfvGznG7C1HMIvZeXpqeQHj2pK-25iJPmRAnKECo.js

77 ms

logo_48.png

logo_48.png

63 ms

Accessibility Review

plymouth-church.net accessibility score

91

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Document doesn't have a <title> element

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

plymouth-church.net 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

Page has valid source maps

SEO Factors

plymouth-church.net SEO score

71

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

Document doesn't have a <title> element

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

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 Plymouth-church.net 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 Plymouth-church.net 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

plymouth-church.net

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