8.9 sec in total
372 ms
8.2 sec
305 ms
Click here to check amazing Fpchurch content. Otherwise, check out these important facts you probably never knew about fpchurch.com
First Presbyterian of Trenton is a Downriver church committed to glorifying God by making, maturing, and multiplying disciples. We'd love for you to join us!
Visit fpchurch.comWe analyzed Fpchurch.com page load time and found that the first response time was 372 ms and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fpchurch.com performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value18.2 s
0/100
25%
Value10.0 s
9/100
10%
Value1,320 ms
17/100
30%
Value0.001
100/100
15%
Value19.1 s
3/100
10%
372 ms
243 ms
256 ms
334 ms
260 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fpchurch.com, 75% (69 requests) were made to Fpchurch.tv and 10% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5 sec) relates to the external source Fpchurch.tv.
Page size can be reduced by 1.3 MB (12%)
10.8 MB
9.5 MB
In fact, the total size of Fpchurch.com main page is 10.8 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. 65% of websites need less resources to load. Images take 9.2 MB which makes up the majority of the site volume.
Potential reduce by 60.3 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 60.3 kB or 83% of the original size.
Potential reduce by 45.4 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. Fpchurch images are well optimized though.
Potential reduce by 642.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 642.9 kB or 68% of the original size.
Potential reduce by 502.9 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. Fpchurch.com needs all CSS files to be minified and compressed as it can save up to 502.9 kB or 86% of the original size.
Number of requests can be reduced by 62 (78%)
79
17
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fpchurch. 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 27 to 1 for CSS and as a result speed up the page load time.
fpchurch.com
372 ms
fpchurch.tv
243 ms
wp-emoji-release.min.js
256 ms
imgmap_style.css
334 ms
styles.css
260 ms
layerslider.css
261 ms
css
23 ms
styles.css
346 ms
font-awesome.min.css
268 ms
settings.css
410 ms
captions.php
3413 ms
jquery.tippy.css
385 ms
checkbox.min.css
393 ms
css
38 ms
bootstrap.min.css
533 ms
style.css
431 ms
custom.css.php
4708 ms
css
42 ms
eventon_styles.css
625 ms
font-awesome.css
645 ms
form.min.css
659 ms
fc_styles.css
667 ms
jetpack.css
767 ms
esv.css
762 ms
jquery.js
939 ms
jquery-migrate.min.js
810 ms
utils.min.js
850 ms
jquery.imagemapster.min.js
878 ms
imagemapper_script.js
905 ms
greensock.js
1045 ms
layerslider.kreaturamedia.jquery.js
1072 ms
layerslider.transitions.js
1023 ms
front.js
1044 ms
jquery.themepunch.plugins.min.js
1207 ms
jquery.themepunch.revolution.min.js
1235 ms
jquery.tippy.js
1134 ms
modernizr.js
1162 ms
eventon_dynamic_styles.css
1229 ms
core.min.js
1264 ms
widget.min.js
1294 ms
devicepx-jetpack.js
4 ms
gprofiles.js
53 ms
js
25 ms
e-201611.js
4 ms
mouse.min.js
1324 ms
resizable.min.js
1078 ms
draggable.min.js
1113 ms
button.min.js
1154 ms
position.min.js
1162 ms
dialog.min.js
1155 ms
editor.min.js
1188 ms
jquery.form.min.js
1146 ms
scripts.js
1150 ms
wpgroho.js
1518 ms
style.css
1658 ms
color.css.php
4081 ms
custom-fonts.css.php
4975 ms
bootstrap.min.js
1386 ms
isotope.js
1493 ms
plugins.js
1861 ms
comment-reply.min.js
1493 ms
wp-embed.min.js
1579 ms
main.js
1636 ms
ga.js
103 ms
FP_50.png
144 ms
FP_160.png
131 ms
transparent.png
133 ms
risen-square.jpg
1270 ms
Goal-sports-header.jpg
1848 ms
deep-sea.jpg
1022 ms
mobile1.png
830 ms
the-promise-square-150x150.jpg
762 ms
trenton.jpg
890 ms
__utm.gif
83 ms
downriver-smaller.jpg
862 ms
JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff
37 ms
1ImRNPx4870-D9a1EBUdPBsxEYwM7FgeyaSgU71cLG0.woff
67 ms
PKCRbVvRfd5n7BTjtGiFZBsxEYwM7FgeyaSgU71cLG0.woff
69 ms
xkvoNo9fC8O2RDydKj12bxsxEYwM7FgeyaSgU71cLG0.woff
69 ms
CcKI4k9un7TZVWzRVT-T8xsxEYwM7FgeyaSgU71cLG0.woff
68 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
67 ms
-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff
68 ms
8KhZd3VQBtXTAznvKjw-kxsxEYwM7FgeyaSgU71cLG0.woff
67 ms
RJMlAoFXXQEzZoMSUteGWD8E0i7KZn-EPnyo3HZu7kw.woff
68 ms
Icons.woff
900 ms
collect
668 ms
hovercard.css
414 ms
services.css
414 ms
timer.png
223 ms
shadow2.png
291 ms
menu-mobile.png
334 ms
g.gif
64 ms
fpchurch.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
fpchurch.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
fpchurch.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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fpchurch.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 Fpchurch.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.
fpchurch.com
Open Graph data is detected on the main page of Fpchurch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: