3.9 sec in total
24 ms
3.2 sec
677 ms
Click here to check amazing Savory content for Egypt. Otherwise, check out these important facts you probably never knew about savory.global
A global nonprofit regenerating the world's grasslands through properly-managed livestock and Holistic Management. 75M+ acres regenerated since 2009.
Visit savory.globalWe analyzed Savory.global page load time and found that the first response time was 24 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
savory.global performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value5.5 s
19/100
25%
Value10.5 s
7/100
10%
Value2,570 ms
4/100
30%
Value0.001
100/100
15%
Value18.7 s
3/100
10%
24 ms
1998 ms
36 ms
32 ms
31 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 87% of them (71 requests) were addressed to the original Savory.global, 2% (2 requests) were made to Benderlidze.github.io and 2% (2 requests) were made to Api.mapbox.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Savory.global.
Page size can be reduced by 743.5 kB (21%)
3.5 MB
2.8 MB
In fact, the total size of Savory.global 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. 70% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 614.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 614.8 kB or 87% of the original size.
Potential reduce by 128.6 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. Savory images are well optimized though.
Potential reduce by 21 B
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.
Number of requests can be reduced by 52 (71%)
73
21
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Savory. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
savory.global
24 ms
savory.global
1998 ms
mediaelementplayer-legacy.min.css
36 ms
wp-mediaelement.min.css
32 ms
frontend.css
31 ms
style.min.css
34 ms
theme.min.css
29 ms
header-footer.min.css
35 ms
select.css
36 ms
main.css
36 ms
wysiwyg.css
43 ms
switcher.css
44 ms
jet-elements.css
56 ms
jet-elements-skin.css
44 ms
frontend-lite.min.css
50 ms
swiper.min.css
30 ms
frontend-lite.min.css
38 ms
search-forms.css
39 ms
chosen.min.css
39 ms
jet-search.css
47 ms
jquery.min.js
41 ms
jquery-migrate.min.js
40 ms
imagesloaded.min.js
62 ms
widget-mega-menu.min.css
39 ms
widget-icon-box.min.css
44 ms
widget-icon-list.min.css
136 ms
embed.php
330 ms
animations.min.css
158 ms
slider-pro.min.css
155 ms
underscore.min.js
158 ms
wp-util.min.js
158 ms
chosen.jquery.min.js
158 ms
jet-plugins.js
158 ms
jet-search.js
157 ms
hello-frontend.min.js
173 ms
e-202434.js
30 ms
jquery.sticky.min.js
165 ms
jquery-numerator.min.js
164 ms
jquery.sliderPro.min.js
170 ms
webpack-pro.runtime.min.js
169 ms
webpack.runtime.min.js
165 ms
frontend-modules.min.js
174 ms
hooks.min.js
172 ms
i18n.min.js
174 ms
frontend.min.js
183 ms
waypoints.min.js
183 ms
core.min.js
182 ms
frontend.min.js
180 ms
elements-handlers.min.js
183 ms
jet-elements.min.js
182 ms
gtm.js
239 ms
375584517452202564.js
1124 ms
index-v2.html
110 ms
9257608
248 ms
Savory-logo_Savory-logo-white-300x108.png
77 ms
regenerating-the-worlds-grasslands.webp
81 ms
HM-logo-web.png
81 ms
%C2%A9Mann__DSC3248.jpg
164 ms
Kroon-boundary-South-Africa.jpg
195 ms
AMiller-Savory-LTM-2021-44-e1676770479157-1024x609.jpg
163 ms
AMiller-Savory-LTM-2021-69-768x512-1.jpeg
164 ms
EOV-Seal_2024-black-1024x808.png
164 ms
L2M-a-savory-program-1-e1690311651300-1024x645.png
154 ms
Savory-Foundation-white.png
191 ms
Hub-Gathering-group-shot.jpg
223 ms
20210607-DSC06375-scaled-e1688057171263-768x447.jpg
194 ms
6a8a0725_43245998140_o-1-scaled-e1678301220779-1024x608.jpg
186 ms
Screen-Shot-2021-12-01-at-11.31.20-AM-1024x679.png
253 ms
Ratings_BLK_4star-300x300.png
214 ms
1ftp_EnvironmentalPartner_Vertical_White-230x300.png
212 ms
mapbox-gl.css
100 ms
mapbox-gl.js
139 ms
d3.v7.min.js
186 ms
turf.min.js
141 ms
NunitoSans-SemiBold.woff
98 ms
NunitoSans-Regular.woff
100 ms
NunitoSans-Light.woff
136 ms
alegreya-variablefont_wght-webfont.woff
135 ms
Alegreya-VariableFont_wght.woff
136 ms
Alegreya-SemiBold.woff
139 ms
Alegreya-Italic-VariableFont_wght.woff
137 ms
Spinner.svg
71 ms
savory.global accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
savory.global best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
savory.global 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
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Savory.global 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 Savory.global 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.
savory.global
Open Graph data is detected on the main page of Savory. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: