27.6 sec in total
3.9 sec
22.8 sec
882 ms
Visit mobile.icta.lk now to see the best up-to-date Mobile ICTA content for Sri Lanka and also check out these interesting facts you probably never knew about mobile.icta.lk
To harness ICT as a lever for economic and social advancement by taking the dividends of ICT to every village, to every citizen, to every business & to re
Visit mobile.icta.lkWe analyzed Mobile.icta.lk page load time and found that the first response time was 3.9 sec and then it took 23.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
mobile.icta.lk performance score
3875 ms
8386 ms
89 ms
111 ms
84 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Mobile.icta.lk, 67% (85 requests) were made to Icta.lk and 13% (16 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (8.4 sec) relates to the external source Icta.lk.
Page size can be reduced by 1.3 MB (41%)
3.1 MB
1.8 MB
In fact, the total size of Mobile.icta.lk main page is 3.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. 70% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 71.3 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. This page needs HTML code to be minified as it can gain 17.1 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 71.3 kB or 84% of the original size.
Potential reduce by 2.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. Mobile ICTA images are well optimized though.
Potential reduce by 466.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 466.9 kB or 71% of the original size.
Potential reduce by 749.3 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. Mobile.icta.lk needs all CSS files to be minified and compressed as it can save up to 749.3 kB or 79% of the original size.
Number of requests can be reduced by 65 (64%)
102
37
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile ICTA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
mobile.icta.lk
3875 ms
www.icta.lk
8386 ms
css
89 ms
css
111 ms
font-awesome.min.css
84 ms
materialize.min.css
59 ms
responsive-tabs.css
490 ms
animate.min.css
740 ms
hover.css
746 ms
language-selector.css
744 ms
styles.css
777 ms
styles.css
778 ms
css
120 ms
genericons.css
1007 ms
style.css
1265 ms
public.css
992 ms
jquery-2.1.4.min.js
82 ms
require-utils.js
993 ms
js_composer.min.css
1305 ms
jquery.form.min.js
770 ms
scripts.js
1006 ms
qppr_frontend_script.min.js
1006 ms
skip-link-focus-fix.js
1018 ms
functions.js
1021 ms
sitepress.js
1290 ms
api.js
37 ms
js_composer_front.js
1290 ms
foundation.min.js
1628 ms
materialize.min.js
15 ms
packery.pkgd.js
22 ms
responsiveTabs.js
1290 ms
jquery.vide.js
1291 ms
scrollReveal.js
1561 ms
jQuery.scrollSpeed.js
1561 ms
app.js
1562 ms
analytics.js
21 ms
wp-emoji-release.min.js
1105 ms
collect
13 ms
logo.jpg
497 ms
search.png
1033 ms
loading.gif
1032 ms
revolutaionbg.jpg
1482 ms
milestones_timeline.png
1032 ms
vision.png
1031 ms
leadership.jpg
1703 ms
act.png
1275 ms
analysis.png
2015 ms
mission.png
1779 ms
industry-icon.png
1273 ms
reply.png
1527 ms
digital.png
1779 ms
digital-icon.png
1729 ms
legal.png
1777 ms
legal-icon.png
1951 ms
policy.jpg
1979 ms
policy-icon.png
2032 ms
digitization.png
2033 ms
digitization-icon.png
2027 ms
capacity-icon.png
2201 ms
slmap.png
2227 ms
citizen-icon.png
2261 ms
security-icon.png
2277 ms
government.png
2281 ms
communication.png
2145 ms
education.png
2310 ms
medical.png
2331 ms
agriculture.png
2366 ms
Roboto-Regular.woff
169 ms
Roboto-Medium.woff
203 ms
Roboto-Light.woff
203 ms
Roboto-Thin.woff
330 ms
Roboto-Bold.woff
266 ms
xkvoNo9fC8O2RDydKj12by3USBnSvpkopQaUR-2r7iU.ttf
329 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
827 ms
1ImRNPx4870-D9a1EBUdPC3USBnSvpkopQaUR-2r7iU.ttf
880 ms
PKCRbVvRfd5n7BTjtGiFZC3USBnSvpkopQaUR-2r7iU.ttf
879 ms
CcKI4k9un7TZVWzRVT-T8y3USBnSvpkopQaUR-2r7iU.ttf
880 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
879 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
879 ms
8KhZd3VQBtXTAznvKjw-ky3USBnSvpkopQaUR-2r7iU.ttf
879 ms
RJMlAoFXXQEzZoMSUteGWKCWcynf_cDxXwCLxiixG1c.ttf
881 ms
fontawesome-webfont.woff
262 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
881 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
879 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
880 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
880 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
879 ms
private_sector.png
2374 ms
transportation.png
2302 ms
recaptcha__en.js
770 ms
address-icon.png
2172 ms
telephone-icon.png
2284 ms
mail-icon.png
2246 ms
sandakadapahana.png
3514 ms
Wifi.jpg
2779 ms
Poster-2.jpg
4819 ms
photo-3.jpg
8372 ms
startup-img-1.jpg
2424 ms
worldmap.png
1949 ms
socialwall.png
2201 ms
anchor
32 ms
styles__ltr.css
8 ms
pmjEM-GhLlUNyebIUFzIQS75e2Oo2a-wD-zEAXBpQqk.js
8 ms
webworker.js
38 ms
logo_48.png
7 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
7 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
7 ms
facebook.png
2225 ms
twitter.png
2250 ms
recaptcha__en.js
5 ms
gplus.png
2230 ms
youtube.png
2217 ms
linkedin.png
2074 ms
vimeo.png
2227 ms
pinterest.png
2216 ms
srilanka.png
2245 ms
nanasa.png
2427 ms
srilankadept.png
2288 ms
gic_en_.gif
2277 ms
cd-top-arrow.svg
2261 ms
ajax-loader.gif
2426 ms
icta.jpg
5432 ms
whoweare.png
2475 ms
whatwedo.png
2318 ms
future.png
2479 ms
involved.png
2494 ms
mobile.icta.lk SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.icta.lk 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 Mobile.icta.lk 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.
mobile.icta.lk
Open Graph description is not detected on the main page of Mobile ICTA. 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: