17.1 sec in total
743 ms
14.4 sec
1.9 sec
Welcome to dotcom.id homepage info - get ready to check Dotcom best content for Indonesia right away, or after learning these important things about dotcom.id
Branding is what we do! Good branding is what we excel at!
Visit dotcom.idWe analyzed Dotcom.id page load time and found that the first response time was 743 ms and then it took 16.4 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.
dotcom.id performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value12.5 s
0/100
25%
Value19.8 s
0/100
10%
Value2,970 ms
3/100
30%
Value0
100/100
15%
Value20.6 s
2/100
10%
743 ms
4778 ms
74 ms
308 ms
573 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 77% of them (107 requests) were addressed to the original Dotcom.id, 9% (12 requests) were made to Embed.tawk.to and 6% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Dotcom.id.
Page size can be reduced by 1.9 MB (48%)
3.9 MB
2.0 MB
In fact, the total size of Dotcom.id main page is 3.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 251.8 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 251.8 kB or 87% of the original size.
Potential reduce by 20.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. Dotcom images are well optimized though.
Potential reduce by 603.5 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 603.5 kB or 54% of the original size.
Potential reduce by 976.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. Dotcom.id needs all CSS files to be minified and compressed as it can save up to 976.4 kB or 71% of the original size.
Number of requests can be reduced by 93 (78%)
119
26
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dotcom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 50 to 1 for CSS and as a result speed up the page load time.
dotcom.id
743 ms
www.dotcom.id
4778 ms
js
74 ms
A.trx_addons_icons.css.pagespeed.cf.1vy6Q5v-3Z.css
308 ms
qw_extension_icons.css
573 ms
mwe5hxs.css
43 ms
css2
39 ms
fontello.css
771 ms
sbi-styles.min.css
1275 ms
advanced-popups-public.css
769 ms
magnific-popup.min.css
773 ms
webfont.min.css
787 ms
public.min.css
838 ms
fontawesome-all.min.css
1278 ms
style.min.css
1025 ms
style.css
1029 ms
elementor-icons.min.css
1050 ms
custom-frontend.min.css
1101 ms
swiper.min.css
1285 ms
__styles.css
2604 ms
portfolio.css
1318 ms
qw_extension_portfolio.css
1365 ms
qw_extension_portfolio.responsive.css
1526 ms
content.css
1534 ms
trx_addons.animations.css
1542 ms
mouse-helper.css
1583 ms
team.css
1631 ms
blogger.css
1784 ms
icons.css
1792 ms
skills.css
1802 ms
front.css
1854 ms
mediaelementplayer-legacy.min.css
1898 ms
wp-mediaelement.min.css
2043 ms
style.css
3134 ms
qw_extension_icons.css
2060 ms
__plugins.css
2682 ms
__custom.css
2163 ms
mailchimp-for-wp.css
2301 ms
style.css
2320 ms
qw_extension_icons.responsive.css
2427 ms
css
32 ms
extra-style.css
2533 ms
p.css
22 ms
jquery.min.js,qver=3.7.1.pagespeed.jm.PoWN7KAtLT.js
2539 ms
jquery-migrate.min.js,qver=3.4.1.pagespeed.jm.bhhu-RahTI.js
2170 ms
frontend-gtag.min.js
2059 ms
advanced-popups-public.js
2102 ms
hooks.min.js,qver==2810c76e705dd1a53b18+i18n.min.js,qver==5e580eb46a90c2b997e6.pagespeed.jc.Zu-AOy9T1u.js
2188 ms
jquery.magnific-popup.min.js
2186 ms
public.min.js
2250 ms
__scripts.js
2372 ms
mouse-helper.js
2105 ms
chart-legacy.min.js
2345 ms
skills.js
2290 ms
superfish.min.js
2125 ms
swiper.min.js
2231 ms
gsap.min.js
2226 ms
mailchimp-for-wp.js
2511 ms
portfolio.js
2464 ms
front.min.js
2305 ms
__scripts.js
2297 ms
mediaelement-and-player.min.js
2290 ms
mediaelement-migrate.min.js
2251 ms
wp-mediaelement.min.js
2386 ms
skin.js
2224 ms
imagesloaded.min.js
2216 ms
masonry.min.js
2220 ms
sbi-scripts.min.js
2170 ms
forms.js
2133 ms
webpack.runtime.min.js
2236 ms
frontend-modules.min.js
2227 ms
waypoints.min.js
2128 ms
core.min.js
1993 ms
frontend.min.js
1973 ms
fbevents.js
211 ms
sbi-sprite.png
1489 ms
front-bg.png
1489 ms
noise.png
1490 ms
januari-2024-27.png
1492 ms
Web-Dotcom-New-02.jpg
1491 ms
Web-Dotcom-New-08-890x890.jpg
1492 ms
Web-Dotcom-New-09-890x890.jpg
1492 ms
Web-Dotcom-New-10-890x890.jpg
1547 ms
Web-Dotcom-New-14.jpg
1570 ms
figure.png
1571 ms
cloud-computing-banner-background-smart-city.jpg
2367 ms
circle.png
1587 ms
team-1-570x696.jpg
1450 ms
c4mP1n92AsfhuCq6tVsaoIx1LQICk0boNoq0SjlDfnzKo-bF3mdQkZYA8Q.ttf
203 ms
c4mP1n92AsfhuCq6tVsaoIx1LQICk0boNoq0SjlDfnzKo-bF3mdQo5YA8Q.ttf
204 ms
c4mP1n92AsfhuCq6tVsaoIx1LQICk0boNoq0SjlDfnzKo-bF3mdQz5YA8Q.ttf
363 ms
c4mP1n92AsfhuCq6tVsaoIx1LQICk0boNoq0SjlDfnzKo-bF3mdQEZYA8Q.ttf
444 ms
c4mP1n92AsfhuCq6tVsaoIx1LQICk0boNoq0SjlDfnzKo-bF3mdQkZcA8Q.ttf
445 ms
c4mP1n92AsfhuCq6tVsaoIx1LQICk0boNoq0SjlDfnzKo-bF3mdQT5EA8Q.ttf
446 ms
c4mP1n92AsfhuCq6tVsaoIx1LQICk0boNoq0SjlDfnzKo-bF3mdQdpEA8Q.ttf
445 ms
c4mP1n92AsfhuCq6tVsaoIx1LQICk0boNoq0SjlDfnzKo-bF3mdQEZEA8Q.ttf
445 ms
c4mP1n92AsfhuCq6tVsaoIx1LQICk0boNoq0SjlDfnzKo-bF3mdQOJEA8Q.ttf
443 ms
d
118 ms
d
201 ms
d
200 ms
d
200 ms
d
199 ms
fontello.woff
2167 ms
team-2-570x696.jpg
1678 ms
team-3-570x696.jpg
1683 ms
team-4-570x696.jpg
1704 ms
default
323 ms
web-hosting-630x630.jpg
1595 ms
fa-brands-400.ttf
2047 ms
fa-solid-900.ttf
1519 ms
fa-regular-400.ttf
1580 ms
ssl-630x630.jpg
1906 ms
placeholder.png
1786 ms
450296980_1524226841500149_3827829093865167355_nfull.jpg
963 ms
449321292_1508389010039104_1771227652531243967_n.heicfull.jpg
1049 ms
449330512_8555482521131710_1559174952991801972_n.heicfull.jpg
1082 ms
448916634_993107519266925_6063689655735873381_n.heicfull.jpg
1101 ms
440515803_376643018706479_2508709561115211265_nfull.jpg
1101 ms
portfolio.responsive.css
267 ms
content.responsive.css
267 ms
__responsive.css
270 ms
mouse-helper.responsive.css
269 ms
team.responsive.css
266 ms
blogger.responsive.css
269 ms
icons.responsive.css
267 ms
skills.responsive.css
267 ms
__responsive.css
269 ms
responsive.css
266 ms
twk-arr-find-polyfill.js
54 ms
twk-object-values-polyfill.js
72 ms
twk-event-polyfill.js
70 ms
twk-entries-polyfill.js
80 ms
twk-iterator-polyfill.js
71 ms
twk-main.js
24 ms
twk-vendor.js
37 ms
twk-chunk-vendors.js
61 ms
twk-chunk-common.js
68 ms
twk-runtime.js
83 ms
twk-app.js
78 ms
dotcom.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
[aria-hidden="true"] elements contain focusable descendents
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
Links do not have a discernible name
dotcom.id best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
dotcom.id SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dotcom.id 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 Dotcom.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.
dotcom.id
Open Graph data is detected on the main page of Dotcom. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: