4.4 sec in total
433 ms
3.4 sec
599 ms
Visit icity.indosat.com now to see the best up-to-date Icity Indosat content for Indonesia and also check out these interesting facts you probably never knew about icity.indosat.com
Forum Berbasis Solusi Pertama di Indonesia, dikembangkan oleh komunitas pengguna Indosat
Visit icity.indosat.comWe analyzed Icity.indosat.com page load time and found that the first response time was 433 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.
icity.indosat.com performance score
433 ms
1366 ms
162 ms
199 ms
60 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Icity.indosat.com, 67% (90 requests) were made to Indosat.i.lithium.com and 7% (9 requests) were made to Icity.indosatooredoo.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Icity.indosatooredoo.com.
Page size can be reduced by 916.9 kB (56%)
1.6 MB
731.2 kB
In fact, the total size of Icity.indosat.com main page is 1.6 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 514.6 kB which makes up the majority of the site volume.
Potential reduce by 276.0 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 69.0 kB, which is 23% 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 276.0 kB or 90% of the original size.
Potential reduce by 26.8 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. Icity Indosat images are well optimized though.
Potential reduce by 326.7 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 326.7 kB or 67% of the original size.
Potential reduce by 287.4 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. Icity.indosat.com needs all CSS files to be minified and compressed as it can save up to 287.4 kB or 85% of the original size.
Number of requests can be reduced by 41 (34%)
121
80
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Icity Indosat. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
icity.indosat.com
433 ms
icity.indosatooredoo.com
1366 ms
indosat_20151094501806.css
162 ms
owl.carousel.css
199 ms
desktop.css
60 ms
buttons.js
11 ms
jquery-1.11.1.min.js
330 ms
owl.carousel.min.js
70 ms
lia-scripts-head-min.js
206 ms
widgets.js
5 ms
lia-scripts-common-min.js
296 ms
lia-scripts-body-min.js
47 ms
icon_thread.png
276 ms
icon_blog_thread.png
247 ms
icon_ideas.png
246 ms
icon_tkb_thread.png
247 ms
message_type_solved.png
244 ms
64x64
245 ms
body-bg.png
65 ms
icity-logo.png
64 ms
menu-log.png
62 ms
BannerICITY_Bank%20Ide_V2.png
236 ms
Banner-FreedomCombo-ffd400-v1.png
135 ms
menu-guidelines.png
64 ms
menu-ask-community.png
66 ms
menu-join-group.png
65 ms
icon-search.png
105 ms
icon_help.png
105 ms
thread-pilihan-sprite.png
106 ms
thread-terasyik-sprite.png
105 ms
terbaru-sprite.png
242 ms
level3.png
235 ms
level1.png
254 ms
newbie.png
242 ms
bank-solusi-sprite.png
240 ms
group-sprite.png
272 ms
video-sprite.png
275 ms
profile
275 ms
profile
275 ms
profile
275 ms
profile
289 ms
profile
309 ms
profile
370 ms
profile
367 ms
profile
368 ms
profile
370 ms
video1.jpg
385 ms
video2.jpg
385 ms
video3.jpg
386 ms
video4.jpg
385 ms
ide-sprite.png
386 ms
blog-sprite.png
387 ms
Komunitas-1.png
341 ms
videoseries
186 ms
videoseries
233 ms
videoseries
251 ms
videoseries
220 ms
icon_blog.png
334 ms
icon_tkb_board.png
335 ms
icon_idea.png
338 ms
arrow-sprite.png
338 ms
tekno-sprite.png
336 ms
icon_board.png
378 ms
FuturaStd-Book_gdi.woff
356 ms
ga.js
150 ms
FuturaStd-Medium_gdi.woff
317 ms
ooredoo-Bold_gdi.woff
340 ms
ooredoo-Regular_gdi.woff
339 ms
fontawesome-webfont.woff
396 ms
page.twitterstreamtaplet:getnewtweets
417 ms
tweet.04d20138f67ab41d6b4af6cc583926d9.js
100 ms
getAllAppDefault.esi
145 ms
fontawesome_webfont.woff
271 ms
fontawesome-webfont.woff
268 ms
FuturaStd-Heavy_gdi.woff
265 ms
www-embed-player-vflQrT_sR.css
54 ms
www-embed-player.js
73 ms
layanan-sprite.png
261 ms
message
380 ms
64x64
391 ms
message
362 ms
message
362 ms
NewRank_SUPERUSER.png
302 ms
message
386 ms
message
389 ms
message
507 ms
syndication
129 ms
tweets.json
213 ms
0%2C0%2C100%2C100
494 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
73 ms
ad_status.js
73 ms
moderator.png
296 ms
message
429 ms
message
450 ms
message
451 ms
getSegment.php
23 ms
checkOAuth.esi
18 ms
message
443 ms
message
563 ms
message
574 ms
message
576 ms
message
598 ms
message
599 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
51 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
52 ms
message
614 ms
message
754 ms
message
731 ms
message
732 ms
message
773 ms
message
751 ms
message
784 ms
t.dhj
36 ms
message
891 ms
message
877 ms
message
939 ms
online-sprite.png
735 ms
link-sprite.png
700 ms
UbTEnY-r_normal.png
232 ms
TwitterItemActions.js
161 ms
t.dhj
29 ms
twitter_stream_pause.png
588 ms
tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css
14 ms
tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css
11 ms
cm
58 ms
CbzNM9yWEAEHiSL.jpg:small
269 ms
s-3271.xgi
5 ms
26 ms
hbpix
468 ms
18 ms
xrefid.xgi
11 ms
pixel
20 ms
pixel
19 ms
2981
21 ms
jot
23 ms
icity.indosat.com SEO score
ID
IN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Icity.indosat.com can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and it does not match the claimed Indonesian language. Our system also found out that Icity.indosat.com 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.
icity.indosat.com
Open Graph data is detected on the main page of Icity Indosat. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: