3.7 sec in total
183 ms
3.3 sec
269 ms
Click here to check amazing Barabbas content. Otherwise, check out these important facts you probably never knew about barabbas.com
Barabbas Road Church is a Bible-teaching church in Miramar, San Diego. Join us Sundays at 10am at 7340 Miramar Rd for verse-by-verse expository preaching, Life Groups, and gospel community.
Visit barabbas.comWe analyzed Barabbas.com page load time and found that the first response time was 183 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
barabbas.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value17.5 s
0/100
25%
Value9.3 s
13/100
10%
Value310 ms
77/100
30%
Value0.012
100/100
15%
Value15.1 s
7/100
10%
183 ms
616 ms
32 ms
278 ms
181 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 78% of them (43 requests) were addressed to the original Barabbas.com, 7% (4 requests) were made to Fonts.googleapis.com and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (616 ms) belongs to the original domain Barabbas.com.
Page size can be reduced by 259.4 kB (10%)
2.5 MB
2.2 MB
In fact, the total size of Barabbas.com main page is 2.5 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. 60% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 51.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 51.5 kB or 83% of the original size.
Potential reduce by 61.1 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. Barabbas images are well optimized though.
Potential reduce by 76.4 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 76.4 kB or 30% of the original size.
Potential reduce by 70.4 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. Barabbas.com needs all CSS files to be minified and compressed as it can save up to 70.4 kB or 45% of the original size.
Number of requests can be reduced by 36 (80%)
45
9
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Barabbas. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
barabbas.com
183 ms
www.barabbas.com
616 ms
css
32 ms
pe_screen.php
278 ms
site.min.css
181 ms
grid.css
185 ms
base.css
184 ms
layout.css
250 ms
shortcodes.css
309 ms
magnific-popup.css
243 ms
mediaelementplayer.css
255 ms
enfold_child.css
317 ms
custom.css
304 ms
style.css
315 ms
css
57 ms
eventon_styles.css
377 ms
font-awesome.css
338 ms
dv_styles.css
365 ms
fc_styles.css
373 ms
jquery.js
429 ms
jquery-migrate.min.js
373 ms
prayerwall.js
401 ms
avia-compat.js
440 ms
wp-emoji-release.min.js
397 ms
eventon_dynamic_styles.css
394 ms
avia.js
456 ms
shortcodes.js
510 ms
jquery.magnific-popup.min.js
455 ms
mediaelement-and-player.min.js
514 ms
wp-mediaelement.js
455 ms
comment-reply.min.js
455 ms
jquery.mousewheel.min.js
525 ms
dv_script.js
523 ms
css
20 ms
css
25 ms
fbevents.js
84 ms
analytics.js
83 ms
logolock3-300x128.png
138 ms
brchome.png
470 ms
Morning-Devotions-Christian-Stock-Image-1030x687.jpg
251 ms
charlie.jpg
249 ms
pastor.png
350 ms
missions1.jpg
229 ms
RobotoCondensed-Light.ttf
247 ms
RobotoCondensed-Regular.ttf
253 ms
BebasNeueRegular.otf
297 ms
entypo-fontello.woff
254 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff
50 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
55 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff
56 ms
collect
21 ms
js
94 ms
logolock3-300x128.png
234 ms
RefTagger.js
350 ms
print.css
65 ms
barabbas.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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
barabbas.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
barabbas.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
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
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 Barabbas.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 Barabbas.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.
barabbas.com
Open Graph data is detected on the main page of Barabbas. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: