5.6 sec in total
217 ms
4.5 sec
890 ms
Visit jrs.net now to see the best up-to-date JRS content for Afghanistan and also check out these interesting facts you probably never knew about jrs.net
The Jesuit Refugee Service (JRS) seeks to accompany, serve, and advocate the cause of refugees and other forcibly displaced people.
Visit jrs.netWe analyzed Jrs.net page load time and found that the first response time was 217 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
jrs.net performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value14.9 s
0/100
25%
Value17.4 s
0/100
10%
Value19,740 ms
0/100
30%
Value0.186
65/100
15%
Value29.0 s
0/100
10%
217 ms
1559 ms
123 ms
151 ms
234 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 52% of them (45 requests) were addressed to the original Jrs.net, 8% (7 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Jrs.net.
Page size can be reduced by 145.6 kB (8%)
1.8 MB
1.7 MB
In fact, the total size of Jrs.net main page is 1.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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 87.8 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 87.8 kB or 80% of the original size.
Potential reduce by 34.3 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. JRS images are well optimized though.
Potential reduce by 10.8 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. This website has mostly compressed JavaScripts.
Potential reduce by 12.6 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. Jrs.net needs all CSS files to be minified and compressed as it can save up to 12.6 kB or 20% of the original size.
Number of requests can be reduced by 54 (70%)
77
23
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JRS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
jrs.net
217 ms
1559 ms
css
123 ms
install-popup-button.js
151 ms
style.min.css
234 ms
cookie-law-info-public.css
317 ms
cookie-law-info-gdpr.css
398 ms
styles.css
478 ms
slick.css
405 ms
addtoany.min.css
405 ms
page.js
118 ms
jquery.min.js
116 ms
addtoany.min.js
405 ms
cookie-law-info-public.js
404 ms
modernizr.min.js
522 ms
ofi.min.js
555 ms
slick.js
592 ms
region-map.js
595 ms
longform.js
555 ms
mobile-menu.js
597 ms
scripts.js
599 ms
utm_form-1.1.0.min.js
112 ms
js
145 ms
js
233 ms
hustle-icons.min.css
543 ms
hustle-global.min.css
545 ms
hustle-optin.min.css
621 ms
hustle-inline.min.css
543 ms
css
31 ms
gtm4wp-form-move-tracker.js
627 ms
hustle-ui.min.js
843 ms
underscore.min.js
709 ms
front.min.js
687 ms
eso.e18d3993.js
78 ms
gtm.js
371 ms
ACFQYQWF
371 ms
diffuser.js
212 ms
ac27808c396a961954f613d57.js
546 ms
icon-search-white.svg
202 ms
logo.svg
183 ms
My-project-1-3-2000x0-c-default.jpg
799 ms
49388192778_ceec2fef3b_c-1-250x300-c-default.png
346 ms
BOURJH3-e1540917284461-250x300-c-default.jpg
324 ms
JRS_4927-250x300-c-default.jpg
346 ms
ETH02_20160603_CFUCHS__012-250x300-c-default.jpg
344 ms
PhotoIRQ06-BECE-e1656066373764.jpg
784 ms
MicrosoftTeams-image-8-1600x800-c-default.jpg
1232 ms
DSC_0991-scaled-e1626699814336.jpg
794 ms
UA_2022_05_Lviv_Sergi_Camara_Tetyana-8-e1655456073681-600x250-c-default.jpg
525 ms
IMG_7790--scaled-e1654788661854-600x250-c-default.jpg
514 ms
TCD01_2022_0523_Credits-to-Irene-Galera-20-2000x0-c-default-1-e1659542869350-2000x0-c-default.jpeg
868 ms
logo-white.svg
773 ms
facebook-official-white.svg
744 ms
twitter-white.svg
725 ms
flickr-white.svg
726 ms
instagram-white.svg
726 ms
linkedin-white.svg
912 ms
youtube-white.svg
910 ms
analytics.js
594 ms
conversion_async.js
581 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff
571 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff
682 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff
685 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff
690 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff
685 ms
prism.app-us1.com
577 ms
js
355 ms
conversion_async.js
602 ms
prism.app-us1.com
452 ms
icons.30.svg.js
147 ms
sm.23.html
286 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
307 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
283 ms
collect
303 ms
js
232 ms
347 ms
wp-controller.js
269 ms
collect
47 ms
collect
35 ms
collect
67 ms
34 ms
collect
71 ms
51 ms
51 ms
ga-audiences
48 ms
ga-audiences
17 ms
jrs.net accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
jrs.net 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
jrs.net 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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jrs.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Jrs.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.
jrs.net
Open Graph data is detected on the main page of JRS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: