Tools & Wizards About Us
back2back.org screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

back2back.org

Back2Back Ministries – A Voice for Orphaned and Vulnerable Children

Page Load Speed

2.1 sec in total

First Response

52 ms

Resources Loaded

1.6 sec

Page Rendered

443 ms

back2back.org screenshot

About Website

Welcome to back2back.org homepage info - get ready to check Back2 Back best content for United States right away, or after learning these important things about back2back.org

Back2Back provides comprehensive care to vulnerable children and families across the world.

Visit back2back.org

Key Findings

We analyzed Back2back.org page load time and found that the first response time was 52 ms and then it took 2 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

back2back.org performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value5.3 s

57/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

back2back.org

52 ms

back2back.org

145 ms

sax8wfe.css

306 ms

gravity-forms-theme-reset.min.css

35 ms

gravity-forms-theme-foundation.min.css

37 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 86% of them (99 requests) were addressed to the original Back2back.org, 8% (9 requests) were made to Use.typekit.net and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (625 ms) relates to the external source Docs.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 824.4 kB (49%)

Content Size

1.7 MB

After Optimization

843.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Back2back.org main page is 1.7 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. Only a small number of websites need less resources to load. HTML takes 906.5 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 809.1 kB

  • Original 906.5 kB
  • After minification 892.1 kB
  • After compression 97.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 809.1 kB or 89% of the original size.

Image Optimization

-20%

Potential reduce by 12.9 kB

  • Original 64.6 kB
  • After minification 51.7 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. Obviously, Back2 Back needs image optimization as it can save up to 12.9 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 1.4 kB

  • Original 517.3 kB
  • After minification 517.3 kB
  • After compression 516.0 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

-1%

Potential reduce by 918 B

  • Original 179.6 kB
  • After minification 179.6 kB
  • After compression 178.7 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. Back2back.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 77 (73%)

Requests Now

105

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

back2back.org

back2back.org

52 ms

back2back.org

back2back.org

145 ms

sax8wfe.css

sax8wfe.css

306 ms

gravity-forms-theme-reset.min.css

gravity-forms-theme-reset.min.css

35 ms

gravity-forms-theme-foundation.min.css

gravity-forms-theme-foundation.min.css

37 ms

gravity-forms-theme-framework.min.css

gravity-forms-theme-framework.min.css

42 ms

dashicons.min.css

dashicons.min.css

36 ms

uploader.style.build.css

uploader.style.build.css

39 ms

formreset.min.css

formreset.min.css

49 ms

formsmain.min.css

formsmain.min.css

55 ms

readyclass.min.css

readyclass.min.css

53 ms

browsers.min.css

browsers.min.css

52 ms

theme.min.css

theme.min.css

59 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

62 ms

general.min.css

general.min.css

72 ms

eael-834.css

eael-834.css

67 ms

eael-618.css

eael-618.css

74 ms

eael-558.css

eael-558.css

71 ms

eael-508.css

eael-508.css

177 ms

eael-467.css

eael-467.css

77 ms

style.min.css

style.min.css

80 ms

header-footer.min.css

header-footer.min.css

88 ms

post-17.css

post-17.css

84 ms

eael-27.css

eael-27.css

86 ms

swiper.min.css

swiper.min.css

91 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

94 ms

post-27.css

post-27.css

101 ms

post-637.css

post-637.css

99 ms

post-709.css

post-709.css

105 ms

post-834.css

post-834.css

108 ms

post-618.css

post-618.css

107 ms

post-558.css

post-558.css

122 ms

post-508.css

post-508.css

120 ms

post-467.css

post-467.css

120 ms

style_login_widget.min.css

style_login_widget.min.css

126 ms

jquery.min.js

jquery.min.js

129 ms

jquery-migrate.min.js

jquery-migrate.min.js

136 ms

api.js

api.js

38 ms

custom-pro-widget-nav-menu.min.css

custom-pro-widget-nav-menu.min.css

117 ms

fontawesome-all.min.css

fontawesome-all.min.css

119 ms

fontawesome-v4-shims.min.css

fontawesome-v4-shims.min.css

117 ms

widget-loop-builder.min.css

widget-loop-builder.min.css

112 ms

jquery.json.min.js

jquery.json.min.js

118 ms

gravityforms.min.js

gravityforms.min.js

114 ms

conditional_logic.min.js

conditional_logic.min.js

119 ms

utils.min.js

utils.min.js

121 ms

page_conditional_logic.min.js

page_conditional_logic.min.js

123 ms

filepondV1.build.js

filepondV1.build.js

135 ms

image-hopper.js

image-hopper.js

132 ms

script.min.js

script.min.js

123 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

116 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

121 ms

wp-polyfill.min.js

wp-polyfill.min.js

127 ms

dom-ready.min.js

dom-ready.min.js

128 ms

hooks.min.js

hooks.min.js

122 ms

i18n.min.js

i18n.min.js

147 ms

a11y.min.js

a11y.min.js

129 ms

core.min.js

core.min.js

119 ms

datepicker.min.js

datepicker.min.js

125 ms

datepicker-legacy.min.js

datepicker-legacy.min.js

126 ms

datepicker.min.js

datepicker.min.js

127 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

127 ms

vendor-theme.min.js

vendor-theme.min.js

127 ms

scripts-theme.min.js

scripts-theme.min.js

130 ms

jquery.textareaCounter.plugin.min.js

jquery.textareaCounter.plugin.min.js

132 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

123 ms

general.min.js

general.min.js

129 ms

hello-frontend.min.js

hello-frontend.min.js

116 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

121 ms

menu.js

menu.js

121 ms

imagesloaded.min.js

imagesloaded.min.js

135 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

118 ms

webpack.runtime.min.js

webpack.runtime.min.js

127 ms

frontend-modules.min.js

frontend-modules.min.js

122 ms

frontend.min.js

frontend.min.js

126 ms

waypoints.min.js

waypoints.min.js

295 ms

frontend.min.js

frontend.min.js

122 ms

elements-handlers.min.js

elements-handlers.min.js

123 ms

p.css

p.css

18 ms

Back2Back-Logo-Horizontal.svg

Back2Back-Logo-Horizontal.svg

43 ms

Get-Involved_Hover_blue.svg

Get-Involved_Hover_blue.svg

41 ms

Logo_R.svg

Logo_R.svg

44 ms

L-Imahe-1.webp

L-Imahe-1.webp

48 ms

Every-Story-Matters.webp

Every-Story-Matters.webp

40 ms

Learn-More_Hover.svg

Learn-More_Hover.svg

44 ms

Accordian_image_hp.webp

Accordian_image_hp.webp

51 ms

Map_white.svg

Map_white.svg

104 ms

HOPE-DOESNT-STAND-STILL.svg

HOPE-DOESNT-STAND-STILL.svg

49 ms

Cancun_.webp

Cancun_.webp

50 ms

Cincinnati_.webp

Cincinnati_.webp

75 ms

Mazatlan_.webp

Mazatlan_.webp

74 ms

Hyderabad.webp

Hyderabad.webp

76 ms

Jos-1.webp

Jos-1.webp

75 ms

Linares.webp

Linares.webp

75 ms

Monterrey_.webp

Monterrey_.webp

168 ms

Port-au-Prince.webp

Port-au-Prince.webp

168 ms

Santiago.webp

Santiago.webp

167 ms

Arrow_vector.svg

Arrow_vector.svg

168 ms

ARROW_mobile.svg

ARROW_mobile.svg

168 ms

Footer-Logo.svg

Footer-Logo.svg

216 ms

Child-Code-Image.png

Child-Code-Image.png

218 ms

d

d

117 ms

d

d

152 ms

d

d

151 ms

d

d

152 ms

d

d

191 ms

d

d

166 ms

d

d

152 ms

d

d

166 ms

pub

pub

625 ms

recaptcha__en.js

recaptcha__en.js

81 ms

datepicker.svg

datepicker.svg

39 ms

css

css

39 ms

AD_4nXd-OInPEM5rqWNQoigK4EcCVRr0kR7dQmSJdw1jii_pkj67e9xLgvB5KPTZH9LwM0ppD9u7ZHxnJvL6i5GwILVU-oHM5zsKEqziieLcx70m9-Qq9rVhjB9NgbhbxSFDg_Y0YVmA9BFIpojj_FBBDg

AD_4nXd-OInPEM5rqWNQoigK4EcCVRr0kR7dQmSJdw1jii_pkj67e9xLgvB5KPTZH9LwM0ppD9u7ZHxnJvL6i5GwILVU-oHM5zsKEqziieLcx70m9-Qq9rVhjB9NgbhbxSFDg_Y0YVmA9BFIpojj_FBBDg

316 ms

font

font

18 ms

Accessibility Review

back2back.org accessibility score

95

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

back2back.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

back2back.org SEO score

99

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

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

back2back.org

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