7.7 sec in total
570 ms
6.8 sec
413 ms
Click here to check amazing Raja Mobil content for Indonesia. Otherwise, check out these important facts you probably never knew about rajamobil.com
Beli Mobil Baru dan Mobil Bekas Secara Online, Tidak Perlu ke Dealer, Proses Cepat dan Mudah. Dapatkan Penawaran Harga Mobil , TDP Murah dan Angsuran Ringan.
Visit rajamobil.comWe analyzed Rajamobil.com page load time and found that the first response time was 570 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
rajamobil.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value21.1 s
0/100
25%
Value10.6 s
7/100
10%
Value1,260 ms
19/100
30%
Value0.343
32/100
15%
Value19.4 s
2/100
10%
570 ms
1910 ms
14 ms
11 ms
15 ms
Our browser made a total of 248 requests to load all elements on the main page. We found that 13% of them (31 requests) were addressed to the original Rajamobil.com, 7% (17 requests) were made to Imgcdn.rajamobil.com and 6% (16 requests) were made to Ads.contextweb.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Rajamobil.com.
Page size can be reduced by 1.2 MB (49%)
2.5 MB
1.3 MB
In fact, the total size of Rajamobil.com main page is 2.5 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. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 322.7 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 322.7 kB or 74% of the original size.
Potential reduce by 41.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. Raja Mobil images are well optimized though.
Potential reduce by 786.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 786.0 kB or 68% of the original size.
Potential reduce by 52.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. Rajamobil.com needs all CSS files to be minified and compressed as it can save up to 52.5 kB or 77% of the original size.
Number of requests can be reduced by 174 (76%)
229
55
The browser has sent 229 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Raja Mobil. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 109 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
rajamobil.com
570 ms
www.rajamobil.com
1910 ms
cloudflare.min.js
14 ms
jquery-ui.css
11 ms
dr-global.css
15 ms
chosen.css
31 ms
dr-home.css
7 ms
dr-w-showcase.css
31 ms
dr-w-iklanterkini.css
14 ms
jquery.js
558 ms
yii.js
577 ms
jquery-ui.js
38 ms
dr-posthead.js
31 ms
ld.js
31 ms
dr-global.js
6 ms
jquery.lockfixed.js
16 ms
dr-selected-pencarianmobil.js
3 ms
chosen.jquery.js
7 ms
jquery.bxslider.js
16 ms
dr-home.js
7 ms
adnetwork.js
20 ms
gpt.js
34 ms
atrk.js
96 ms
fbevents.js
51 ms
em.js
345 ms
analytics.js
49 ms
gtm.js
239 ms
ga.js
79 ms
bg-body.gif
36 ms
sprite-global.png
62 ms
logo-rajamobil-2015.png
21 ms
arrow-menu-li.gif
21 ms
Imlek-2016.jpg
22 ms
id_user_169-Tata-Nexon-IIMS-2014c_1456773805410.jpg
1428 ms
K1lQM2Icfe1tdIRTrBWLRRwZNwGXvM8j.jpg
67 ms
uvrOOFmnGclc7H0oN6INFkqtIukgyQEY.jpg
780 ms
gfZWGNdIWUGjFNC611jTYhfYWszp_b-X.jpg
760 ms
fIy_rh0Mrg1-52Emsmmbxr5OTlo5eh8z.jpg
214 ms
lCf5nudSScrDuR3Hfy71CKPN-7jSKp20.jpg
217 ms
7AXPW_-c32wvvgOMdsB7uvssLelGGZsk.jpg
208 ms
m2qSEAyRhCpH76BuOy4v9zqEcjXh-94B.JPG
209 ms
EMcTk1I4Tg_GYJ5-i7HtbbgWO1EDMgWk.jpg
213 ms
3teQhBhp77xdHOrGkQLUIlAAI7aoNUAF.jpg
213 ms
QTL5hqd74hFf3BLtgViy51uQ3YDfmiHS.jpg
216 ms
id_user_227-4_1456759432585.jpg
1424 ms
id_user_169-Militer_1456751060590.jpg
57 ms
id_user_169-Tata-giias-2015-AB_1456774204273.jpg
57 ms
id_user_200-Rio-5_1456745109202.jpg
58 ms
id_user_169-Tata-Nexon-IIMS-2014c_1456773805410.jpg
575 ms
id_user_227-4_1456759432585.jpg
609 ms
id_user_169-Militer_1456751060590.jpg
62 ms
id_user_169-Tata-giias-2015-AB_1456774204273.jpg
62 ms
id_user_200-Rio-5_1456745109202.jpg
207 ms
id_user_209-IMG-9953_1456712915687.jpg
202 ms
id_user_169-1_1456666991040.jpg
204 ms
id_user_209-rifat-1_1456642261601.jpg
210 ms
id_user_169-Toyota-Rush-TRD-Sportivo-2016A_1456565264457.jpeg
211 ms
id_user_200-Iris_1456746769537.jpg
664 ms
id_user_169-Makas_1456752399413.jpg
640 ms
id_user_207-Untitled-8_1456740836521.jpg
1464 ms
subscribe.gif
51 ms
event
192 ms
pubads_impl_81.js
187 ms
widget_v2.132.js
44 ms
oswald-light-webfont.woff
42 ms
oswald-bold-webfont.woff
186 ms
294 ms
collect
162 ms
pilihan-arrow.gif
150 ms
__$$__stringtable_lang_id.js
121 ms
atrk.gif
147 ms
__utm.gif
113 ms
__utm.gif
113 ms
event
352 ms
collect
144 ms
ads
758 ms
cookie.js
41 ms
container.html
43 ms
test.png
38 ms
collect
59 ms
frame_2.3.3.html
179 ms
icon-king-ads.png
15 ms
546 ms
p
96 ms
beacon.js
55 ms
emnb_77_ID-25.gif
484 ms
analytics_id.html
54 ms
adoptimised.html
551 ms
tracker.js
707 ms
gw.js
53 ms
arrow-select.gif
38 ms
lihatmerekbaru
879 ms
dc.js
27 ms
543864007.js
449 ms
__utm.gif
15 ms
expansion_embed.js
338 ms
8482890878778740581
521 ms
avatar_simple_visitor.png
146 ms
17000607190701889811
253 ms
3155579441332847698
255 ms
chosen-sprite.png
575 ms
abg.js
106 ms
m_js_controller.js
129 ms
googlelogo_color_112x36dp.png
208 ms
osd.js
74 ms
10070386151240319509
176 ms
4455830115762067006
178 ms
7973986877529353825
201 ms
9312732461987850541
179 ms
aL63HcygAAVYuCCsAAA==
31 ms
abd.jstag.js
109 ms
s
121 ms
x_button_blue2.png
98 ms
acj
551 ms
pixel
21 ms
pd
61 ms
rr
8 ms
show_ads_streamlyn.js
10 ms
ri
15 ms
show_ads_streamlyn.js
12 ms
rr
13 ms
ri
13 ms
show_ads_streamlyn.js
11 ms
rr
12 ms
ri
13 ms
ads-sync.js
11 ms
ads-sync.js
12 ms
ads-sync.js
11 ms
getjs.aspx
25 ms
getjs.aspx
26 ms
getjs.aspx
21 ms
getjs.static.js
28 ms
a83fbdd9-24ed-d4fb-1f09-3d030c7a08b7
54 ms
openx
11 ms
pixel
31 ms
openx
9 ms
sd
46 ms
GetAd.aspx
16 ms
GetAd.aspx
40 ms
GetAd.aspx
32 ms
sd
60 ms
sd
49 ms
sd
49 ms
ADTECH;cfp=1;rndc=1456805632;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456805632885
17 ms
ADTECH;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456805632904
20 ms
ADTECH;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456805632910
22 ms
400066.gif
22 ms
getjs.aspx
38 ms
400066.gif
19 ms
getjs.aspx
21 ms
400066.gif
17 ms
getjs.aspx
17 ms
GetAd.aspx
16 ms
GetAd.aspx
13 ms
sd
30 ms
GetAd.aspx
17 ms
ADTECH;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456805632963
9 ms
ADTECH;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456805632966
12 ms
getjs.aspx
15 ms
ADTECH;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456805632976
6 ms
getjs.aspx
14 ms
getjs.aspx
14 ms
GetAd.aspx
17 ms
GetAd.aspx
15 ms
GetAd.aspx
16 ms
ADTECH;cfp=1;rndc=1456805632;loc=100;target=_blank;grp=[group];misc=1456805633006
135 ms
ADTECH;cfp=1;rndc=1456805632;loc=100;target=_blank;grp=[group];misc=1456805633011
153 ms
ADTECH;cfp=1;rndc=1456805633;loc=100;target=_blank;grp=[group];misc=1456805633018
131 ms
activeview
18 ms
activeview
17 ms
cdsad.js
60 ms
30 ms
generic
10 ms
sync
12 ms
pixel
25 ms
providerid=1037;userid=5c2452aa-6feb-4b12-bc6c-583d275aaf2c
177 ms
mapuser
177 ms
mapuser
14 ms
mapuser
180 ms
mapuser
179 ms
mapuser
371 ms
mapuser
204 ms
mapuser
196 ms
ad
130 ms
ad
144 ms
ad
179 ms
getjs.aspx
21 ms
usersync.yashi.com
5 ms
match
454 ms
5447
27 ms
rand=11729
23 ms
400966.gif
26 ms
getjs.aspx
33 ms
usersync.yashi.com
22 ms
rand=17774
28 ms
5447
29 ms
GetAd.aspx
33 ms
400966.gif
18 ms
GetAd.aspx
15 ms
getjs.aspx
15 ms
sync
6 ms
rand=27850
7 ms
5447
19 ms
400966.gif
9 ms
ADTECH;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456805633571
17 ms
ADTECH;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456805633581
8 ms
GetAd.aspx
16 ms
ad
33 ms
Admeta.js
81 ms
ADTECH;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456805633601
7 ms
JSAdservingSP.ashx
12 ms
JSAdservingSP.ashx
12 ms
JSAdservingSP.ashx
14 ms
ADTECH;loc=100;target=_blank;grp=[group];misc=1456805633697
144 ms
fltiu.js
43 ms
ADTECH;loc=100;target=_blank;grp=[group];misc=1456805633700
121 ms
ADTECH;loc=100;target=_blank;grp=[group];misc=1456805633706
143 ms
iftfl.js
8 ms
getjs.aspx
15 ms
mapuser
89 ms
GetAd.aspx
17 ms
getjs.aspx
18 ms
getjs.aspx
14 ms
ad
168 ms
GetAd.aspx
14 ms
GetAd.aspx
15 ms
ad
328 ms
ad
285 ms
0.gif
14 ms
mapuser
5 ms
mapuser
95 ms
mapuser
94 ms
providerid=1036;userid=3f43ba3a391368460af2c68660e524fe2b8a47166c6c25c0437ea25e63f4c
99 ms
ADTECH;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456805634025
9 ms
empty.gif
209 ms
JSAdservingSP.ashx
33 ms
ad
45 ms
generic
17 ms
sync
18 ms
UserMatch.ashx
13 ms
iftfl.js
8 ms
ADTECH;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456805634166
53 ms
match
7 ms
ad
37 ms
ADTECH;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456805634204
8 ms
JSAdservingSP.ashx
11 ms
JSAdservingSP.ashx
9 ms
UserMatch.ashx
8 ms
rajamobil.com accessibility score
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
Image elements do not have [alt] attributes
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
rajamobil.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
rajamobil.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
ID
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rajamobil.com can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and it matches the claimed language. Our system also found out that Rajamobil.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.
rajamobil.com
Open Graph description is not detected on the main page of Raja Mobil. 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: