3.4 sec in total
968 ms
1.9 sec
508 ms
Click here to check amazing Potential Church content for United States. Otherwise, check out these important facts you probably never knew about potentialchurch.com
Potential Church, partnering with people to reach their God potential to impact the world for good.
Visit potentialchurch.comWe analyzed Potentialchurch.com page load time and found that the first response time was 968 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
potentialchurch.com performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value7.1 s
5/100
25%
Value16.5 s
0/100
10%
Value140 ms
95/100
30%
Value0.033
100/100
15%
Value19.3 s
2/100
10%
968 ms
20 ms
131 ms
92 ms
127 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 81% of them (91 requests) were addressed to the original Potentialchurch.com, 3% (3 requests) were made to S.gravatar.com and 3% (3 requests) were made to I1.wp.com. The less responsive or slowest element that took the longest time to load (968 ms) belongs to the original domain Potentialchurch.com.
Page size can be reduced by 1.6 MB (40%)
4.0 MB
2.4 MB
In fact, the total size of Potentialchurch.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 1.9 MB which makes up the majority of the site volume.
Potential reduce by 105.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 105.5 kB or 83% of the original size.
Potential reduce by 806 B
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. Potential Church images are well optimized though.
Potential reduce by 950.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 950.3 kB or 71% of the original size.
Potential reduce by 580.7 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. Potentialchurch.com needs all CSS files to be minified and compressed as it can save up to 580.7 kB or 85% of the original size.
Number of requests can be reduced by 93 (87%)
107
14
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Potential 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 75 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
potentialchurch.com
968 ms
webfont.js
20 ms
wp-emoji-release.min.js
131 ms
circularCountdown.css
92 ms
settings.css
127 ms
dynamic-captions.css
92 ms
public-pro.css
93 ms
button.css
109 ms
pikaday.css
135 ms
wpimagehover.css
136 ms
elusive-webfont.css
137 ms
polls-css.css
170 ms
bootstrap.min.css
247 ms
ss-gizmo.css
214 ms
font-awesome.min.css
216 ms
style.css
406 ms
responsive.css
260 ms
jetpack.css
297 ms
hubspot.css
264 ms
jquery.js
295 ms
jquery-migrate.min.js
291 ms
circularCountdown.js
293 ms
jquery.themepunch.plugins.min.js
342 ms
jquery.themepunch.revolution.min.js
370 ms
css
37 ms
public.css
253 ms
core.min.js
148 ms
widget.min.js
145 ms
mouse.min.js
188 ms
accordion.min.js
188 ms
position.min.js
189 ms
menu.min.js
186 ms
autocomplete.min.js
304 ms
slider.min.js
303 ms
tabs.min.js
305 ms
sortable.min.js
303 ms
draggable.min.js
304 ms
droppable.min.js
304 ms
selectable.min.js
305 ms
datepicker.min.js
308 ms
resizable.min.js
307 ms
button.min.js
308 ms
dialog.min.js
307 ms
jquery.form.min.js
308 ms
jquery.color.min.js
311 ms
masonry.min.js
331 ms
jquery.masonry.min.js
332 ms
progressbar.min.js
331 ms
checkout.js
51 ms
devicepx-jetpack.js
9 ms
gprofiles.js
56 ms
js
20 ms
tooltip.min.js
323 ms
effect.min.js
323 ms
e-201611.js
4 ms
effect-blind.min.js
346 ms
effect-bounce.min.js
309 ms
effect-clip.min.js
302 ms
effect-drop.min.js
316 ms
effect-explode.min.js
291 ms
effect-fade.min.js
288 ms
effect-fold.min.js
304 ms
effect-highlight.min.js
302 ms
effect-pulsate.min.js
267 ms
effect-size.min.js
266 ms
effect-scale.min.js
270 ms
effect-shake.min.js
271 ms
effect-slide.min.js
260 ms
effect-transfer.min.js
262 ms
photon.js
267 ms
parsley.min.js
269 ms
public.js
285 ms
WEB-BANNER-1.jpg
40 ms
Egg-A-Palooza.jpg
58 ms
BAPTISM-WEB-BANNER.jpg
37 ms
brian_webbanner.jpg
35 ms
slider_job.jpg
37 ms
moment.min.js
171 ms
working_paralax_icmapus.png
34 ms
pikaday.js
172 ms
pikaday.jquery.js
188 ms
wpimagehover.js
194 ms
jquery.sharrre.min.js
195 ms
polls-js.js
197 ms
wpgroho.js
203 ms
love-it.js
209 ms
jquery.cookie.js
225 ms
bootstrap.min.js
235 ms
jquery-ui-1.10.2.custom.min.js
232 ms
jquery.flexslider-min.js
233 ms
jquery.easing.js
243 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
22 ms
owl.carousel.min.js
245 ms
sntaY1Q8xeij0j8FAJb2VvesZW2xOQ-xsNqO47m55DA.ttf
22 ms
431747.js
66 ms
theme-scripts.js
323 ms
ilightbox.min.js
288 ms
jquery.isotope.min.js
249 ms
imagesloaded.js
251 ms
jquery.infinitescroll.min.js
254 ms
functions.js
241 ms
wp-embed.min.js
266 ms
ss-gizmo.woff
253 ms
fontawesome-webfont.woff
279 ms
FINAL_potentialLOGO.png
279 ms
blank.png
470 ms
hovercard.css
44 ms
services.css
53 ms
timer.png
47 ms
slider-nav.png
48 ms
g.gif
5 ms
__ptq.gif
49 ms
potentialchurch.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
potentialchurch.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
potentialchurch.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Potentialchurch.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 Potentialchurch.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.
potentialchurch.com
Open Graph data is detected on the main page of Potential Church. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: