7.2 sec in total
1.4 sec
5.5 sec
299 ms
Visit indeks.kompas.com now to see the best up-to-date Indeks Kompas content for Indonesia and also check out these interesting facts you probably never knew about indeks.kompas.com
Penyidik kepolisian sudah memintai keterangan dari sejumlah pihak, baik dari rumah sakit maupun keluarga korban.
Visit indeks.kompas.comWe analyzed Indeks.kompas.com page load time and found that the first response time was 1.4 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
indeks.kompas.com performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value3.5 s
63/100
25%
Value13.9 s
1/100
10%
Value16,960 ms
0/100
30%
Value0.013
100/100
15%
Value38.1 s
0/100
10%
1405 ms
540 ms
548 ms
547 ms
298 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Indeks.kompas.com, 20% (21 requests) were made to Assets.kompas.com and 10% (10 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Ads6.kompasads.com.
Page size can be reduced by 475.5 kB (60%)
793.5 kB
318.0 kB
In fact, the total size of Indeks.kompas.com main page is 793.5 kB. 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. Javascripts take 527.2 kB which makes up the majority of the site volume.
Potential reduce by 139.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. 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 139.5 kB or 84% of the original size.
Potential reduce by 4.9 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. Obviously, Indeks Kompas needs image optimization as it can save up to 4.9 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 272.6 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 272.6 kB or 52% of the original size.
Potential reduce by 58.5 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. Indeks.kompas.com needs all CSS files to be minified and compressed as it can save up to 58.5 kB or 83% of the original size.
Number of requests can be reduced by 70 (73%)
96
26
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Indeks Kompas. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
indeks.kompas.com
1405 ms
kcm-style-v2.css
540 ms
jquery.fancybox.css
548 ms
kcm-topbar.css
547 ms
jquery.js
298 ms
jquery.lazyload-ad-1.4.2-min.js
295 ms
glDatePicker.min.js
294 ms
jquery.lazyload.mini.js
293 ms
jquery.fancybox.pack.min.js
297 ms
modernizr.custom.js
294 ms
main_index.js
793 ms
sso_personalisasi.js
294 ms
modernizer.js
297 ms
dropdown.js
295 ms
css
24 ms
gpt.js
24 ms
search.jpg
21 ms
logoBottom.jpg
24 ms
pubads_impl_81.js
14 ms
OpenSans-Regular-webfont.woff
5 ms
OpenSans-ExtraBold-webfont.woff
5 ms
74rNkO0_718VQPTEmPNsIvesZW2xOQ-xsNqO47m55DA.ttf
56 ms
container.html
29 ms
ads
445 ms
ajs.php
1526 ms
osd.js
7 ms
afr.php
891 ms
afr.php
889 ms
countdown.js
4 ms
lg.php
318 ms
social.png
4 ms
adServer.bs
35 ms
OpenSans-Bold-webfont.woff
4 ms
OpenSans-Semibold-webfont.woff
4 ms
04022b4d-65aa-4d50-9412-78e5ee92d450.jpg
8 ms
bounce
9 ms
adsbygoogle.js
10 ms
widgets.js
25 ms
ca-pub-9012468469771973.js
150 ms
zrt_lookup.html
153 ms
show_ads_impl.js
81 ms
platform.js
194 ms
beacon.js
86 ms
em.js
244 ms
ads
269 ms
cb=gapi.loaded_0
22 ms
cb=gapi.loaded_1
46 ms
fastbutton
159 ms
fastbutton
151 ms
postmessageRelay
129 ms
frame_2.3.3.html
309 ms
atrk.js
368 ms
ga.js
98 ms
all.js
485 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
296 ms
grey.gif
558 ms
rs=AGLTcCMjK4CJMIdNJ3yzirfRYfXhXxdyVw
105 ms
js
474 ms
api.js
159 ms
core:rpc:shindig.random:shindig.sha1.js
365 ms
2536007149-postmessagerelay.js
360 ms
__utm.gif
174 ms
cb=gapi.loaded_0
186 ms
cb=gapi.loaded_1
186 ms
__utm.gif
174 ms
__utm.gif
172 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
416 ms
activeview
110 ms
activeview
130 ms
p
227 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
64 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
80 ms
bri970x250.html
579 ms
bri970x90.html
675 ms
atrk.gif
225 ms
lg.php
272 ms
lg.php
261 ms
info.json
262 ms
test.png
241 ms
img
110 ms
pixel
99 ms
ck-confirm
79 ms
271 ms
xd_arbiter.php
338 ms
xd_arbiter.php
551 ms
16-0015-AD4-300X250.gif
87 ms
lidar.js
51 ms
rs.js
99 ms
sbhK2lTE.js
86 ms
cTrvNaRi.html
9 ms
p
182 ms
rpc.flow
237 ms
vce_st.js
183 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
68 ms
edge.6.0.0.min.js
61 ms
p
46 ms
p
32 ms
bri970x250_edge.js
116 ms
bri970x90_edge.js
39 ms
bri970x90_edge.js
29 ms
jot.html
2 ms
activeview
14 ms
activeview
13 ms
bri970x250_edge.js
57 ms
indeks.kompas.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
indeks.kompas.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the notification permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
indeks.kompas.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
ID
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indeks.kompas.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 English language. Our system also found out that Indeks.kompas.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.
indeks.kompas.com
Open Graph data is detected on the main page of Indeks Kompas. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: