Tools & Wizards About Us
unto.com screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

unto.com

Humanitarian Aid for People in the Toughest Places on Earth | Unto.com

Page Load Speed

3.7 sec in total

First Response

13 ms

Resources Loaded

3.1 sec

Page Rendered

523 ms

unto.com screenshot

About Website

Visit unto.com now to see the best up-to-date Unto content and also check out these interesting facts you probably never knew about unto.com

Through humanitarian aid, Unto expresses Jesus' kindness to people in tough places by relieving suffering, restoring dignity, and revealing hope.

Visit unto.com

Key Findings

We analyzed Unto.com page load time and found that the first response time was 13 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

unto.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value20.5 s

0/100

25%

SI (Speed Index)

Value20.6 s

0/100

10%

TBT (Total Blocking Time)

Value4,040 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.296

40/100

15%

TTI (Time to Interactive)

Value27.5 s

0/100

10%

Network Requests Diagram

unto.com

13 ms

unto.com

1343 ms

dwt3buv.css

210 ms

premium-addons.css

37 ms

frontend.css

34 ms

Our browser made a total of 134 requests to load all elements on the main page. We found that 74% of them (99 requests) were addressed to the original Unto.com, 4% (6 requests) were made to Googletagmanager.com and 4% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Unto.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 716.7 kB (16%)

Content Size

4.4 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Unto.com main page is 4.4 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. Javascripts take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 149.8 kB

  • Original 182.0 kB
  • After minification 177.4 kB
  • After compression 32.2 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 149.8 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 26.7 kB

  • Original 1.6 MB
  • After minification 1.6 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. Unto images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 502.8 kB

  • Original 2.2 MB
  • After minification 2.2 MB
  • After compression 1.7 MB

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 502.8 kB or 22% of the original size.

CSS Optimization

-9%

Potential reduce by 37.3 kB

  • Original 425.8 kB
  • After minification 425.5 kB
  • After compression 388.5 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. Unto.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 99 (85%)

Requests Now

117

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

unto.com

unto.com

13 ms

unto.com

unto.com

1343 ms

dwt3buv.css

dwt3buv.css

210 ms

premium-addons.css

premium-addons.css

37 ms

frontend.css

frontend.css

34 ms

blocks.style.build.css

blocks.style.build.css

31 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

33 ms

wp-mediaelement.css

wp-mediaelement.css

31 ms

views-frontend.css

views-frontend.css

54 ms

cru-branded-checkout-public.css

cru-branded-checkout-public.css

53 ms

wplc-plugin-public.css

wplc-plugin-public.css

55 ms

all.css

all.css

233 ms

pannellum.css

pannellum.css

54 ms

video-js.css

video-js.css

56 ms

videojs-vr.css

videojs-vr.css

57 ms

owl.carousel.css

owl.carousel.css

63 ms

wpvr-public.css

wpvr-public.css

64 ms

all.min.css

all.min.css

60 ms

v4-shims.min.css

v4-shims.min.css

66 ms

public.css

public.css

72 ms

jet-elements.css

jet-elements.css

85 ms

jet-elements-skin.css

jet-elements-skin.css

75 ms

elementor-icons.css

elementor-icons.css

71 ms

frontend.css

frontend.css

76 ms

swiper.css

swiper.css

69 ms

post-2602.css

post-2602.css

99 ms

frontend.css

frontend.css

118 ms

frontend.css

frontend.css

191 ms

uael-frontend.min.css

uael-frontend.min.css

145 ms

all.min.css

all.min.css

101 ms

v4-shims.css

v4-shims.css

99 ms

global.css

global.css

179 ms

post-359.css

post-359.css

104 ms

post-6644.css

post-6644.css

106 ms

post-10451.css

post-10451.css

107 ms

post-10541.css

post-10541.css

110 ms

general.min.css

general.min.css

108 ms

bones-stylesheet.css

bones-stylesheet.css

111 ms

css

css

95 ms

fontawesome.css

fontawesome.css

130 ms

js

js

186 ms

api.js

api.js

102 ms

solid.css

solid.css

131 ms

animations.min.css

animations.min.css

117 ms

jquery.js

jquery.js

176 ms

jquery-migrate.js

jquery-migrate.js

176 ms

toolset-common-es-frontend.js

toolset-common-es-frontend.js

174 ms

cru-branded-checkout-public.js

cru-branded-checkout-public.js

156 ms

pannellum.js

pannellum.js

158 ms

libpannellum.js

libpannellum.js

157 ms

video.js

video.js

247 ms

videojs-vr.js

videojs-vr.js

202 ms

videojs-pannellum-plugin.js

videojs-pannellum-plugin.js

154 ms

owl.carousel.js

owl.carousel.js

155 ms

jquery.cookie.js

jquery.cookie.js

150 ms

v4-shims.js

v4-shims.js

149 ms

modernizr.custom.min.js

modernizr.custom.min.js

148 ms

mpp-frontend.js

mpp-frontend.js

148 ms

page-scroll-to-id.min.js

page-scroll-to-id.min.js

145 ms

wpvr-public.js

wpvr-public.js

141 ms

wp-polyfill-inert.js

wp-polyfill-inert.js

142 ms

regenerator-runtime.js

regenerator-runtime.js

143 ms

wp-polyfill.js

wp-polyfill.js

121 ms

hooks.js

hooks.js

120 ms

vue.js

vue.js

132 ms

jet-menu-public-scripts.js

jet-menu-public-scripts.js

120 ms

wpfront-scroll-top.js

wpfront-scroll-top.js

113 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

113 ms

general.min.js

general.min.js

113 ms

scripts.js

scripts.js

112 ms

jquery.smartmenus.js

jquery.smartmenus.js

112 ms

frontend-advanced-menu.js

frontend-advanced-menu.js

109 ms

fontawesome-all.min.js

fontawesome-all.min.js

433 ms

TweenMax.js

TweenMax.js

91 ms

waypoints.js

waypoints.js

89 ms

motionpath.js

motionpath.js

89 ms

modal.js

modal.js

85 ms

lottie.js

lottie.js

59 ms

premium-addons.js

premium-addons.js

45 ms

webpack-pro.runtime.js

webpack-pro.runtime.js

31 ms

p.css

p.css

55 ms

webpack.runtime.js

webpack.runtime.js

30 ms

frontend-modules.js

frontend-modules.js

33 ms

i18n.js

i18n.js

31 ms

frontend.js

frontend.js

34 ms

core.js

core.js

34 ms

frontend.js

frontend.js

34 ms

elements-handlers.js

elements-handlers.js

38 ms

jet-elements.js

jet-elements.js

42 ms

widgets-scripts.js

widgets-scripts.js

84 ms

jquery.sticky.js

jquery.sticky.js

44 ms

frontend.js

frontend.js

83 ms

tooltipster.js

tooltipster.js

279 ms

gtm.js

gtm.js

90 ms

ShoeWoman-1.jpg

ShoeWoman-1.jpg

77 ms

ShoeWoman.jpg

ShoeWoman.jpg

79 ms

homevidback.jpg

homevidback.jpg

78 ms

fb_wallpaper_email_masthead-crop.png

fb_wallpaper_email_masthead-crop.png

77 ms

destination

destination

410 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

565 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff

584 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

612 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

731 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

720 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

768 ms

fa-solid-900.woff

fa-solid-900.woff

400 ms

fa-solid-900.woff

fa-solid-900.woff

272 ms

fa-solid-900.woff

fa-solid-900.woff

561 ms

fa-regular-400.woff

fa-regular-400.woff

206 ms

fa-regular-400.woff

fa-regular-400.woff

203 ms

fa-regular-400.woff

fa-regular-400.woff

591 ms

local-ga.js

local-ga.js

490 ms

recaptcha__en.js

recaptcha__en.js

679 ms

Unto_Logo_Cru.png

Unto_Logo_Cru.png

332 ms

Hero-LockupR-with-donate-button.png

Hero-LockupR-with-donate-button.png

356 ms

d

d

273 ms

d

d

301 ms

analytics.js

analytics.js

399 ms

js

js

251 ms

gtm.js

gtm.js

342 ms

264 ms

linkid.js

linkid.js

221 ms

collect

collect

211 ms

collect

collect

283 ms

js

js

78 ms

collect

collect

191 ms

collect

collect

199 ms

collect

collect

184 ms

collect

collect

199 ms

210 ms

ga-audiences

ga-audiences

15 ms

ga-audiences

ga-audiences

22 ms

16 ms

36.png

36.png

10 ms

Accessibility Review

unto.com accessibility score

97

Accessibility Issues

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

unto.com best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

unto.com SEO score

93

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

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

Social Sharing Optimization

unto.com

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