Tools & Wizards About Us
trafficking.net screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

trafficking.net

International Justice Mission | End Modern Slavery for Good

Page Load Speed

2.1 sec in total

First Response

18 ms

Resources Loaded

1.7 sec

Page Rendered

378 ms

trafficking.net screenshot

About Website

Visit trafficking.net now to see the best up-to-date Trafficking content and also check out these interesting facts you probably never knew about trafficking.net

IJM is a global organization that protects people in poverty from human trafficking, modern-day slavery, violence and police abuse of power.

Visit trafficking.net

Key Findings

We analyzed Trafficking.net page load time and found that the first response time was 18 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

trafficking.net performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value1,790 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

trafficking.net

18 ms

www.ijm.org

542 ms

all.css

39 ms

js

172 ms

cookieconsent.min.css

88 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Trafficking.net, 33% (16 requests) were made to Ijm.org and 25% (12 requests) were made to Ijmstoragelive.blob.core.windows.net. The less responsive or slowest element that took the longest time to load (542 ms) relates to the external source Ijm.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 119.3 kB (12%)

Content Size

1.0 MB

After Optimization

910.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Trafficking.net main page is 1.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. 70% of websites need less resources to load. Images take 475.3 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 113.5 kB

  • Original 162.0 kB
  • After minification 161.8 kB
  • After compression 48.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 113.5 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 2.1 kB

  • Original 475.3 kB
  • After minification 473.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. Trafficking images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.7 kB

  • Original 323.3 kB
  • After minification 322.7 kB
  • After compression 319.7 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.

CSS Optimization

-0%

Potential reduce by 23 B

  • Original 69.0 kB
  • After minification 69.0 kB
  • After compression 69.0 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. Trafficking.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 17 (44%)

Requests Now

39

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Trafficking. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

trafficking.net

trafficking.net

18 ms

www.ijm.org

www.ijm.org

542 ms

all.css

all.css

39 ms

js

js

172 ms

cookieconsent.min.css

cookieconsent.min.css

88 ms

donation-form.js

donation-form.js

170 ms

api.js

api.js

184 ms

countdown.js

countdown.js

168 ms

home.js

home.js

166 ms

plugin.js

plugin.js

164 ms

plugin.css

plugin.css

165 ms

cookieconsent.min.js

cookieconsent.min.js

82 ms

gtm.js

gtm.js

138 ms

refresh-tokens

refresh-tokens

444 ms

web2-home-hero-2.jpg

web2-home-hero-2.jpg

216 ms

23mar.jpg

23mar.jpg

425 ms

Icon_Strengthen_Justice_Systems.svg

Icon_Strengthen_Justice_Systems.svg

427 ms

Icon_Rescue_restore.svg

Icon_Rescue_restore.svg

471 ms

Icon_Bring_Criminal_To_Justice.svg

Icon_Bring_Criminal_To_Justice.svg

426 ms

Icon_Scale_Demand_For_Protection.svg

Icon_Scale_Demand_For_Protection.svg

473 ms

2022-convene__card-1-rescue-victims_2022-04-28-181353_ixtf_2022-05-31-160340_gqum.jpg

2022-convene__card-1-rescue-victims_2022-04-28-181353_ixtf_2022-05-31-160340_gqum.jpg

514 ms

freedom-partner-blue.png

freedom-partner-blue.png

471 ms

web2_homepage-engage.jpg

web2_homepage-engage.jpg

518 ms

DAF-Direct.jpg

DAF-Direct.jpg

474 ms

giving-confidence.jpg

giving-confidence.jpg

516 ms

reader-medium-webfont.woff

reader-medium-webfont.woff

405 ms

reader-webfont.woff

reader-webfont.woff

405 ms

reader-bold-webfont.woff

reader-bold-webfont.woff

405 ms

reader-black-webfont.woff

reader-black-webfont.woff

404 ms

recaptcha__en.js

recaptcha__en.js

531 ms

bat.js

bat.js

206 ms

insight.min.js

insight.min.js

260 ms

iframe_api

iframe_api

216 ms

c.min.js

c.min.js

134 ms

boomerang.min.js

boomerang.min.js

213 ms

up_loader.1.1.0.js

up_loader.1.1.0.js

133 ms

reader-italic-webfont.woff

reader-italic-webfont.woff

75 ms

reader-mediumitalic-webfont.woff

reader-mediumitalic-webfont.woff

76 ms

reader-bolditalic-webfont.woff

reader-bolditalic-webfont.woff

77 ms

analytics.js

analytics.js

117 ms

118 ms

collect

collect

63 ms

www-widgetapi.js

www-widgetapi.js

16 ms

collect

collect

35 ms

ga-audiences

ga-audiences

24 ms

js

js

29 ms

iframe

iframe

9 ms

img

img

31 ms

Accessibility Review

trafficking.net accessibility score

78

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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.

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

trafficking.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

trafficking.net SEO score

92

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

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trafficking.net 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 Trafficking.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

trafficking.net

Open Graph data is detected on the main page of Trafficking. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: