3 sec in total
726 ms
2.1 sec
163 ms
Click here to check amazing Vam Wfp content for Sudan. Otherwise, check out these important facts you probably never knew about vam.wfp.org
Visit vam.wfp.orgWe analyzed Vam.wfp.org page load time and found that the first response time was 726 ms and then it took 2.3 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.
vam.wfp.org performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value16.3 s
0/100
25%
Value7.2 s
30/100
10%
Value970 ms
28/100
30%
Value0
100/100
15%
Value9.9 s
27/100
10%
726 ms
233 ms
347 ms
361 ms
479 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 21% of them (18 requests) were addressed to the original Vam.wfp.org, 60% (52 requests) were made to Js.arcgis.com and 3% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (859 ms) belongs to the original domain Vam.wfp.org.
Page size can be reduced by 2.1 MB (71%)
2.9 MB
822.8 kB
In fact, the total size of Vam.wfp.org main page is 2.9 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. Javascripts take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 391.1 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 391.1 kB or 90% of the original size.
Potential reduce by 55 B
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. Vam Wfp images are well optimized though.
Potential reduce by 1.3 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 1.3 MB or 72% of the original size.
Potential reduce by 323.8 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. Vam.wfp.org needs all CSS files to be minified and compressed as it can save up to 323.8 kB or 86% of the original size.
Number of requests can be reduced by 77 (92%)
84
7
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vam Wfp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 64 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
vam.wfp.org
726 ms
reset.css
233 ms
990_18_0_10.css
347 ms
main.css
361 ms
jquery.fancybox-1.3.4.css
479 ms
jquery.min.js
26 ms
jquery.fancybox-1.3.4.js
598 ms
shareaholic.js
6 ms
worldmap.html
147 ms
vam_banner2.jpg
678 ms
triangle1.png
230 ms
homepageimage.jpg
859 ms
Hotspot_Legend.png
233 ms
bullet01.png
230 ms
analytics.js
22 ms
collect
67 ms
d0ebea9e2cf3a213f5d6429fb39ec4be.json
68 ms
shrMain.min.js
14 ms
collect
197 ms
esri.css
179 ms
claro.css
108 ms
layout.css
193 ms
utilities.js
191 ms
preload.js
202 ms
requests.js
203 ms
extent.js
314 ms
popups.js
316 ms
tundra.css
188 ms
jquery.min.js
100 ms
init.js
138 ms
pageview.gif
241 ms
jsapi_en-us.js
131 ms
svg.js
70 ms
FeatureLayer.js
58 ms
TitlePane.js
66 ms
BasemapGallery.js
58 ms
BorderContainer.js
61 ms
Toolbar.js
57 ms
ComboBox.js
59 ms
ItemFileReadStore.js
58 ms
DateTextBox.js
57 ms
Legend.js
59 ms
Bookmarks.js
185 ms
DeferredList.js
61 ms
blank.gif
52 ms
app.js
122 ms
vglnk.js
122 ms
partners.js
398 ms
FeatureType.js
73 ms
FeatureTemplate.js
68 ms
FeatureEditResult.js
78 ms
SnapshotMode.js
72 ms
OnDemandMode.js
71 ms
SelectionMode.js
69 ms
TrackManager.js
74 ms
WebTiledLayer.js
105 ms
Basemap.js
69 ms
_KeyNavContainer.js
67 ms
Calendar.js
65 ms
_DateTimeTextBox.js
68 ms
filter.js
68 ms
simpleFetch.js
69 ms
ComboBoxMixin.js
70 ms
LayoutContainer.js
69 ms
entities.js
68 ms
ScaleDependentRenderer.js
69 ms
DotDensityRenderer.js
66 ms
BookmarkItem.js
259 ms
pixel.gif
44 ms
pixel.gif
42 ms
angular.min.js
31 ms
RenderMode.js
26 ms
GridLayout.js
22 ms
CalendarLite.js
21 ms
_KeyNavMixin.js
19 ms
BasemapLayer.js
19 ms
RangeBoundTextBox.js
64 ms
sorter.js
60 ms
QueryResults.js
15 ms
_AutoCompleterMixin.js
15 ms
_ComboBoxMenu.js
15 ms
_LayoutWidget.js
57 ms
DataList.js
142 ms
_SearchMixin.js
142 ms
_ComboBoxMenuMixin.js
142 ms
_ListMouseMixin.js
141 ms
vam.wfp.org 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
vam.wfp.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
vam.wfp.org SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vam.wfp.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Vam.wfp.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.
vam.wfp.org
Open Graph description is not detected on the main page of Vam Wfp. 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: