6.4 sec in total
627 ms
4.8 sec
987 ms
Click here to check amazing Pullman Jakarta Central Park content for Indonesia. Otherwise, check out these important facts you probably never knew about pullmanjakartacentralpark.com
“With pop art, a modern sleek and unique design, our luxury 5-star hotel offer guests a truly unique - business and leisure - stay experience....
Visit pullmanjakartacentralpark.comWe analyzed Pullmanjakartacentralpark.com page load time and found that the first response time was 627 ms 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.
pullmanjakartacentralpark.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value11.1 s
0/100
25%
Value10.5 s
7/100
10%
Value790 ms
37/100
30%
Value1.134
1/100
15%
Value11.4 s
19/100
10%
627 ms
136 ms
688 ms
187 ms
201 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 34% of them (42 requests) were addressed to the original Pullmanjakartacentralpark.com, 30% (37 requests) were made to Maps.google.com and 9% (11 requests) were made to Static-lub-sg-1.wp-ha.fastbooking.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Pullmanjakartacentralpark.com.
Page size can be reduced by 1.1 MB (50%)
2.3 MB
1.1 MB
In fact, the total size of Pullmanjakartacentralpark.com main page is 2.3 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. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 97.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. 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 97.1 kB or 84% 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. Pullman Jakarta Central Park images are well optimized though.
Potential reduce by 881.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 881.0 kB or 70% of the original size.
Potential reduce by 126.2 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. Pullmanjakartacentralpark.com needs all CSS files to be minified and compressed as it can save up to 126.2 kB or 84% of the original size.
Number of requests can be reduced by 49 (42%)
118
69
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pullman Jakarta Central Park. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.pullmanjakartacentralpark.com
627 ms
analytics.js
136 ms
8997260_2048_1537-300x225.jpg
688 ms
s4.0-19949-5.png
187 ms
11419138_824087967709117_1889888235_a.jpg
201 ms
10175241_955162154538685_2002556697_n.jpg
212 ms
fb-social.css
229 ms
jquery-ui.css
138 ms
reset.css
449 ms
jquery.fancybox.css
456 ms
custom.css
671 ms
jquery.min.js
128 ms
jquery-ui.min.js
1113 ms
jquery.ui.datepicker.min.js
457 ms
booking.min.js
457 ms
fb-cookie-law.js
666 ms
jquery.cycle2.min.js
788 ms
webfont.js
131 ms
jquery.fancybox.pack.js
774 ms
jquery.resizeCenter.js
773 ms
jquery.ui.datepicker-en.js
859 ms
waypoints.min.js
861 ms
js
115 ms
FBMap.js
270 ms
function.js
1112 ms
wp-embed.min.js
866 ms
fb-social.min.js
870 ms
xtcore.js
1077 ms
logo-pullman.svg
1077 ms
icon-globe.svg
1109 ms
selector.svg
1111 ms
pin-address.svg
1394 ms
icon-facebook-black.svg
1391 ms
icon-twitter-black.svg
1398 ms
icon-instagram-black.svg
1398 ms
icon-facebook-white.svg
1400 ms
icon-twitter-white.svg
1402 ms
icon-instagram-white.svg
1635 ms
icon-close.svg
1638 ms
calendar_white.svg
1628 ms
8997242_2048_1537-300x225.jpg
921 ms
Spa_cut-300x103.jpg
496 ms
1_home-300x94.jpg
757 ms
21-300x169.jpg
757 ms
31-300x169.jpg
756 ms
5_home-300x98.jpg
990 ms
41-300x169.jpg
1054 ms
s1.0-19949-5.png
111 ms
4.0-19949-5.png
106 ms
12728482_171319553244013_375175197_n.jpg
104 ms
12728455_788678224594490_2138538201_n.jpg
118 ms
12547361_1120895501262664_1704583176_n.jpg
119 ms
12558297_1135234026495381_2116187847_n.jpg
142 ms
collect
29 ms
collect
31 ms
spinner.png
941 ms
calendar.svg
932 ms
FuturaStd-Book.woff
873 ms
FuturaStd-CondensedBoldObl.woff
1228 ms
arrow-prev.svg
574 ms
arrow-next.svg
576 ms
close.svg
579 ms
common.js
58 ms
map.js
59 ms
util.js
56 ms
marker.js
56 ms
controls.js
53 ms
places_impl.js
54 ms
geometry.js
54 ms
directions.js
54 ms
arrow-prev.svg
410 ms
arrow-next.svg
412 ms
close.svg
617 ms
close.png
619 ms
onion.js
122 ms
openhand_8_8.cur
98 ms
infowindow.js
46 ms
css
146 ms
powered-by-google-on-white3.png
136 ms
autocomplete-icons.png
135 ms
ViewportInfoService.GetViewportInfo
175 ms
stats.js
94 ms
transparent.png
97 ms
hit.xiti
255 ms
google4.png
57 ms
mapcnt6.png
58 ms
sv5.png
64 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
47 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
46 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
47 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
46 ms
pin-address.png
222 ms
tmapctrl.png
71 ms
tmapctrl4.png
82 ms
vt
77 ms
vt
56 ms
vt
73 ms
vt
72 ms
vt
70 ms
vt
73 ms
vt
115 ms
vt
109 ms
vt
126 ms
vt
116 ms
vt
128 ms
vt
133 ms
vt
191 ms
vt
169 ms
vt
170 ms
vt
181 ms
vt
191 ms
vt
192 ms
vt
224 ms
vt
226 ms
vt
241 ms
vt
232 ms
vt
245 ms
vt
261 ms
vt
284 ms
8997260_2048_1537-700x700.jpg
922 ms
8997242_2048_1537-700x700.jpg
1121 ms
Spa_cut-700x411.jpg
906 ms
AuthenticationService.Authenticate
72 ms
pullmanjakartacentralpark.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.
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 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
Links do not have a discernible name
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.
pullmanjakartacentralpark.com 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
pullmanjakartacentralpark.com 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 Pullmanjakartacentralpark.com 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 Pullmanjakartacentralpark.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.
pullmanjakartacentralpark.com
Open Graph data is detected on the main page of Pullman Jakarta Central Park. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: