Tools & Wizards About Us
jrs.net screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

jrs.net

Jesuit Refugee Service (JRS) - Accompany, Serve, Advocate

Page Load Speed

6.9 sec in total

First Response

176 ms

Resources Loaded

6 sec

Page Rendered

710 ms

jrs.net screenshot

About Website

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

Key Findings

We analyzed Jrs.net page load time and found that the first response time was 176 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

jrs.net performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value17.6 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value1,140 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.086

93/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

jrs.net

176 ms

2965 ms

css

65 ms

install-popup-button.js

100 ms

script.js

62 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 73% of them (36 requests) were addressed to the original Jrs.net, 4% (2 requests) were made to Googletagmanager.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Jrs.net.

Page Optimization Overview & Recommendations

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

Content Size

3.5 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jrs.net main page is 3.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. 45% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 51.0 kB

  • Original 63.8 kB
  • After minification 55.7 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 8.1 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 51.0 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 244.6 kB

  • Original 3.3 MB
  • After minification 3.0 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. JRS images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 23.2 kB

  • Original 137.7 kB
  • After minification 137.3 kB
  • After compression 114.5 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 23.2 kB or 17% of the original size.

CSS Optimization

-40%

Potential reduce by 24.0 kB

  • Original 60.5 kB
  • After minification 60.5 kB
  • After compression 36.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. Jrs.net needs all CSS files to be minified and compressed as it can save up to 24.0 kB or 40% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (62%)

Requests Now

45

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 45 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 20 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

jrs.net

jrs.net

176 ms

2965 ms

css

css

65 ms

install-popup-button.js

install-popup-button.js

100 ms

script.js

script.js

62 ms

style.min.css

style.min.css

141 ms

styles.css

styles.css

322 ms

slick.css

slick.css

334 ms

addtoany.min.css

addtoany.min.css

335 ms

page.js

page.js

98 ms

jquery.min.js

jquery.min.js

180 ms

addtoany.min.js

addtoany.min.js

332 ms

modernizr.min.js

modernizr.min.js

357 ms

ofi.min.js

ofi.min.js

356 ms

slick.js

slick.js

476 ms

region-map.js

region-map.js

417 ms

longform.js

longform.js

417 ms

mobile-menu.js

mobile-menu.js

423 ms

scripts.js

scripts.js

425 ms

jquery.bind-first-0.2.3.min.js

jquery.bind-first-0.2.3.min.js

425 ms

js.cookie-2.1.3.min.js

js.cookie-2.1.3.min.js

544 ms

public.js

public.js

700 ms

utm_form-1.1.0.min.js

utm_form-1.1.0.min.js

92 ms

js

js

94 ms

js

js

111 ms

embed.php

embed.php

254 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

542 ms

log

log

456 ms

icon-search-white.svg

icon-search-white.svg

145 ms

logo.svg

logo.svg

143 ms

Untitled-design-1-2000x0-c-default.png

Untitled-design-1-2000x0-c-default.png

736 ms

49388192778_ceec2fef3b_c-1-250x300-c-default.png

49388192778_ceec2fef3b_c-1-250x300-c-default.png

308 ms

BOURJH3-e1540917284461-250x300-c-default.jpg

BOURJH3-e1540917284461-250x300-c-default.jpg

146 ms

JRS_4927-250x300-c-default.jpg

JRS_4927-250x300-c-default.jpg

266 ms

ETH02_20160603_CFUCHS__012-250x300-c-default.jpg

ETH02_20160603_CFUCHS__012-250x300-c-default.jpg

266 ms

JRS-GRF-2023-1-e1708620890483.jpeg

JRS-GRF-2023-1-e1708620890483.jpeg

468 ms

Landscape_Images-with-outline.png

Landscape_Images-with-outline.png

829 ms

406664238_651796823802941_3836551794143615826_n-1-1600x800-c-default.jpg

406664238_651796823802941_3836551794143615826_n-1-1600x800-c-default.jpg

378 ms

TCD01_2022_0523_Credits-to-Irene-Galera-20-2000x0-c-default-1-e1659542869350-2000x0-c-default.jpeg

TCD01_2022_0523_Credits-to-Irene-Galera-20-2000x0-c-default-1-e1659542869350-2000x0-c-default.jpeg

629 ms

logo-white.svg

logo-white.svg

391 ms

133 ms

font

font

120 ms

facebook-official-white.svg

facebook-official-white.svg

250 ms

twitter-white.svg

twitter-white.svg

263 ms

flickr-white.svg

flickr-white.svg

331 ms

instagram-white.svg

instagram-white.svg

345 ms

linkedin-white.svg

linkedin-white.svg

346 ms

youtube-white.svg

youtube-white.svg

416 ms

49 ms

Accessibility Review

jrs.net accessibility score

93

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

<frame> or <iframe> elements do not have a title

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

jrs.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

jrs.net SEO score

74

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: