4.8 sec in total
824 ms
3.8 sec
202 ms
Click here to check amazing Landmine content. Otherwise, check out these important facts you probably never knew about landmine.org
Since 1996 the humanitarian organization People against Landmines (Menschen gegen Minen) is working on demining projects.
Visit landmine.orgWe analyzed Landmine.org page load time and found that the first response time was 824 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
landmine.org performance score
name
value
score
weighting
Value12.1 s
0/100
10%
Value18.0 s
0/100
25%
Value14.9 s
1/100
10%
Value780 ms
38/100
30%
Value1.134
1/100
15%
Value19.3 s
2/100
10%
824 ms
222 ms
223 ms
219 ms
343 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 85% of them (63 requests) were addressed to the original Landmine.org, 4% (3 requests) were made to Cdnjs.cloudflare.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Landmine.org.
Page size can be reduced by 940.9 kB (43%)
2.2 MB
1.2 MB
In fact, the total size of Landmine.org main page is 2.2 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. 60% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 44.4 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 44.4 kB or 79% of the original size.
Potential reduce by 17.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. Landmine images are well optimized though.
Potential reduce by 737.8 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 737.8 kB or 70% of the original size.
Potential reduce by 141.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. Landmine.org needs all CSS files to be minified and compressed as it can save up to 141.0 kB or 85% of the original size.
Number of requests can be reduced by 39 (56%)
70
31
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Landmine. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
www.landmine.org
824 ms
jcemediabox.css
222 ms
style.css
223 ms
gstyle.css
219 ms
layerslider.css
343 ms
css
16 ms
djmegamenu.css
347 ms
animate.compat.min.css
30 ms
offcanvas.min.css
315 ms
djmobilemenu.css
342 ms
font-awesome.min.css
37 ms
template.css
334 ms
greensock.js
737 ms
mootools-core.js
625 ms
core.js
440 ms
mootools-more.js
1090 ms
jquery.min.js
770 ms
jquery-noconflict.js
459 ms
jquery-migrate.min.js
547 ms
caption.js
571 ms
maximenuckmobile.js
664 ms
jcemediabox.js
902 ms
results.js
732 ms
popuphighslide-with-html.js
874 ms
layerslider.js
1049 ms
layerslider.transitions.js
844 ms
jquery.djmegamenu.min.js
879 ms
jquery.djmobilemenu.min.js
951 ms
system.css
983 ms
general.css
991 ms
template.css
1145 ms
seb.css
1056 ms
template.responsive.css
1144 ms
css
22 ms
jquery.js
1208 ms
script.js
1154 ms
script.responsive.js
1161 ms
system.css
114 ms
de.gif
138 ms
en.gif
137 ms
Landminenproblem.jpg
351 ms
mine-clearance.jpg
318 ms
Kuando-Kubango.jpg
454 ms
Aufklaerung.jpg
338 ms
angola-overview.jpg
247 ms
Malanje-Intro.jpg
247 ms
KK-Intro.jpg
347 ms
krieg-und-minen-in-angola-th.jpg
357 ms
Funding-Intro.jpg
425 ms
landminen.jpg
546 ms
Haller-Da-Silva2.jpg
465 ms
eu.png
463 ms
ge.png
467 ms
usa.png
529 ms
nl.png
561 ms
it.png
573 ms
ja.png
569 ms
analytics.js
14 ms
page.jpg
580 ms
header.jpg
634 ms
line.gif
637 ms
fontawesome-webfont.woff
34 ms
collect
96 ms
0ybgGDoxxrvAnPhYGzMlQLzuMasz6Df2MHGeHmmZ.ttf
80 ms
skin.css
573 ms
popup.html
575 ms
tooltip.html
581 ms
all.js
14 ms
footer.png
563 ms
all.js
5 ms
66 ms
rounded-black.png
130 ms
zoomout.cur
122 ms
loader.white.gif
117 ms
landmine.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
landmine.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
landmine.org 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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Landmine.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 Landmine.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.
landmine.org
Open Graph description is not detected on the main page of Landmine. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: