4 sec in total
390 ms
3.2 sec
416 ms
Welcome to total.id homepage info - get ready to check Total best content for Indonesia right away, or after learning these important things about total.id
Find out how at Total, we commit to better energy in Indonesia through our activities and projects. Commit with us !
Visit total.idWe analyzed Total.id page load time and found that the first response time was 390 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
total.id performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value8.1 s
2/100
25%
Value6.4 s
41/100
10%
Value320 ms
76/100
30%
Value0.285
42/100
15%
Value8.2 s
40/100
10%
390 ms
214 ms
296 ms
292 ms
432 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Total.id, 16% (17 requests) were made to Files.cotoben.total.com and 6% (6 requests) were made to Pixel.mathtag.com. The less responsive or slowest element that took the longest time to load (725 ms) relates to the external source Files.cotoben.total.com.
Page size can be reduced by 1.0 MB (63%)
1.7 MB
619.5 kB
In fact, the total size of Total.id main page is 1.7 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. 65% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 36.1 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 5.2 kB, which is 11% 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 36.1 kB or 75% of the original size.
Potential reduce by 11.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. Total images are well optimized though.
Potential reduce by 810.0 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 810.0 kB or 72% of the original size.
Potential reduce by 183.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. Total.id needs all CSS files to be minified and compressed as it can save up to 183.5 kB or 86% of the original size.
Number of requests can be reduced by 65 (67%)
97
32
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Total. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and as a result speed up the page load time.
total.id
390 ms
en-us
214 ms
css__2xDLJnQ_bUwQjbR35Zgty3W0-dsNocWxciLR9cOMqmE__lPqTBWw_oUdI_WjXEaGA28Dgdc6G1Rjdq3H7G7xVczw__Ugs-8jTmTVKn6ZUwGSYE0QjcpBNSI_rYfms0PkixcNc.css
296 ms
js__LIgtn4YeaXb0QEEG7aovEL39kUjmeo5j4WZdOOUJwDE___p_ToJO1QmGt2Da_WB0On-gpR9VYDzldJaG7_lg5vtY__Ugs-8jTmTVKn6ZUwGSYE0QjcpBNSI_rYfms0PkixcNc.js
292 ms
swfobject2.js
432 ms
commonFunctions.js
79 ms
js__RHmWSmTVaP_rY6_-wWYujk3AzTMENcLpSTG8Fru_lxU__fKs18vOyhEn9k4ZPix1_4ySWrXSjlCTTu18pJ8eQYCw__Ugs-8jTmTVKn6ZUwGSYE0QjcpBNSI_rYfms0PkixcNc.js
293 ms
js__DUbJ4Q1Jw6MhxbqrcmEs0YOx_ote-nXlbUg4Y033eCY__a5203MlaAm3c6HKj1LsulEE2M2efrDJO7bB4wMl3dCE__Ugs-8jTmTVKn6ZUwGSYE0QjcpBNSI_rYfms0PkixcNc.js
329 ms
js__TW-KpH837aE7SHChJ-AmTBLHwtOig323DlE3ouyKZZo__rb0bYRvqVjrA0XFyE11Z4-q4Fy8tS00xbK7LfjMTwaQ__Ugs-8jTmTVKn6ZUwGSYE0QjcpBNSI_rYfms0PkixcNc.js
147 ms
js__-5DqRMWSmhm50dsDNBXXy9F_jFHQv5jK9AQwB7I-oaQ__PVQZ5iYs87nr0NjqONb6QKHYjgJm2DD-EqYWNmGZobA__Ugs-8jTmTVKn6ZUwGSYE0QjcpBNSI_rYfms0PkixcNc.js
328 ms
buttons.js
34 ms
js__EQTbev17bwXgN5dFRCepR2PIZw5VbXqM64l6ahKGVho__9BjT3lmlA2REMVik3670N2e5vSRxN__Q05EO5qK_wd4__Ugs-8jTmTVKn6ZUwGSYE0QjcpBNSI_rYfms0PkixcNc.js
326 ms
ServerOnline.gif
402 ms
logo.png
356 ms
australie_0.jpg
356 ms
icon_worl_generique_0.png
275 ms
cental_prrof_gaz_pillar.jpg
95 ms
indonesie_home_icon_pillar_1_id.png
354 ms
mechanic_training_300x231.jpg
353 ms
icon-joinus.png
352 ms
denny_pribadi_podium_300x231.jpg
355 ms
hp_proccom_total.png
549 ms
hp_id_total.png
487 ms
website_awango_by_total.png
547 ms
fb_31.png
549 ms
twitter_17.png
491 ms
linkedin_28.png
547 ms
youtube_28.png
649 ms
instagram_28.png
580 ms
vine2_28.png
725 ms
activityi;src=4482784;type=HomeP0;cat=HomeP0;ord=1;num=6657725307159.126
52 ms
icons-sd63bfddfe5.png
358 ms
player.php
343 ms
bg-header-960.png
362 ms
bg-slider-inner.png
383 ms
play-960px.png
384 ms
widgets.js
21 ms
x24919
225 ms
beacon
302 ms
oct.js
13 ms
i.cid
382 ms
beacon
299 ms
11398868-5e58-467f-86d1-650e10dd998a.woff
492 ms
631bf655-ced5-4627-93d4-89d1bdfe3014.woff
426 ms
4d888997-2061-451b-8569-6cee195e9915.woff
491 ms
200b707d-2296-40cb-8b09-72cea5de16a8.woff
381 ms
all.js
25 ms
ga.js
272 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
204 ms
getAllAppDefault.esi
276 ms
arrow-gray.png
102 ms
commonFunctions.js
98 ms
154 ms
179 ms
xd_arbiter.php
57 ms
xd_arbiter.php
122 ms
ps
48 ms
pixel
80 ms
80 ms
Pug
78 ms
usersync
68 ms
iframe.html
369 ms
collect
119 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
28 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
40 ms
info.json
154 ms
xuid
58 ms
tap.php
53 ms
demconf.jpg
51 ms
sd
50 ms
cmap
64 ms
61 ms
pixel
37 ms
ga-audiences
53 ms
js
31 ms
getSegment.php
21 ms
i.match
103 ms
i.match
103 ms
i.match
100 ms
i.js
60 ms
adsct
134 ms
adsct
56 ms
fbds.js
5 ms
4 ms
t.dhj
60 ms
hit.xiti
221 ms
t.dhj
39 ms
overlay.js
302 ms
cm
43 ms
x35248
119 ms
js
95 ms
s-3271.xgi
21 ms
6 ms
hbpix
34 ms
xrefid.xgi
23 ms
pixel
16 ms
12 ms
kickStyles.css
360 ms
jquery-1.7.min.js
401 ms
iscroll.min.js
429 ms
wscompiler_v2_compressed.js
396 ms
2981
27 ms
img
48 ms
jot.html
2 ms
iframe
30 ms
img
23 ms
img
27 ms
analytics.js
28 ms
vy76p0k6.json
36 ms
total.id 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
total.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
total.id SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Total.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 Total.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.
total.id
Open Graph description is not detected on the main page of Total. 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: