4.8 sec in total
250 ms
4.2 sec
359 ms
Welcome to immigration.gov.tt homepage info - get ready to check Immigration best content for Trinidad and Tobago right away, or after learning these important things about immigration.gov.tt
The Immigration Division embraces the opportunity of providing information to it’s customers through this website. The Division welcomes you to this site and hopes it provides you with useful informat...
Visit immigration.gov.ttWe analyzed Immigration.gov.tt page load time and found that the first response time was 250 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
immigration.gov.tt performance score
250 ms
838 ms
728 ms
730 ms
758 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 Immigration.gov.tt, 7% (5 requests) were made to Translate.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Immigration.gov.tt.
Page size can be reduced by 2.8 MB (28%)
10.1 MB
7.3 MB
In fact, the total size of Immigration.gov.tt main page is 10.1 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. 45% of websites need less resources to load. Images take 8.6 MB which makes up the majority of the site volume.
Potential reduce by 54.6 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 54.6 kB or 80% of the original size.
Potential reduce by 1.8 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. Obviously, Immigration needs image optimization as it can save up to 1.8 MB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 867.9 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 867.9 kB or 64% of the original size.
Potential reduce by 73.1 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. Immigration.gov.tt needs all CSS files to be minified and compressed as it can save up to 73.1 kB or 78% of the original size.
Number of requests can be reduced by 30 (42%)
71
41
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Immigration. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
immigration.gov.tt
250 ms
default.css
838 ms
module.css
728 ms
skin.css
730 ms
container.css
758 ms
portal.css
707 ms
module.css
710 ms
StandardMenu.css
1174 ms
ComboBox.Default.css
1114 ms
jquery.min.js
1190 ms
jquery-ui.min.js
1208 ms
style.css
1170 ms
Telerik.Web.UI.WebResource.axd
1075 ms
WebResource.axd
1111 ms
jquery.easing.1.3.js
1132 ms
trans-banner.min.js
1209 ms
Telerik.Web.UI.WebResource.axd
1227 ms
dnn.js
1242 ms
dnn.modalpopup.js
1212 ms
ControlPanel.debug.js
1938 ms
dnn.jquery.js
1990 ms
dnncore.js
1933 ms
jquery.cycle.min.js
2291 ms
StandardMenu.js
1243 ms
jquery.hoverIntent.min.js
1955 ms
element.js
19 ms
Search.js
1860 ms
initWidgets.js
2053 ms
ga.js
12 ms
govtt_header_left.jpg
794 ms
immigrationlogosmall.png
808 ms
StandardLI.png
809 ms
Action_16X16_Standard.png
817 ms
1.Pic1.png
1464 ms
1.Pic5.png
965 ms
1.Pic8.png
1718 ms
1.Pic2.png
1473 ms
1.Pic9.png
1706 ms
1.Pic3.png
1533 ms
1.Pic7.png
2085 ms
1.Pic6.png
1758 ms
HomePic1.png
1780 ms
HomePic2.png
1695 ms
HomePic3.png
1776 ms
ReadMore1.png
2192 ms
HomePic4.png
2198 ms
HomePic5.png
2203 ms
HomePic7.png
2161 ms
dbl_footer.png
2203 ms
govtt.png
2188 ms
__utm.gif
19 ms
Body-BG.jpg
1105 ms
headfootbg.png
1119 ms
rootItemR.png
1120 ms
rootItemL.png
1128 ms
search.png
1147 ms
translateelement.css
25 ms
main.js
79 ms
site_bg_ie.png
1657 ms
preloader.gif
1099 ms
preloader.gif
1110 ms
Footer-BG.png
1223 ms
DotNetNukeAjaxShared.js
1237 ms
DnnSearch_16X16_Standard.png
1180 ms
icons.png
1215 ms
timer-sprite.png
1224 ms
TitilliumText22L005-webfont.ttf
1514 ms
element_main.js
4 ms
translate_24dp.png
18 ms
l
21 ms
cleardot.gif
35 ms
translate_24dp.png
10 ms
te_ctrl3.gif
4 ms
widgets.js
392 ms
immigration.gov.tt SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Immigration.gov.tt 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 Immigration.gov.tt 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.
immigration.gov.tt
Open Graph description is not detected on the main page of Immigration. 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: