1.6 sec in total
156 ms
1.3 sec
116 ms
Click here to check amazing IGEMS DOI content for United States. Otherwise, check out these important facts you probably never knew about igems.doi.gov
Public website for the Interior Geospatial Emergency Management Systems (IGEMS)
Visit igems.doi.govWe analyzed Igems.doi.gov page load time and found that the first response time was 156 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
igems.doi.gov performance score
156 ms
35 ms
62 ms
125 ms
119 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 15% of them (17 requests) were addressed to the original Igems.doi.gov, 85% (95 requests) were made to Js.arcgis.com. The less responsive or slowest element that took the longest time to load (461 ms) belongs to the original domain Igems.doi.gov.
Page size can be reduced by 1.2 MB (71%)
1.7 MB
489.7 kB
In fact, the total size of Igems.doi.gov 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. 40% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 19.9 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 19.9 kB or 85% of the original size.
Potential reduce by 1.0 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. IGEMS DOI images are well optimized though.
Potential reduce by 983.5 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 983.5 kB or 69% of the original size.
Potential reduce by 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. Igems.doi.gov needs all CSS files to be minified and compressed as it can save up to 178.7 kB or 85% of the original size.
Number of requests can be reduced by 106 (95%)
111
5
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IGEMS DOI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 98 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
igems.doi.gov
156 ms
esri.css
35 ms
bootstrapmap.css
62 ms
bootstrap_custom.css
125 ms
igems.css
119 ms
igems.js
271 ms
jquery-1.11.0.min.js
461 ms
bootstrap.min.js
177 ms
misc.js
121 ms
init.js
166 ms
jsapi_en-us.js
212 ms
QueryTask.js
200 ms
RelationshipQuery.js
198 ms
StatisticDefinition.js
197 ms
svg.js
193 ms
bootstrapmap.js
119 ms
Geocoder.js
61 ms
BasemapGallery.js
60 ms
Scalebar.js
34 ms
OverviewMap.js
60 ms
Bookmarks.js
58 ms
WebTiledLayer.js
61 ms
Legend.js
61 ms
IdentifyTask.js
99 ms
IdentifyParameters.js
84 ms
Print.js
133 ms
doi_logo.png
79 ms
About.png
79 ms
Basemap.png
79 ms
Bookmark.png
79 ms
Layer.png
80 ms
Legend.png
123 ms
MapRefresh.png
120 ms
loading.gif
122 ms
Task.js
29 ms
FeatureSet.js
31 ms
BookmarkItem.js
154 ms
DeferredList.js
35 ms
_Widget.js
18 ms
_Templated.js
109 ms
VETiledLayer.js
32 ms
ArcGISImageServiceLayer.js
183 ms
ImageServiceParameters.js
80 ms
Basemap.js
73 ms
_EventedWidget.js
118 ms
Moveable.js
110 ms
a11yclick.js
78 ms
_TemplatedMixin.js
84 ms
focus.js
88 ms
locator.js
94 ms
entities.js
134 ms
ScaleDependentRenderer.js
124 ms
DotDensityRenderer.js
149 ms
_WidgetBase.js
105 ms
_OnDijitClickMixin.js
108 ms
_FocusMixin.js
111 ms
hccss.js
115 ms
IdentifyResult.js
134 ms
utils.js
186 ms
touch.js
99 ms
NodeList-traverse.js
143 ms
Menu.js
89 ms
MenuItem.js
94 ms
Button.js
120 ms
ComboButton.js
112 ms
PrintTask.js
149 ms
PrintParameters.js
154 ms
BasemapLayer.js
157 ms
cache.js
99 ms
_AttachMixin.js
101 ms
a11y.js
101 ms
AddressCandidate.js
96 ms
_WidgetsInTemplateMixin.js
178 ms
common.js
168 ms
Mover.js
150 ms
Destroyable.js
103 ms
hccss.js
98 ms
popup.js
106 ms
DropDownMenu.js
105 ms
_Contained.js
100 ms
_CssStateMixin.js
101 ms
DropDownButton.js
92 ms
MosaicRule.js
96 ms
ImageServiceIdentifyTask.js
87 ms
ImageServiceIdentifyParameters.js
97 ms
_FormWidget.js
136 ms
_ButtonMixin.js
161 ms
Geoprocessor.js
67 ms
PrintTemplate.js
91 ms
canvas.js
145 ms
query.js
107 ms
LegendLayer.js
87 ms
blank.gif
69 ms
place.js
49 ms
BackgroundIframe.js
53 ms
Viewport.js
57 ms
_MenuBase.js
61 ms
autoscroll.js
88 ms
_Container.js
58 ms
_HasDropDown.js
254 ms
JobInfo.js
45 ms
GPMessage.js
46 ms
LinearUnit.js
60 ms
DataFile.js
49 ms
RasterData.js
60 ms
Date.js
61 ms
ParameterValue.js
60 ms
GPResultImageLayer.js
61 ms
_FormWidgetMixin.js
84 ms
main.js
78 ms
_KeyNavContainer.js
26 ms
_KeyNavMixin.js
9 ms
igems.doi.gov SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Igems.doi.gov 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 Igems.doi.gov 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.
igems.doi.gov
Open Graph description is not detected on the main page of IGEMS DOI. 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: