10 sec in total
2.1 sec
7.5 sec
376 ms
Click here to check amazing LAPAN content for Indonesia. Otherwise, check out these important facts you probably never knew about lapan.go.id
Visit lapan.go.idWe analyzed Lapan.go.id page load time and found that the first response time was 2.1 sec and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lapan.go.id performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value19.8 s
0/100
25%
Value20.5 s
0/100
10%
Value5,270 ms
0/100
30%
Value0.902
3/100
15%
Value21.6 s
1/100
10%
2120 ms
514 ms
528 ms
532 ms
531 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 61% of them (63 requests) were addressed to the original Lapan.go.id, 10% (10 requests) were made to Maps.google.com and 9% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Lapan.go.id.
Page size can be reduced by 1.4 MB (23%)
5.9 MB
4.6 MB
In fact, the total size of Lapan.go.id main page is 5.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. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 71.5 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 21.2 kB, which is 25% 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.5 kB or 85% of the original size.
Potential reduce by 361.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. LAPAN images are well optimized though.
Potential reduce by 684.1 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 684.1 kB or 68% of the original size.
Potential reduce by 257.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. Lapan.go.id needs all CSS files to be minified and compressed as it can save up to 257.7 kB or 83% of the original size.
Number of requests can be reduced by 32 (33%)
96
64
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LAPAN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
lapan.go.id
2120 ms
normalize.css
514 ms
base.css
528 ms
grid.css
532 ms
style.css
531 ms
demo_responsivelayout.css
535 ms
easy-responsive-tabs.css
534 ms
jquery.min.js
1043 ms
modernizr-2.6.2.min.js
791 ms
responsiveslides.css
792 ms
demo_responsiveslide.css
794 ms
responsiveslides.min.js
798 ms
easyResponsiveTabs.js
796 ms
default.css
1089 ms
nivo-slider.css
1088 ms
jquery.nivo.slider.js
1093 ms
jquery.carouFredSel-6.2.1.js
1349 ms
bgspace.jpg
1560 ms
headerlapan1.jpg
2395 ms
cariicon.png
269 ms
detekgan.png
1854 ms
banner-penginderaan-jauh.png
2102 ms
sainsa.png
2399 ms
kebijakan-kedirgantaraan1.png
2392 ms
sainsa5.png
1820 ms
deinderaja3.png
2079 ms
detekgan4.png
2120 ms
kebijakan5.png
2338 ms
layanan_informasi3.png
2365 ms
blu.jpg
2386 ms
LAYANAN_MANAJEMEN3.png
2600 ms
diskusi_tempo.jpg
2638 ms
ttd.jpg
2919 ms
galaxy.jpg
2928 ms
unsoed.png
2663 ms
363665_penampakan-matahari-5-menit-jelang-gmt_663_3823_thumb.jpg
2665 ms
de67b9eab66efc9602ffd3265e9b05932_thumb.jpeg
2858 ms
gmt_20160228_093510_thumb.jpg
2901 ms
1456651176_gerhana_thumb.jpg
2929 ms
web14.JPG
3743 ms
onlinelib.jpg
3119 ms
mini-banner.png
3164 ms
infolapan.png
3184 ms
Lapor.png
3193 ms
kepeg.jpg
3195 ms
cliping.jpg
3381 ms
jdih_link.jpg
3436 ms
iselion2015.jpg
3451 ms
aprsaf1.png
3451 ms
lpse1.jpg
3452 ms
header_sidoma_logobaru.jpg
3631 ms
banner-hotspot.png
2814 ms
index2
806 ms
logo_aspwg.jpg
4226 ms
banner-gmt.png
1595 ms
Thumbnail_ISAST2015(1).jpg
3458 ms
icon_rb.png
3440 ms
t6TAWaNpGxY
158 ms
js15.js
27 ms
1445098.php
46 ms
cc_489.js
4 ms
www-embed-player-vflZsBgOl.css
63 ms
www-embed-player.js
92 ms
base.js
164 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
50 ms
ad_status.js
84 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
102 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
109 ms
js
55 ms
javascript2.js
278 ms
common.js
18 ms
map.js
36 ms
util.js
38 ms
geometry.js
36 ms
poly.js
37 ms
getdata
559 ms
onion.js
60 ms
openhand_8_8.cur
51 ms
transparent.png
20 ms
kh
42 ms
controls.js
18 ms
undo_poly.png
31 ms
css
34 ms
google4.png
21 ms
mapcnt6.png
15 ms
tmapctrl.png
12 ms
tmapctrl4.png
22 ms
imgs8.png
23 ms
google_white5.png
23 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
30 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
42 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
59 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
61 ms
e-proc.jpg
2178 ms
marker.js
10 ms
Drawing.png
257 ms
infowindow.js
10 ms
online_journal1.jpg
2088 ms
siptekgan_thumbnail.jpg
2140 ms
lapan_icons_send.png
1911 ms
facebook.jpg
1900 ms
twitter.gif
1892 ms
loading.gif
1830 ms
arrows.png
261 ms
lapan.go.id 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.
ARIA IDs are not unique
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
lapan.go.id 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lapan.go.id SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lapan.go.id can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Lapan.go.id 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.
lapan.go.id
Open Graph description is not detected on the main page of LAPAN. 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: